Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building avahi
Date: Wed, 5 Jan 2011 17:10:27 +0100	[thread overview]
Message-ID: <20110105171027.1e64ffe6@surf> (raw)
In-Reply-To: <B3C53ADB207D471B8656E4BCBBDDD557@WSA.local>

Hello Andreas,

On Wed, 5 Jan 2011 15:20:55 +0100
"Andreas Stahl" <a.stahl@wsa-electronic.de> wrote:

> I cannot build the avahi package on buildroot-2010.11
> my steps:
> - download and extract buildroot-2010.11.tar.bz2
> - cd to the buildroot-2010.11 directory
> - make atngw100_defconfig
> - make

For what it's worth, on my system, this exact set of commands produces
a working build, which includes avahi.

> '/usr/buildroot-2010.11/output/build/avahi-0.6.27/avahi-glib'

This path seems to indicate that you might be running Buildroot as
root. You should not do this.

And in fact I think it's precisely because you're building somewhere
in /usr that things break. In order to workaround libtool oddness, we
have a mechanism in Buildroot that modifies .la files by replacing:

 /usr

by

 $(STAGING_DIR)/usr

But in your case, since your $(STAGING_DIR) starts by /usr, the rule
gets executed over and over and over again, so the path goes like this:

 /usr
 $(STAGING_DIR)/usr
 $(STAGING_DIR)/$(STAGING_DIR)/usr
 $(STAGING_DIR)/$(STAGING_DIR)/$(STAGING_DIR)/usr

etc.

So as a quick fix you can just not build from /usr, and build from
$HOME, as a normal user. Long term, we should improve our sed
expression to not fall into this.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-01-05 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 14:20 [Buildroot] Problem building avahi Andreas Stahl
2011-01-05 16:10 ` Thomas Petazzoni [this message]
2011-01-06 11:11   ` Andreas Stahl
2011-01-06 11:32     ` Thomas Petazzoni
2011-01-06 12:33       ` Peter Korsgaard
2011-01-06 12:55         ` Thomas Petazzoni
2011-01-06 13:19           ` Quotient Remainder
2011-01-06 13:19           ` 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=20110105171027.1e64ffe6@surf \
    --to=thomas.petazzoni@free-electrons.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