Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] elfutils successfully compiled with buildroot 2012.05
Date: Wed, 19 Dec 2012 13:59:34 +0200	[thread overview]
Message-ID: <50D1AC26.4010905@petroprogram.com> (raw)
In-Reply-To: <1355909574.8626.6.camel@sven>

Good morning Sven

19.12.2012 11:32, Sven Neumann kirjoitti:
> On Tue, 2012-12-18 at 23:57 +0200, Stefan Fr?berg wrote:
>> Hello to all
>>
>> I just want to tell that I have now managed to complete building
>> elfutils version 0.155
>> successfully with Buildroot version 2012.05.
>>
>> After some sleep (and patch cleanup) I will send it here for initial review.
>> Not all of it went smoothly but I will explain it in more detail in the
>> patches.
>>
>> There are few screenshots of my uClibc environment under VirtualBox
>> with working readelf from elfutils package.
>>
>> Regards
>> Stefan
>>
>> P.S.:  AFAIK, Glib from version 2.32 and up needs elfutils (or at least
>> it's libelf component) as hard dependency ????
> No, it's a soft dependency. glib 2.32 will build without libelf. In a
> build without libelf you won't be able to use the GResource
> functionality though, see
> http://developer.gnome.org/gio/2.32/gio-GResource.html
>
>
> Regards,
> Sven
>
Ah, I see.

I assumed it to be hard dependency because in my Gentoo linux installation
they list it as so.
But this is good to know.

Thanks!

Regards
Stefan

      reply	other threads:[~2012-12-19 11:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 21:57 [Buildroot] elfutils successfully compiled with buildroot 2012.05 Stefan Fröberg
2012-12-19  9:32 ` Sven Neumann
2012-12-19 11:59   ` Stefan Fröberg [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=50D1AC26.4010905@petroprogram.com \
    --to=stefan.froberg@petroprogram.com \
    --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