Bug 4097 - Build failure
Summary: Build failure
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
Depends on:
Blocks: 1839
  Show dependency treegraph
Reported: 2007-02-24 22:48 UTC by Jan Kratochvil
Modified: 2007-03-12 12:31 UTC (History)
0 users

See Also:
Host: i686-pc-linux-gnu
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Jan Kratochvil 2007-02-24 22:48:06 UTC

gcj -I../../frysk/frysk-imports -I. -Igetopt.jar -Ijunit.jar -Werror -Wall -fPIC
 -ggdb2   -o fryski   libfrysk-imports.so  libfrysk-getopt.so  libfrysk-junit.so
libfrysk-imports.a libfrysk-getopt.a libfrysk-junit.a
./elfutils/libdwfl/libdwfl.a ./elfutils/libdw/libdw.a ./elfutils/libebl/libebl.a
./elfutils/libelf/libelf.a -lstdc++ ./libunwind/src/libunwind-ptrace.a
./libunwind/src/libunwind-x86.a -laudit -lopcodes -L./lib/opcodes -lbfd_get 
./libunwind/src/libunwind-x86.a(Gresume.o): In function `_Ux86_local_resume':
warning: warning: sigreturn is not implemented and will always fail
/usr/lib/gcc/i386-redhat-linux/4.1.2/../../../crt1.o: In function `_start':
(.text+0x18): undefined reference to `main'
collect2: ld returned 1 exit status
make[3]: *** [fryski] Error 1
make[3]: Leaving directory `/home/jkratoch/redhat/frysk-build/frysk-imports'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/jkratoch/redhat/frysk-build/frysk-imports'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/jkratoch/redhat/frysk-build/frysk-imports'
make: *** [all-recursive] Error 1
Comment 1 Jan Kratochvil 2007-03-07 23:58:38 UTC
It now builds but there is needed the mjw's patch from:
Comment 2 Mark Wielaard 2007-03-12 12:31:03 UTC
I added a configure check to see if -Wall is supported. Together with Kris
recent work you should now be able to simple build with ../frysk/autogen.sh

Next up is waiting for -Wall to be fixed in rawhide and seeing which warning
flags really make sense for our code base.