Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dtc: broken for static builds
Date: Mon, 3 Feb 2014 06:50:41 +0200	[thread overview]
Message-ID: <20140203045041.GI9184@tarshish> (raw)
In-Reply-To: <87bnypp6bs.fsf@dell.be.48ers.dk>

Hi Peter,

On Sun, Feb 02, 2014 at 10:12:23PM +0100, Peter Korsgaard wrote:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>  >> Ahh yes, I do see it on x86-64. Thanks.
> 
>  > What did you see on x86-64 exactly? Wasn't it related to libstdc++.a
>  > not being generated by the internal toolchain backend?
> 
> Sorry, I don't recall the details, but I think the issue was with it
> trying to create a shared library and not building the object files with fPIC.

I guess Thomas refers to 7d6c79ed887e (Compile static versions of gcc 
libraries). Before that libstdc++.a was not provided by the internal 
toolchain.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-02-03  4:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07  9:44 [Buildroot] [PATCH] dtc: broken for static builds Vicente Olivert Riera
2014-01-09 20:14 ` Peter Korsgaard
2014-01-10 14:51   ` Vicente Olivert Riera
2014-01-10 21:59     ` Peter Korsgaard
2014-01-28 21:01       ` Thomas Petazzoni
2014-01-30  9:35         ` Vicente Olivert Riera
2014-02-02 21:12         ` Peter Korsgaard
2014-02-03  4:50           ` Baruch Siach [this message]
2014-01-10 22:00 ` Peter Korsgaard

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=20140203045041.GI9184@tarshish \
    --to=baruch@tkos.co.il \
    --cc=buildroot@busybox.net \
    /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