This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC 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: Error when building cross compiler

From: Denis Onischenko <denis dot onischenko at gmail dot com>
To: Kai Ruottu <kai dot ruottu at wippies dot com>, iant at google dot com, gcc-help at gcc dot gnu dot org, gcc at gcc dot gnu dot org
Date: Sat, 24 Oct 2009 11:59:46 +0300
Subject: Re: Error when building cross compiler
References: <c80516030910040600oaa591a6kfb45de734393930e@mail.gmail.com> <mcriqetn4ak.fsf@dhcp-172-17-9-151.mtv.corp.google.com> <c80516030910051125y21c8b48dp88bab103377e90a2@mail.gmail.com> <c80516030910051147y537bd4dfjb04c96f0e3e89da9@mail.gmail.com> <mcry6nplj0o.fsf@dhcp-172-17-9-151.mtv.corp.google.com> <4AD5D375.1070909@wippies.com>

>> There is something peculiar going on, because a
>> x86_64-unknown-linux-gnu hosted compiler would not normally refer to
>> libgcc_s.so.1 at all.  Even if it did, nothing would normally direct
>> the dynamic linker to look in the gcc build directory.  Something is
>> wrong but I don't know what it is.

I have successfully build cross-compiler with overriden RPATH_ENVVAR,
as following:
make RPATH_ENVVAR=MY_LD_LIBRARY_PATH

So error was indeed caused by changing LD_LIBRARY_PATH during the
build, as described by Kai.

I think this is a bug.

Follow-Ups:
- Re: Error when building cross compiler
  - From: Ian Lance Taylor

References:
- Re: Error when building cross compiler
  - From: Denis Onischenko
- Re: Error when building cross compiler
  - From: Denis Onischenko
- Re: Error when building cross compiler
  - From: Ian Lance Taylor
- Re: Error when building cross compiler
  - From: Kai Ruottu

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