On 09/30/2010 12:21 PM, Frans Meulenbroeks wrote:
It looks like libunwind provides header files that are named
identically to gcc header files. gcc then confuses these headers when it
is built, causing a break of the build.
This patch makes libunwind depend on gcc which resolves the build issue. Both
build nicely when gcc is built first.
Hm. Ideally this should be patched in gcc.
I don't think this is a gcc issue. It's a reasonable point of view,
right, but pushing the header file issue back to libunwind is a valid
POV, too. I think it's rather a problem between those two packages.
> Now I feel that if someone
does a bitbake libunwind; bitbake -cclean gcc; bitbake gcc things
still fail.
Did you give this a try? I'll check it as soon as I can.
Btw what include files are we talking about?
I took word from Steffen (Sledz) about the cause of the problem, so I
didn't investigate any further. Introducing the dependency seemed to fix
the problem, so why bother. However, I feel like this kind of problem is
better fixed (the way you're proposing it) by the package maintainer, if
there is one.
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Developer
DResearch Digital Media Systems GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:[email protected]
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB:54412
Ust.-IDNr. DE169013825; WEEE Reg.-Nr. DE 85995642
Geschäftsführer: Dr. M. Weber, W. Mögle
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
