This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: GCC 2.96 for new cygwin?
- From: Tino Lange <Tino dot Lange at isg dot de>
- To: Patrick Reuter <preuter at labri dot fr>, cygwin at cygwin dot com
- Date: Thu, 21 Nov 2002 22:05:59 +0100
- Subject: Re: GCC 2.96 for new cygwin?
- Organization: IS Innovative Software AG
- References: <3DDD3911.60C6D5CF@labri.fr> <3DDD3C22.8BFB7A6B@isg.de> <3DDD3E73.722A02BE@labri.fr>
Hi Patrick!
> thanks a lot for this help. I could have saved 2 hours asking you before
:-)
> I usually work on red hat 7.2, and I dynamically link libraries (in my example
> lapack) using the LD_LIBRARY_PATH and the .so are dynamically linked.
> Now I need to compile the project under Windows. Do you know how this works?
You have to compile *everything* under cygwin, also the libraries (if
they're not that prominent that they can be installed via "setup.exe").
> I also need to link some libXXX.a. This seems not to work neither.
Hmmm, it really should. Are they compiled within the cygwin environment?
Try rebuilding the *.a with the new compiler. (The 2.95 you were looking
for)
You know that c++-libs built by gcc3.x are incompatible to the gcc2.x
ones?
So you cannot link some parts that you were able to compile with the
gcc-3.2 with the parts you now compile with the gcc-2.95. (This might
only work for plain C)
Cheers,
Tino
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/