View previous topic :: View next topic |
Author |
Message |
Gaap Apprentice
Joined: 28 Jul 2005 Posts: 276
|
Posted: Tue Sep 05, 2006 8:06 pm Post subject: [RISOLTO]Problemi in emerge unshield |
|
|
come da topic posto subito il problema:
Code: |
>>> Emerging (1 of 485) app-arch/unshield-0.2 to /
>>> checking ebuild checksums ;-)
>>> checking auxfile checksums ;-)
>>> checking miscfile checksums ;-)
>>> checking unshield-0.2.tar.gz ;-)
>>> Unpacking source...
>>> Unpacking unshield-0.2.tar.gz to /var/tmp/portage/unshield-0.2/work
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/unshield-0.2/work/unshield-0.2 ...
* econf: updating unshield-0.2/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating unshield-0.2/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --build=i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gawk... (cached) gawk
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking for a BSD-compatible install... /bin/install -c
checking whether ln -s works... yes
checking for ld used by GCC... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/i686-pc-linux-gnu-nm -B
checking for a sed that does not truncate output... /bin/sed
checking how to recognise dependent libraries... pass_all
checking command to parse /usr/bin/i686-pc-linux-gnu-nm -B output... ok
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib
checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip
checking for objdir... .libs
checking for i686-pc-linux-gnu-gcc option to produce PIC... -fPIC
checking if i686-pc-linux-gnu-gcc PIC flag -fPIC works... yes
checking if i686-pc-linux-gnu-gcc static flag -static works... yes
checking if i686-pc-linux-gnu-gcc supports -c -o file.o... yes
checking if i686-pc-linux-gnu-gcc supports -c -o file.lo... yes
checking if i686-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking whether make sets $(MAKE)... (cached) yes
checking for ld used by GCC... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for an ANSI C-conforming const... yes
checking whether byte ordering is bigendian... no
checking for inttypes.h... (cached) yes
checking for stdint.h... (cached) yes
checking stdbool.h usability... yes
checking stdbool.h presence... yes
checking for stdbool.h... yes
checking for inflate in -lz... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating lib/md5/Makefile
config.status: creating lib/Makefile
config.status: creating src/Makefile
config.status: creating lib/unshield_config.h
config.status: executing depfiles commands
Making all in lib
make[1]: Entering directory `/var/tmp/portage/unshield-0.2/work/unshield-0.2/lib'
make all-recursive
make[2]: Entering directory `/var/tmp/portage/unshield-0.2/work/unshield-0.2/lib'
Making all in md5
make[3]: Entering directory `/var/tmp/portage/unshield-0.2/work/unshield-0.2/lib/md5'
source='md5c.c' object='md5c.lo' libtool=yes \
depfile='.deps/md5c.Plo' tmpdepfile='.deps/md5c.TPlo' \
depmode=gcc3 /bin/sh ../../depcomp \
/bin/sh ../../libtool --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../lib -g -Wall -Wno-long-long -Werror -ansi -O2 -mtune=i686 -pipe -I.. -O2 -mtune=i686 -pipe -c -o md5c.lo `test -f 'md5c.c' || echo './'`md5c.c
mkdir .libs
i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../lib -g -Wall -Wno-long-long -Werror -ansi -O2 -mtune=i686 -pipe -I.. -O2 -mtune=i686 -pipe -c md5c.c -MT md5c.lo -MD -MP -MF .deps/md5c.TPlo -fPIC -DPIC -o .libs/md5c.lo
i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../lib -g -Wall -Wno-long-long -Werror -ansi -O2 -mtune=i686 -pipe -I.. -O2 -mtune=i686 -pipe -c md5c.c -MT md5c.lo -MD -MP -MF .deps/md5c.TPlo -o md5c.o >/dev/null 2>&1
mv -f .libs/md5c.lo md5c.lo
/bin/sh ../../libtool --mode=link i686-pc-linux-gnu-gcc -g -Wall -Wno-long-long -Werror -ansi -O2 -mtune=i686 -pipe -I.. -O2 -mtune=i686 -pipe -o libmd5.la md5c.lo -lz
rm -fr .libs/libmd5.la .libs/libmd5.* .libs/libmd5.*
ar cru .libs/libmd5.al md5c.lo
i686-pc-linux-gnu-ranlib .libs/libmd5.al
creating libmd5.la
(cd .libs && rm -f libmd5.la && ln -s ../libmd5.la libmd5.la)
make[3]: Leaving directory `/var/tmp/portage/unshield-0.2/work/unshield-0.2/lib/md5'
Making all in .
make[3]: Entering directory `/var/tmp/portage/unshield-0.2/work/unshield-0.2/lib'
source='bswap.c' object='bswap.lo' libtool=yes \
depfile='.deps/bswap.Plo' tmpdepfile='.deps/bswap.TPlo' \
depmode=gcc3 /bin/sh ../depcomp \
/bin/sh ../libtool --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -g -ansi -Wall -Wno-long-long -Werror -O2 -mtune=i686 -pipe -I.. -O2 -mtune=i686 -pipe -c -o bswap.lo `test -f 'bswap.c' || echo './'`bswap.c
source='directory.c' object='directory.lo' libtool=yes \
depfile='.deps/directory.Plo' tmpdepfile='.deps/directory.TPlo' \
depmode=gcc3 /bin/sh ../depcomp \
/bin/sh ../libtool --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -g -ansi -Wall -Wno-long-long -Werror -O2 -mtune=i686 -pipe -I.. -O2 -mtune=i686 -pipe -c -o directory.lo `test -f 'directory.c' || echo './'`directory.c
mkdir .libs
i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -g -ansi -Wall -Wno-long-long -Werror -O2 -mtune=i686 -pipe -I.. -O2 -mtune=i686 -pipe -c directory.c -MT directory.lo -MD -MP -MF .deps/directory.TPlo -fPIC -DPIC -o .libs/directory.lo
cc1: warnings being treated as errors
In file included from internal.h:17,
from directory.c:2:
cabfile.h:58: warning: 'packed' attribute ignored for field of type 'uint8_t[11u]'
cabfile.h:68: warning: 'packed' attribute ignored for field of type 'uint8_t[13u]'
cabfile.h:93: warning: 'packed' attribute ignored for field of type 'uint8_t[15u]'
cabfile.h:105: warning: 'packed' attribute ignored for field of type 'uint8_t[15u]'
cabfile.h:112: warning: 'packed' attribute ignored for field of type 'uint8_t[11u]'
cabfile.h:115: warning: 'packed' attribute ignored for field of type 'uint8_t'
make[3]: *** [directory.lo] Error 1
make[3]: *** Waiting for unfinished jobs....
rm -f .libs/bswap.lo
i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -g -ansi -Wall -Wno-long-long -Werror -O2 -mtune=i686 -pipe -I.. -O2 -mtune=i686 -pipe -c bswap.c -MT bswap.lo -MD -MP -MF .deps/bswap.TPlo -fPIC -DPIC -o .libs/bswap.lo
cc1: warnings being treated as errors
In file included from internal.h:17,
from bswap.c:2:
cabfile.h:58: warning: 'packed' attribute ignored for field of type 'uint8_t[11u]'
cabfile.h:68: warning: 'packed' attribute ignored for field of type 'uint8_t[13u]'
cabfile.h:93: warning: 'packed' attribute ignored for field of type 'uint8_t[15u]'
cabfile.h:105: warning: 'packed' attribute ignored for field of type 'uint8_t[15u]'
cabfile.h:112: warning: 'packed' attribute ignored for field of type 'uint8_t[11u]'
cabfile.h:115: warning: 'packed' attribute ignored for field of type 'uint8_t'
make[3]: *** [bswap.lo] Error 1
make[3]: Leaving directory `/var/tmp/portage/unshield-0.2/work/unshield-0.2/lib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/unshield-0.2/work/unshield-0.2/lib'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/portage/unshield-0.2/work/unshield-0.2/lib'
make: *** [all-recursive] Error 1
!!! ERROR: app-arch/unshield-0.2 failed.
Call stack:
ebuild.sh, line 1539: Called dyn_compile
ebuild.sh, line 939: Called src_compile
ebuild.sh, line 609: Called die
!!! emake failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
|
non riesco neanche ad individuare il punto preciso dove indica l'errore e non so' se tutti quei warning sono normali ...
grazie in anticipo ^^ _________________ > Ai geek piace pensare di poter ignorare la politica; potete lasciarla stare, ma la politica non vi lascerà in pace.
Last edited by Gaap on Thu Sep 07, 2006 9:14 am; edited 1 time in total |
|
Back to top |
|
|
.:deadhead:. Advocate
Joined: 25 Nov 2003 Posts: 2963 Location: Milano, Italy
|
|
Back to top |
|
|
Gaap Apprentice
Joined: 28 Jul 2005 Posts: 276
|
Posted: Tue Sep 05, 2006 9:59 pm Post subject: |
|
|
Ho cercato nel forum ma niente bugzilla.. continuo la ricerca, intanto chiedo sempre una mano
p.s. non so' come funzionano le ricerche in bugzilla .. _________________ > Ai geek piace pensare di poter ignorare la politica; potete lasciarla stare, ma la politica non vi lascerà in pace. |
|
Back to top |
|
|
.:chrome:. Advocate
Joined: 19 Feb 2005 Posts: 4588 Location: Brescia, Italy
|
Posted: Tue Sep 05, 2006 11:33 pm Post subject: Re: Problemi in emerge unshield |
|
|
io proverei una delle versioni in testing. anche la 0.4 ad esempio
molti programmi scazzano con gcc-4, e nelle nuove versioni sono spesso presenti correzioni per il nuovo compilatore |
|
Back to top |
|
|
Gaap Apprentice
Joined: 28 Jul 2005 Posts: 276
|
Posted: Thu Sep 07, 2006 9:14 am Post subject: |
|
|
Problema superato con la versione 0.5 _________________ > Ai geek piace pensare di poter ignorare la politica; potete lasciarla stare, ma la politica non vi lascerà in pace. |
|
Back to top |
|
|
|