[Buildroot] [PATCH] Fix avahi build
Peter Korsgaard
jacmet at uclibc.org
Mon May 18 13:52:03 UTC 2009
>>>>> "Thiago" == Thiago A Corrêa <thiago.correa at gmail.com> writes:
Hi,
Thiago> I build several times, perhaps something got mixed
Thiago> up. Anyway, I figured what was the problem. X was disabled by
Thiago> Kconfig because the config name changed, so it picked up the
Thiago> default value (no X). I've reenabled all the packages
Thiago> disabled by Kconfig. X won't build for me either, but that's
Thiago> not quite my changes fault. It could be X code, or a bug with
Thiago> the avr32 toolchain source code.
Thiago> Do you want to commit with it updated? Or should we drop
Thiago> this patch (defconfig update) or drop atngw100-expanded
Thiago> altogether?
Well, basic avr32 support seems to be missing from the X server. I
don't have access to any avr32 hardware, so unless someone steps up to
fix it I think we should make BR2_PACKAGE_XSERVER_XORG_SERVER depend
on !BR2_avr32 (with a comment entry explaining it similar to the
packages needing C++/wchar/largefile support).
And then the -expanded defconfig doesn't make any sense, so it should
get removed.
Thiago> Anyway, X has nothing to do with avahi AFAIK.
True.
Thiago> Avahi is enabled in atngw100_defconfig as well. What you would have
Thiago> to do to reach the problematic code is actually enable "IPv4LL network
Thiago> address configuration daemon". Perhaps it should happen on all
Thiago> platforms or as I said before, there is some build order that creates
Thiago> the folder first for you but not for atngw100*_defconfig 's.
I normally build avahi with ipv4ll support (on ppc) without problems,
so it seems specific to atngw100. I'll do a test build and check.
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list