is it a fresh build or rebuild over an already built tree? avati 2008/6/19 Mateusz Korniak <mateusz-lists@xxxxxxxxxxxxxx>: > Hi > after gcc upgrade to (4.2.3->4.2.4) glusterfs-1.3.9 fails to build [1]: > Full log: > > http://buildlogs.pld-linux.org/index.php?dist=th&arch=i686&ok=0&name=glusterfs > Any hints ? > > Regards, TIA > > [1]: > make[2]: Entering directory > `/home/users/matkor/rpm/BUILD/glusterfs-1.3.9/xlators' > Making all in cluster > make[3]: Entering directory > `/home/users/matkor/rpm/BUILD/glusterfs-1.3.9/xlators/cluster' > Making all in unify > make[4]: Entering directory > `/home/users/matkor/rpm/BUILD/glusterfs-1.3.9/xlators/cluster/unify' > Making all in src > make[5]: Entering directory > `/home/users/matkor/rpm/BUILD/glusterfs-1.3.9/xlators/cluster/unify/src' > athlon-pld-linux-gcc -DHAVE_CONFIG_H -I. -I../../../.. -fPIC > -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall -DGF_LINUX_HOST_OS > -I../../../../libglusterfs/src -shared -nostartfiles -O2 > -fno-strict-aliasing -fwrapv -march=athlon -gdwarf-2 -g2 -MT > unify.o -MD -MP -MF .deps/unify.Tpo -c -o unify.o unify.c > mv -f .deps/unify.Tpo .deps/unify.Po > athlon-pld-linux-gcc -DHAVE_CONFIG_H -I. -I../../../.. -fPIC > -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall -DGF_LINUX_HOST_OS > -I../../../../libglusterfs/src -shared -nostartfiles -O2 > -fno-strict-aliasing -fwrapv -march=athlon -gdwarf-2 -g2 -MT > unify-self-heal.o -MD -MP -MF .deps/unify-self-heal.Tpo -c -o > unify-self-heal.o unify-self-heal.c > mv -f .deps/unify-self-heal.Tpo .deps/unify-self-heal.Po > /bin/sh ../../../../libtool --tag=CC --mode=link > athlon-pld-linux-gcc -fPIC -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall > -DGF_LINUX_HOST_OS -I../../../../libglusterfs/src -shared -nostartfiles -O2 > -fno-strict-aliasing -fwrapv -march=athlon -gdwarf-2 -g2 -Wl,--as-needed > -Wl,-z,relro -Wl,-z,-combreloc -o > unify.so unify.o unify-self-heal.o -ldl -lpthread > libtool: link: > athlon-pld-linux-gcc -fPIC -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall > -DGF_LINUX_HOST_OS -I../../../../libglusterfs/src -nostartfiles -O2 > -fno-strict-aliasing -fwrapv -march=athlon -gdwarf-2 -g2 -Wl,--as-needed > -Wl,-z -Wl,relro -Wl,-z -Wl,-combreloc -o > unify.so unify.o unify-self-heal.o -ldl -lpthread > /usr/bin/ld: warning: cannot find entry symbol _start; defaulting to > 0000000008049400 > unify.o: In function `unify_rmelem': > > /home/users/matkor/rpm/BUILD/glusterfs-1.3.9/xlators/cluster/unify/src/unify.c:3927: > undefined reference to `gf_log_loglevel' > > /home/users/matkor/rpm/BUILD/glusterfs-1.3.9/xlators/cluster/unify/src/unify.c:3927: > undefined reference to `_gf_log' > (...) > > /home/users/matkor/rpm/BUILD/glusterfs-1.3.9/xlators/cluster/unify/src/unify-self-heal.c:82: > undefined reference to `fd_destroy' > collect2: ld returned 1 exit status > make[5]: *** [unify.so] Error 1 > make[5]: Leaving directory > `/home/users/matkor/rpm/BUILD/glusterfs-1.3.9/xlators/cluster/unify/src' > make[4]: *** [all-recursive] Error 1 > make[4]: Leaving directory > `/home/users/matkor/rpm/BUILD/glusterfs-1.3.9/xlators/cluster/unify' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory > `/home/users/matkor/rpm/BUILD/glusterfs-1.3.9/xlators/cluster' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory > `/home/users/matkor/rpm/BUILD/glusterfs-1.3.9/xlators' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/users/matkor/rpm/BUILD/glusterfs-1.3.9' > make: *** [all] Error 2 > error: Bad exit status from /home/users/matkor/tmp/rpm-tmp.39883 (%build) > > > -- > Mateusz Korniak > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel > -- If I traveled to the end of the rainbow As Dame Fortune did intend, Murphy would be there to tell me The pot's at the other end.
