Re: Unable to override OBJCOPY during configure

Re: Unable to override OBJCOPY during configure

[Adhemerval Zanella]

			

On 03/02/2021 23:01, Ryan Burns via Libc-help wrote:
> Hi Libc-help,
> 
> I'm having trouble cross-compiling glibc to powerpc64le. Compiling to powerpc64le requires a working objcopy, which I have available via powerpc64le-unknown-linux-gnu-objcopy, and I can provide that at build time using "make OBJCOPY=powerpc64le-unknown-linux-gnu-objcopy".
> But the toplevel ./configure does OBJCOPY=`$CC -print-prog-name=objcopy` unconditionally, and is unable to find powerpc64le-unknown-linux-gnu-objcopy, so the later version check (to enforce the objcopy 2.26 minimum requirement) fails.
> Is it possible to manually specify the objcopy binary at configure time, or bypass the configure check for the objcopy version?
> 
> Thanks,
> Ryan
> 

If you have a cross-toolchain correctly configured, the '-print-prog-name=objcopy' 
should give the full path to the objcopy. On my system:

$ [...]/powerpc64le-glibc-linux-gnu-gcc -print-prog-name=objcopy
[...]/compilers/powerpc64le-linux-gnu/bin/../lib/gcc/powerpc64le-glibc-linux-gnu/8.3.1/../../../../powerpc64le-glibc-linux-gnu/bin/objcopy

Otherwise you can explicit set OBJCOPY to the objcopy during configure:

$ [...]/configure --prefix=/usr [...] OBJCOPY=/path/to/objcopy

Re: Unable to override OBJCOPY during configure

[Ryan Burns]

Hmm, I tried providing OBJCOPY to configure, but it looks like it gets clobbered here:
https://sourceware.org/git/?p=glibc.git;a=blob;f=configure;h=1dc3af60b4146ba5f9fd251a6820e21752c65444;hb=HEAD#l4494
Perhaps I am misunderstanding the configure script, but I think it's overriding the OBJCOPY I'm providing?

I think you are correct that I should reconfigure my toolchain so that '-print-prog-name' works correctly.
But if this is an acceptable use of an explicit OBJCOPY, I'd like to be able
to get by with that for now so I don't have to recompile gcc.


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, February 5, 2021 3:41 AM, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:

> On 03/02/2021 23:01, Ryan Burns via Libc-help wrote:
>
> > Hi Libc-help,
> > I'm having trouble cross-compiling glibc to powerpc64le. Compiling to powerpc64le requires a working objcopy, which I have available via powerpc64le-unknown-linux-gnu-objcopy, and I can provide that at build time using "make OBJCOPY=powerpc64le-unknown-linux-gnu-objcopy".
> > But the toplevel ./configure does OBJCOPY=`$CC -print-prog-name=objcopy` unconditionally, and is unable to find powerpc64le-unknown-linux-gnu-objcopy, so the later version check (to enforce the objcopy 2.26 minimum requirement) fails.
> > Is it possible to manually specify the objcopy binary at configure time, or bypass the configure check for the objcopy version?
> > Thanks,
> > Ryan
>
> If you have a cross-toolchain correctly configured, the '-print-prog-name=objcopy'
> should give the full path to the objcopy. On my system:
>
> $ [...]/powerpc64le-glibc-linux-gnu-gcc -print-prog-name=objcopy
> [...]/compilers/powerpc64le-linux-gnu/bin/../lib/gcc/powerpc64le-glibc-linux-gnu/8.3.1/../../../../powerpc64le-glibc-linux-gnu/bin/objcopy
>
> Otherwise you can explicit set OBJCOPY to the objcopy during configure:
>
> $ [...]/configure --prefix=/usr [...] OBJCOPY=/path/to/objcopy

Re: Unable to override OBJCOPY during configure

[H.J. Lu]

On Fri, Feb 5, 2021 at 4:10 PM Ryan Burns via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Hmm, I tried providing OBJCOPY to configure, but it looks like it gets clobbered here:
> https://sourceware.org/git/?p=glibc.git;a=blob;f=configure;h=1dc3af60b4146ba5f9fd251a6820e21752c65444;hb=HEAD#l4494
> Perhaps I am misunderstanding the configure script, but I think it's overriding the OBJCOPY I'm providing?
>
> I think you are correct that I should reconfigure my toolchain so that '-print-prog-name' works correctly.
> But if this is an acceptable use of an explicit OBJCOPY, I'd like to be able
> to get by with that for now so I don't have to recompile gcc.
>
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, February 5, 2021 3:41 AM, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
>
> > On 03/02/2021 23:01, Ryan Burns via Libc-help wrote:
> >
> > > Hi Libc-help,
> > > I'm having trouble cross-compiling glibc to powerpc64le. Compiling to powerpc64le requires a working objcopy, which I have available via powerpc64le-unknown-linux-gnu-objcopy, and I can provide that at build time using "make OBJCOPY=powerpc64le-unknown-linux-gnu-objcopy".
> > > But the toplevel ./configure does OBJCOPY=`$CC -print-prog-name=objcopy` unconditionally, and is unable to find powerpc64le-unknown-linux-gnu-objcopy, so the later version check (to enforce the objcopy 2.26 minimum requirement) fails.
> > > Is it possible to manually specify the objcopy binary at configure time, or bypass the configure check for the objcopy version?
> > > Thanks,
> > > Ryan
> >
> > If you have a cross-toolchain correctly configured, the '-print-prog-name=objcopy'
> > should give the full path to the objcopy. On my system:
> >
> > $ [...]/powerpc64le-glibc-linux-gnu-gcc -print-prog-name=objcopy
> > [...]/compilers/powerpc64le-linux-gnu/bin/../lib/gcc/powerpc64le-glibc-linux-gnu/8.3.1/../../../../powerpc64le-glibc-linux-gnu/bin/objcopy
> >
> > Otherwise you can explicit set OBJCOPY to the objcopy during configure:
> >
> > $ [...]/configure --prefix=/usr [...] OBJCOPY=/path/to/objcopy
>
>

You can use scripts/build-many-glibcs.py to cross compile glibc.

-- 
H.J.