From: Martin Jansa <martin.jansa@gmail.com>
To: Giuseppe CONDORELLI <giuseppe.condorelli@st.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] eglibc: fix as and ld check in libc dir
Date: Thu, 17 Jan 2013 14:46:19 +0100 [thread overview]
Message-ID: <20130117134619.GI3067@jama> (raw)
In-Reply-To: <065b01cdf4b6$e1510160$a3f30420$@st.com>
[-- Attachment #1: Type: text/plain, Size: 2333 bytes --]
On Thu, Jan 17, 2013 at 02:30:55PM +0100, Giuseppe CONDORELLI wrote:
> Hi Martin,
>
> Do you mean applying the patch you highlighted in libc/configure?
I was expecting you're trying to fix ld --version detection when ld is
gold. But after few experiments I don't see what you're trying to fix:
martin@jama ~ $ ld.bfd --version 2>&1 | sed -n 's/^.*GNU ld.* \([0-9][0-9]*\.[0-9.]*\).*$/\1/p'
2.23.1
martin@jama ~ $ ld.gold --version 2>&1 | sed -n 's/^.*GNU ld.* \([0-9][0-9]*\.[0-9.]*\).*$/\1/p'
nothing -> ld.gold still unsupported
old:
martin@jama ~ $ echo 2.23.1 | egrep "2.1[0-9][0-9]*|2.[2-9][0-9]*|[3-9].*|[1-9][0-9]*"
2.23.1
martin@jama ~ $ echo 2.19.1 | egrep "2.1[0-9][0-9]*|2.[2-9][0-9]*|[3-9].*|[1-9][0-9]*"
2.19.1
martin@jama ~ $ echo 2.19 | egrep "2.1[0-9][0-9]*|2.[2-9][0-9]*|[3-9].*|[1-9][0-9]*"
2.19
martin@jama ~ $ echo 2.1 | egrep "2.1[0-9][0-9]*|2.[2-9][0-9]*|[3-9].*|[1-9][0-9]*"
2.1
new:
martin@jama ~ $ echo 2.19.1 | egrep "2.1[0-9]*|2.[2-9][0-9]*|[3-9].*|[1-9][0-9]*"
2.19.1
martin@jama ~ $ echo 2.23.1 | egrep "2.1[0-9]*|2.[2-9][0-9]*|[3-9].*|[1-9][0-9]*"
2.23.1
martin@jama ~ $ echo 2.19 | egrep "2.1[0-9]*|2.[2-9][0-9]*|[3-9].*|[1-9][0-9]*"
2.19
martin@jama ~ $ echo 2.1 | egrep "2.1[0-9]*|2.[2-9][0-9]*|[3-9].*|[1-9][0-9]*"
2.1
Can you show some example version your patch is fixing?
Cheers,
> >-----Original Message-----
> >From: Martin Jansa [mailto:martin.jansa@gmail.com]
> >Sent: giovedì 17 gennaio 2013 13:42
> >To: Giuseppe Condorelli
> >Cc: Giuseppe CONDORELLI; openembedded-core@lists.openembedded.org
> >Subject: Re: [OE-core] [PATCH] eglibc: fix as and ld check in libc dir
> >
> >On Wed, Jan 16, 2013 at 04:07:39PM +0100, Giuseppe Condorelli wrote:
> >> 2013/1/16 Martin Jansa <martin.jansa@gmail.com>
> >>
> >> > On Wed, Jan 16, 2013 at 03:14:07PM +0100, Giuseppe CONDORELLI wrote:
> >> > > Fix routine to check as and ld version check in the configure, to
> allow
> >> > system
> >> > > to correctly check for version 2.1x.
> >> >
> >> > Does it build with gold now?
> >> >
> >> > http://lists.linuxtogo.org/pipermail/openembedded-core/2012-
> >March/020310.html
> >
> >does it?
> >
> >--
> >Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-01-17 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 14:14 [PATCH] eglibc: fix as and ld check in libc dir Giuseppe CONDORELLI
2013-01-16 15:02 ` Martin Jansa
2013-01-16 15:07 ` Giuseppe Condorelli
2013-01-17 12:42 ` Martin Jansa
2013-01-17 13:30 ` Giuseppe CONDORELLI
2013-01-17 13:46 ` Martin Jansa [this message]
2013-01-17 16:59 ` Giuseppe CONDORELLI
2013-01-17 17:28 ` Martin Jansa
2013-01-18 8:32 ` Giuseppe CONDORELLI
2013-01-18 8:55 ` Martin Jansa
2013-01-18 9:01 ` Giuseppe CONDORELLI
2013-01-18 17:12 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130117134619.GI3067@jama \
--to=martin.jansa@gmail.com \
--cc=giuseppe.condorelli@st.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox