Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3DDD4AB7.BCCCE196@isg.de> Date: Thu, 21 Nov 2002 22:05:59 +0100 From: Tino Lange Organization: IS Innovative Software AG X-Accept-Language: de,en,fr MIME-Version: 1.0 To: Patrick Reuter , cygwin AT cygwin DOT com Subject: Re: GCC 2.96 for new cygwin? References: <3DDD3911 DOT 60C6D5CF AT labri DOT fr> <3DDD3C22 DOT 8BFB7A6B AT isg DOT de> <3DDD3E73 DOT 722A02BE AT labri DOT fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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/