This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: can't for daemon problem with gcc/gcj compiled program
- From: "Knight, Lloyd" <Lloyd dot Knight at adc dot com>
- To: <tromey at redhat dot com>
- Cc: <java at gcc dot gnu dot org>
- Date: Tue, 10 Apr 2007 13:14:04 -0500
- Subject: RE: can't for daemon problem with gcc/gcj compiled program
i am open to all suggestions.
if i need a newer copy of gcc i can build that.
especially if the likelihood of my receiving any assistance with issues
is better than with a "closed" version.
are there some preferred configure options?
for 3.4.6 i used --prefix=/new/dir --enable-shared and
--enable-languages=c,c++,java
(i limited the languages because the fortran stuff was giving me compile
issues.)
if the prevailing wisdom is to upgrade, i can do that....
thanks for your reply.
lloyd
-----Original Message-----
From: tromey@redhat.com [mailto:tromey@redhat.com]
Sent: Tuesday, April 10, 2007 12:15 PM
To: Knight, Lloyd
Cc: java@gcc.gnu.org
Subject: Re: can't for daemon problem with gcc/gcj compiled program
>>>>> "Lloyd" == Knight, Lloyd <Lloyd.Knight@adc.com> writes:
Lloyd> i have compiled/installed gcc3.4.6 in order to compile the gpl
Lloyd> software, pdftk1.4 on solaris8.
GCC 3.4.6 is rather old. Why not use a newer version?
Lloyd> [4] GC_thr_init(0x9eacc4, 0x9eae04, 0x0, 0xffbef628, 0x0,
Lloyd> 0x917284), at 0x5dbd90
You could try 'make check' in the GC build directory. That is a basic
GC smoke test.
But even if it fails there's really nothing we can do to help you.
3.4.x is closed. We've done GC imports since then, so upgrading might
help. (I am not a Solaris user so I can't say for certain.)
Tom