This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: Pb of compilation of libgcj on WinNT
- To: <hpoulard@actia.fr>
- Subject: Re: Pb of compilation of libgcj on WinNT
- From: "Shane McDonald" <mcdshane@sedsystems.ca>
- Date: Fri, 11 Jun 1999 09:02:01 -0600
- Cc: <java-discuss@sourceware.cygnus.com>
- References: <122814040699*/S=hpoulard/O=actia/PRMD=actia/ADMD=atlas/C=fr/@MHS> <199906051601.JAA21795@hoser.cygnus.com>
Hi there:
From: Anthony Green <green@cygnus.com>
To: <hpoulard@actia.fr>
Cc: <java-discuss@sourceware.cygnus.com>
Sent: Saturday, June 05, 1999 10:01 AM
Subject: Re: Pb of compilation of libgcj on WinNT
> Herve wrote:
> > There are still problem during the building of the library (more
precisely
> > the libiberty.a). The configuring process do not find the standard
include
> > files (like stdio.h .....)
>
> I'm afraid I can't help you. This is an egcs or cygwin problem.
> You'll have better luck resolving this on either of those lists.
I don't know if you made any progress on getting this resolved. I had a
similar problem (configuring process did not find the standard include
files). I tracked the problem down to the software looking for the include
files in /usr/include, rather than the appropriate cygwin directory. I
worked around the problem by copying cygwin's includes into a newly-created
/usr/include directory. I'm sure there's an option to configure to specify
this, but I took the easy way out...
After doing this, I was able to compile egcs, including the gcj stuff, but
wasn't able to compile libgcj. I don't have my notes with me, so I can't
report the exact error, but it appeared to be a limitation of the Windows
environment, so I gave up at that point.
Shane McDonald