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, 12 Dec 2011 13:54:00 -0000 [thread overview]
Message-ID: <CAHUNapTd3=gbFe8X-p9Zg=kJK4N1QUNtpC+oDvLL5uh3izKb-w@mail.gmail.com> (raw)
In-Reply-To: <201112121335.43024.yann.morin.1998@anciens.enib.fr>
Hi Yann,
On Mon, Dec 12, 2011 at 7:35 AM, Yann E. MORIN
<yann.morin.1998@anciens.enib.fr> wrote:
> Could you test without the patch, but first setting the following before
> runninf ct-ng:
> export CONFIG_SITE=
Yes, I saw that post on the buildroot mailing list too. As a quick
test it "fixed" the install-strip problem I was having. Now I want to
go back and re-test on a full build with and without CONFIG_SITE and
with and without the patch that is provided to my machine's
/usr/share/site/x86_64-unknown-linux-gnu.
Seeing as it appears to be a bug in openSUSE I guess your proposed
patch isn't necessary?
I'll report back when I've played around with it some more, but it
looks like the problem is fixed and appears to be a bug in openSUSE
12.1.
Best regards,
Trevor
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-12-12 13:54 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
2011-12-11 21:44 ` Yann E. MORIN
2011-12-12 12:36 ` Yann E. MORIN
2011-12-12 13:54 ` Trevor Woerner [this message]
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='CAHUNapTd3=gbFe8X-p9Zg=kJK4N1QUNtpC+oDvLL5uh3izKb-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).