From: Robert Yang <liezhi.yang@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: About update binutils (2.24 to 2.25)
Date: Thu, 8 Jan 2015 10:14:57 +0800 [thread overview]
Message-ID: <54ADE821.8030000@windriver.com> (raw)
In-Reply-To: <796F80B8-679B-4E8F-867C-522A3CFBF88A@gmail.com>
On 01/08/2015 10:10 AM, Khem Raj wrote:
>
>> On Jan 7, 2015, at 6:05 PM, Robert Yang <liezhi.yang@windriver.com> wrote:
>>
>>
>>
>> On 01/08/2015 09:55 AM, Khem Raj wrote:
>>>
>>>> On Jan 7, 2015, at 5:44 PM, Robert Yang <liezhi.yang@windriver.com> wrote:
>>>>
>>>>
>>>> Hi Khem,
>>>>
>>>> I'm trying to upgrade binutils from 2.24 to 2.25, there is
>>>> a patch binutils/libtool-2.4-update.patch which has 19317
>>>> lines, do you have any ideas on how did we make it in the past,
>>>> please ?
>>>
>>> what conflicts are you seeing ? if they are just in configure files then you
>>> need to autoteconf them manually one by one using the appropriate version of auototools as recommended
>>> for bintutils 2.25 usually gcc/binutils don’t use latest auto tools.
>>
>> Conflicts in ld/configure, I fixed it manually, I was curious how we made this
>> patch, and now you have explained, thanks.
>
> some portions are written and others are generated. since we do not autoreconf binutils, we do have to regenerate configure scripts
> so its a special case. Usually that would not be needed for autotooled recipes
Thanks, got it.
// Robert
>
>>
>> // Robert
>>
>>>
>>> but if they are reporting changes in other files then its a different problem needs to be looked at.
>>>
>>>
>>>>
>>>> $ diffstat ./binutils/libtool-2.4-update.patch
>>>> bfd/configure | 1314 +++++++++++++++++-----
>>>> bfd/configure.in | 2
>>>> binutils/configure | 1312 +++++++++++++++++-----
>>>> configure | 2
>>>> gas/configure | 1312 +++++++++++++++++-----
>>>> gprof/configure | 1317 +++++++++++++++++-----
>>>> ld/configure | 1693 ++++++++++++++++++++++-------
>>>> libtool.m4 | 1094 +++++++++++++------
>>>> ltmain.sh | 2925 ++++++++++++++++++++++++++++++++++-----------------
>>>> ltoptions.m4 | 2
>>>> ltversion.m4 | 12
>>>> lt~obsolete.m4 | 2
>>>> opcodes/configure | 1314 +++++++++++++++++-----
>>>> opcodes/configure.in | 2
>>>> 14 files changed, 8937 insertions(+), 3366 deletions(-)
>>>>
>>>> --
>>>> Thanks
>>>>
>>>> Robert
>>>
>>>
>>>
>
>
>
prev parent reply other threads:[~2015-01-08 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 1:44 About update binutils (2.24 to 2.25) Robert Yang
2015-01-08 1:55 ` Khem Raj
2015-01-08 2:05 ` Robert Yang
2015-01-08 2:10 ` Khem Raj
2015-01-08 2:14 ` Robert Yang [this message]
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=54ADE821.8030000@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.