On Thu, Feb 14, 2008 at 8:42 AM, Denys Vlasenko <[EMAIL PROTECTED]> wrote: > > "gcc file.c -o /dev/null" used to delete /dev/null if compile failed. > It never "used to work" as expected in this case, until this bug was fixed.
could you give me a real life file.c example ? small preferably. I cannot reproduce this on DetaolB v0.8.1 which contains gcc-3.4.6 > busybox couldnt care less about whether toolchain was built with, > or without libintl & gettext. It just wants toolchail to compile C files. on DetaolB v0.8.1, if I compile gettext and install it, the specs file needs adjustments to be able to compile bbox 1.8.2 or 1.9.0 so actually bbox cares at least about the presence or not of gettext. something is not right here. I can provide log files. > Sorry, but the bug we were discussing has NOTHING to do > with libintl & gettext. I assume you met completely different bug > with somewhat similar symptoms. the symptom was not similar. it was the same. the /dev/null became a standard file and not a block file anymore. until I fixed the specs file by hand... -- Christian -- http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside ! _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
