From: Trevor Woerner <twoerner@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: Re: build failure in native gdb with crosstool-ng-1.13.1 on openSUSE 12.1
Date: Mon, 05 Dec 2011 22:36:00 -0000 [thread overview]
Message-ID: <CAHUNapT9LN+N96WWgi568e0kALZivnOf+zzgqdLEH2zhTrTu+w@mail.gmail.com> (raw)
In-Reply-To: <CAHUNapSwV0QTYeQOGfUWG=X11xWyrP+KqVRRZvt-hK_Jevuk1w@mail.gmail.com>
Hi Yann,
Any thoughts on the following? The patch worked but my "install strip"
step still failed.
Best regards,
Trevor
PS for the last couple days I have been receiving bounce messages from
anciens.enib.fr, so I'm not sure if you saw this reply previously.
On Tue, Nov 29, 2011 at 9:46 PM, Trevor Woerner <twoerner@gmail.com> wrote:
> (sorry, forgot the CC the list)
>
>
> ---------- Forwarded message ----------
> From: Trevor Woerner <twoerner@gmail.com>
> Date: Tue, Nov 29, 2011 at 9:45 PM
> Subject: Re: build failure in native gdb with crosstool-ng-1.13.1 on
> openSUSE 12.1
> To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
>
>
> Hi Yann,
>
> On Tue, Nov 29, 2011 at 5:53 PM, Yann E. MORIN
> <yann.morin.1998@anciens.enib.fr> wrote:
>> What target are youbuilding for? Could you post your .config, please?
>
> arm-cortex_a8-linux-gnueabi
>
> I have attached the config, but it's pretty much exactly the sample
> directly from ct-ng. The only changes are a couple path tweaks, and to
> enable make-3.81.
>
>> I never encountered this issue, but it can make sense if the target
>> architecture is 64-bit, in which case the libraries could be installed
>> in the lib64 sub-directory
>
> The target is 32-bit ARM, the host is 64-bit x86.
>
> If it's of any use I've attached the results of performing "gcc -v" on
> both 11.4 and 12.1. The only notable difference is that 11.4 enabled
> gold and 12.1 doesn't.
>
>> Care to test the attached patch, please?
>
> I have tested the patch and it works as well as my manual tweak;
> native gdb now builds, but it still fails in the strip step.
>
>>> The build then fails a little later (during cleanup, stripping all
>>> binaries) but I haven't looking into that yet to provide much
>>> information.
>>
>> Probably again an issue with lib vs. lib64 confusion along the road...
>
> I'm not sure what's going on here. I have attached the last part of
> the build log (hoping it's enough for your purposes).
>
> Best regards,
> Trevor
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-12-05 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 23:19 Trevor Woerner
2011-11-29 22:54 ` Yann E. MORIN
[not found] ` <CAHUNapRiJtqH3yJDztc-ZroJKzjgRWuSwDKNjZVYYSn5iM0ryA@mail.gmail.com>
2011-11-30 2:46 ` Trevor Woerner
2011-12-05 22:36 ` Trevor Woerner [this message]
2011-12-11 21:44 ` Yann E. MORIN
2011-12-12 12:36 ` Yann E. MORIN
2011-12-12 13:54 ` Trevor Woerner
2011-12-12 14:07 ` Yann E. MORIN
2011-12-12 21:53 ` Trevor Woerner
2011-12-12 22:43 ` Yann E. MORIN
2011-12-13 3:43 ` Trevor Woerner
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=CAHUNapT9LN+N96WWgi568e0kALZivnOf+zzgqdLEH2zhTrTu+w@mail.gmail.com \
--to=twoerner@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).