On Apr 19, 2013, at 06:50, Tim Kientzle <kient...@freebsd.org> wrote: > On Apr 17, 2013, at 10:33 AM, Dimitry Andric wrote: > >> In any case, the layout has been like this since the initial clangbsd >> import, and I never saw any reason to change it. Maybe Ed can tell a >> bit more, since he seems to have done the initial infrastructure setup. > > FreeBSD/ARM just switched from GCC to Clang, which is > why this just got noticed. U-Boot is used quite heavily for > FreeBSD/ARM (and MIPS and PowerPC as well, I believe). > > Here are the options I see for getting > cc -print-file-name=include > to work again: > > * Hack clang to handle -print-file-name=include specially. > I did this for GCC already, but I'm not thrilled about it. > > * Configure clang differently so that this option works. > > * Symlink /usr/include to appear somewhere that clang expects. > > * Rearrange our directory layout slightly to match clang's expectations.
You seem to have left out the most obvious one: * Fixing U-Boot's configuration script(s) so they don't depend on undocumented compiler options. I don't understand why we would want to go through all this trouble, just for telling U-Boot where a bunch of headers are located? What happened to configure scripts with options, they did not disappear overnight, I hope? _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
