[debbugs-tracker] bug#24916: closed (Followup to AR=ar issues)

[GNU bug Tracking System]

Your message dated Thu, 10 Nov 2016 09:26:42 +0100
with message-id <address@hidden>
and subject line Re: bug#24916: Followup to AR=ar issues
has caused the debbugs.gnu.org bug report #24916,
regarding Followup to AR=ar issues
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24916: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24916
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Followup to AR=ar issues
>
>
>
>
> Date: 
>
> Thu, 10 Nov 2016 13:36:20 +1300
>
>
>
>
> User-agent: 
>
> KMail/5.2.3 (Linux/4.8.0-26-generic; KDE/5.26.0; x86_64; ; )
>
>
>
>
> I'm an OpenWRT user - which builds just about everything as cross tools - lots 
> of systems don't do AR and RANLIB paths correctly .... and it's not really 
> been a problem until recently ....
>
> I'm also an Ubuntu user and until I synced to their latest release OpenWRT 
> builds worked great .... now a bunch of stuff fails  .... the underlying 
> problem seems to be that now by default ar run on an Intel platform adds a 
> SYM64 header to archives even if they only contain 32-bit objects (in my case 
> ARM ones) - the older cross tools just throw their hands up and barf
>
> I wonder if a stopgap solution might be to accept that AR is broken in the 
> build environments and make ar smarter about what it generates, only adding 
> that header if 64-bit objects are there
>
>         Paul
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#24916: Followup to AR=ar issues
>
>
>
>
> Date: 
>
> Thu, 10 Nov 2016 09:26:42 +0100
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
>
>
>
>
> tag 24916 notabug
> thanks
>
> On 11/10/2016 01:36 AM, Paul Campbell wrote:
> > I'm an OpenWRT user - which builds just about everything as cross tools - 
> > lots 
> > of systems don't do AR and RANLIB paths correctly .... and it's not really 
> > been a problem until recently ....
> > 
> > I'm also an Ubuntu user and until I synced to their latest release OpenWRT 
> > builds worked great .... now a bunch of stuff fails  .... the underlying 
> > problem seems to be that now by default ar run on an Intel platform adds a 
> > SYM64 header to archives even if they only contain 32-bit objects (in my case 
> > ARM ones) - the older cross tools just throw their hands up and barf
> > 
> > I wonder if a stopgap solution might be to accept that AR is broken in the 
> > build environments and make ar smarter about what it generates, only adding 
> > that header if 64-bit objects are there
>
> ar is not part of coreutils but from binutils.  Therefore, there's nothing
> we can do here regarding this problem. Thus, I'm marking this as 'not a bug'
> in our bug tracker.
>
> Have a nice day,
> Berny
>
>
>
> --- End Message ---