On 08/01/15 15:15, Martin Lucina wrote: >> Maybe you can compare the cc default settings and also the output for cc >> -E for lib/libc/stdio/vnsprintf.c > > The compiler flags and indeed the entire command line used to compile > vsnprintf.o are identical. However, on the ubuntu machine I see strange > warnings about redefining vsnprintf, among other things.
And what about preprocessor output? There can be something hidden in specs which causes the compiler to behave differently in way you cannot see on the command line (at least not without -v). > Not sure what is going on here. I've attached the relevant portions of the > build logs to this message. Yea, nobody has been sure about those warning for quite a while. AFAIK they've been there since the initial bolting of NetBSD libc onto the then-known-as-rumpuser-xen. But since they've been *seemingly* harmless, nobody has bothered. Looks like I need to get to the bottom of it finally, possibly tonight. > /home/mato/rumprun-xen/rumptools/dest/usr/include/ssp/stdio.h:64:0: warning: > "vsnprintf" redefined [enabled by default] > #define vsnprintf(str, len, fmt, ap) \ ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
