Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Fix avahi build
Date: Sun, 17 May 2009 23:29:40 +0200	[thread overview]
Message-ID: <87k54fo1tn.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <d6cda7730905171037r4f4aa9f7y9a12eb9377ab70f8@mail.gmail.com> ("Thiago A. Corrêa"'s message of "Sun\, 17 May 2009 14\:37\:38 -0300")

>>>>> "Thiago" == Thiago A Corr?a <thiago.correa@gmail.com> writes:

Hi,

 >> I take it that you mean atngw100-expanded_defconfig? Did you try
 >> building that after your latest changes? The defconfig seems
 >> completely bogus to me - docker tried to use pkg-config from
 >> staging_dir instead of host_dir (fixed now), and you had turned off
 >> the X stuff and still tried to build libgtk2/webkit/docker/openmotif.

 Thiago> I just test built it and things that are newer than the defconfig,
 Thiago> when oldconfig jumps in asking what to do I just accepted the default
 Thiago> behavior. I didn't change it more than that. Then I run a test build,
 Thiago> and it stopped at avahi, so I fixed the problem with avahi, commited
 Thiago> avahi change, and resume the build.

 Thiago> Once I could see that the defconfg built completely, then I updated
 Thiago> the defconfig with my .config that contains the newly defined symbols
 Thiago> (with their default values).

So atngw100-expanded_defconfig builds for you even though it has X
disabled and libgtk2 / docker / webkit / sylpheed / xpdf and so on
enabled? That sounds very odd to me.

 Thiago> So, no idea what changed in the between at the main repository.

The only thing that changed to the expanded defconfig recently was
your change.

You are building from your 2009.05 branch and not master, right?

 >> Furthermore, enabling the Xserver doesn't work as there seems to be
 >> missing some avr32 support:
 >> 
 >> Are you using this?

 Thiago> I didn't try to build X, I don't use it. Unless it gets built
 Thiago> by one of the _defconfigs that I updated, then I built and
 Thiago> didn't see this happening. I can't afford to stare at the
 Thiago> screen for 30 or 40 minutes watching the build. If it doesn't
 Thiago> stop the build then mostly for sure I would miss it.

atngw100-expanded does (or rather, it should as it tried to build
stuff using X).

 >> And you didn't run into the above issues?
 >> 

 Thiago> Nope, not in my tree. They all built prior to commit to my local tree
 Thiago> and prior to push.

On the 2009.05 branch and with the -expanded defconfig?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-05-17 21:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 21:43 [Buildroot] [PATCH] Update atngw100-extended_defconfig root
2009-05-13 21:43 ` [Buildroot] [PATCH] Fix avahi build root
2009-05-13 21:43   ` [Buildroot] [PATCH] Update atngw100-base_defconfig root
2009-05-13 21:43     ` [Buildroot] [PATCH] CUPS requires stack protection support root
2009-05-13 21:43       ` [Buildroot] [PATCH] Update i686_defconfig root
2009-05-13 21:43         ` [Buildroot] [PATCH] Remove unused busybox.config root
2009-05-13 21:43           ` [Buildroot] [PATCH] Update i386_defconfig root
2009-05-13 21:43             ` [Buildroot] [PATCH] Update default linux config for x86 root
2009-05-13 21:43               ` [Buildroot] [PATCH] Remove unused busybox config root
2009-05-13 21:43                 ` [Buildroot] [PATCH] Update kernel config for atngw100_defconfig root
2009-05-13 21:43                   ` [Buildroot] [PATCH] Remove unused kernel configs root
2009-05-14 15:29               ` [Buildroot] [PATCH] Update default linux config for x86 Peter Korsgaard
2009-05-14 15:28       ` [Buildroot] [PATCH] CUPS requires stack protection support Peter Korsgaard
2009-05-14 15:26   ` [Buildroot] [PATCH] Fix avahi build Peter Korsgaard
2009-05-15  5:11     ` Thiago A. Corrêa
2009-05-16 12:04       ` Peter Korsgaard
2009-05-17 17:37         ` Thiago A. Corrêa
2009-05-17 21:29           ` Peter Korsgaard [this message]
2009-05-18  4:49             ` Thiago A. Corrêa
2009-05-18 13:52               ` Peter Korsgaard
2009-05-18 15:05                 ` 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=87k54fo1tn.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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