This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH]: mknetrel builds Guile #3: libtool

On Mon, Jul 15, 2002 at 06:31:41PM +0200, Jan Nieuwenhuizen wrote:
>Christopher Faylor <> writes:
>> Btw, after some investigation, It appears that you are putting
>>/whereever/i686-pc-cygwin/bin in your path when it is not intended to
>>be in your path.  That directory is only intended to be run by the
>>cross tools.  If you need to use the cross versions of ar, as, ld,
>>etc., you should be invoking them as i686-pc-cygwin-ar,
>>i686-pc-cygwin-as, etc.  Including this directory in your path will
>>just confuse the native tools since it has the undecorated versions
>>of the programs like "ld".
>Yes, thanks.  Indeed, I did that until recently.  I found out, very
>soon that the cross 'ld' cannot be in PATH, it will break things
>After looking at mknetrel I realised that using the i686-pc-cygwin-*
>tools directly should work (it worked for you apparently); and that's
>a much nicer solution.  [I seem to remember this didn't work for
>configuring/compiling certain things, a long time ago, but I may have
>done something silly back then.  Then I kept that setup because it
>However, It turns out that your fix to help libtool that wants LD:
>    LD=$(${build_cc} -print-prog-name=ld)
>doesn't seem to work over here:
>    mknetrel-debug ~$ which gcc
>    /usr/bin/gcc
>    mknetrel-debug ~$ which ld
>    /usr/bin/ld
>    mknetrel-debug ~$ gcc -print-prog-name=ld
>    ld
>    mknetrel-debug ~$ which i686-pc-cygwin-gcc
>    /home/cygwin/cygwin-1.3.10/linux-x-cygwin/usr/bin/i686-pc-cygwin-gcc
>    mknetrel-debug ~$ i686-pc-cygwin-gcc -print-prog-name=ld
>    ld
>    mknetrel-debug ~$ i686-pc-cygwin-gcc -print-prog-name=i686-pc-cygwin-ld
>    i686-pc-cygwin-ld
>Isn't -print-prog-name supposed to give the full path, or do I have an
>installation problem?  Note that the native gcc (2.95.4) does not
>produce a full path either?

It is supposed to provide the full path.  I suspect you have something
installed incorrectly, like maybe ld is missing from i686-pc-cygwin/bin
or you still have i686-pc-cygwin/bin in your path..  If the above is
true, then the cross version of gcc is using the linux (or whatever)
version of ld.  That's clearly wrong.

So, to be clear:  If i686-pc-cygwin-gcc is not returning a full path,
you have an installation problem.  You should fix that.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]