From mboxrd@z Thu Jan 1 00:00:00 1970 From: Baruch Siach Date: Thu, 1 Nov 2012 08:10:28 +0200 Subject: [Buildroot] cannot compile a program within a uclibc build chroot In-Reply-To: <50921057.2080606@scalemp.com> References: <50913F89.3000802@scalemp.com> <5091A1B2.7060407@mind.be> <50921057.2080606@scalemp.com> Message-ID: <20121101061028.GA17989@sapphire.tkos.co.il> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hi Eial, On Thu, Nov 01, 2012 at 08:01:59AM +0200, Eial Czerwacki wrote: > On 11/01/2012 12:09 AM, Arnout Vandecappelle wrote: > > On 10/31/12 16:11, Eial Czerwacki wrote: > >> '/usr/lib/gcc/i686-unknown-linux-uclibc/4.6.0/../../../../i686-unknown-linux-uclibc/bin/as': > >> > >> execv: No such file or directory > > > > This is probably because one of the libraries against which as is linked > > cannot be found. It's probably linked with the host libc instead of the > > target libc. You can verify that with 'readelf -d': if you see libc.so.6 > > in there, it's been linked with the host's glibc. > > > > Regards, > > Arnout > ok, that is stranger, I cannot run readelf from within the chroot > although it is there, see: Well, you don't need to. You can use your host's readelf on your target's binaries to get the same information. > sh: can't execute 'readelf': No such file or directory > ~ # which readelf > /usr/bin/readelf > ~ # /usr/bin/readelf > sh: can't execute '/usr/bin/readelf': No such file or directory You may get a "No such file or directory" error when one of your NEEDED shared libraries are missing. Run 'readelf -d' on your terget's readelf, to see your dependencies. baruch -- http://baruch.siach.name/blog/ ~. .~ Tk Open Systems =}------------------------------------------------ooO--U--Ooo------------{= - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -