Hi, On Dec 16, 2014, at 14:46, Barry Kauler <[email protected]> wrote:
> > On 12/16/14, Barry Kauler <[email protected]> wrote: >> Rene, >> I think that you have had a lot of experience with dietlibc, perhaps >> you recognise this problem: >> >> I compiled a small utility with dietlibc, and it compiles ok, the binary >> works. >> >> However, T2 reports a failure, with this message: >> >> /usr/dietlibc/lib-i386/libc.a(vprintf.o): In function `vprintf': >> vprintf.c:(.text+0x3e): warning: warning: the printf functions add >> several kilobytes of bloat. >> /usr/dietlibc/lib-i386/libc.a(stdout.o): In function `__fflush_stdout': >> stdout.c:(.text+0x7): warning: warning: your code uses stdio (7+k bloat). >> /usr/lib/gcc/i686-t2-linux-gnu/4.9.2/../../../../i686-t2-linux-gnu/bin/ld: >> error in /usr/dietlibc/lib-i386/dyn_stop.o(.eh_frame); no >> .eh_frame_hdr table will be created. >> >> As the error appears to not really be an error, how can I tell T2 to ignore >> it? >> > > Oh, looking again at the error log, it seems the above might not be > why T2 stopped. > Here is more of the log: > > /usr/dietlibc/lib-i386/libc.a(stderr.o): In function `__fflush_stderr': > stderr.c:(.text+0x7): warning: warning: your code uses stdio (7+k bloat). > /usr/dietlibc/lib-i386/libc.a(vfprintf.o): In function `vfprintf': > vfprintf.c:(.text+0x37): warning: warning: the printf functions add > several kilobytes of bloat. > /usr/lib/gcc/i686-t2-linux-gnu/4.9.2/../../../../i686-t2-linux-gnu/bin/ld: > error in /usr/dietlibc/lib-i386/dyn_stop.o(.eh_frame); no > .eh_frame_hdr table will be created. > Running ldconfig ... > ldconfig: /usr/lib/libisl.so.10.2.2-gdb.py is not an ELF file - it has > the wrong magic bytes at the start. > > ldconfig: /usr/lib/libstdc++.so.6.0.20-gdb.py is not an ELF file - it > has the wrong magic bytes at the start. > > Creating file list and doing final adaptions ... > Searching for orphaned files ... > Found 18 files for this package. > Found 6 orphaned files for this package. > Clear (old) md5sums ... > Calculating package dependencies ... > Creating md5sum files ... done. > Creating package description ... > Making post-install adaptions. > Found files in /usr/local: > /usr/local/petget/debdb2pupdb > /usr/local/petget/find_cat > /usr/local/pup_event/pup_event_frontend_d > /usr/local/pup_event/pup_event_ipc > /usr/local/simple_network_setup/proxy-setup > Due to previous errors. > > ...so, is it an error to install into /usr/local? Well, yeah. /usr/local is meant for admin / user local installed things. That is why T2 prevents this by default for distro builders. (As some packages Makefiles install there accidentally, so that us developers catches this quickly.) You could set check_usrlocal=0 in the package if you really want to do this anyways, … (Btw. why do you install such files within the dietlibc package, and not something more matching? sysfiles or another package?) -- ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin http://exactcode.com | http://exactscan.com | http://ocrkit.com | http://t2-project.org | http://rene.rebe.de
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
