Summary: | sys-fs/zfs-fuse fails to compile (_FORTIFY_SOURCE) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ian Ballantyne <ian> |
Component: | [OLD] Core system | Assignee: | Christian Parpart (RETIRED) <trapni> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kolcon |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ian Ballantyne
2009-08-13 16:28:13 UTC
Just to make sure: -Werror comes from the package, not your CFLAGS, right ? It's not set in my make.conf, and it's not in the environment when I build: bandicoot2 ~ # env | grep -i error bandicoot2 ~ # echo $CFLAGS bandicoot2 ~ # emerge -v --tree -a zfs-fuse 8<--- failed build bandicoot2 ~ # grep -i error /etc/make.conf PORTAGE_ELOG_CLASSES="warn error log" bandicoot2 ~ # grep FLA /etc/make.conf CFLAGS="-march=k8 -O3 -pipe" CXXFLAGS="-O3 -pipe" bandicoot2 ~ # cd /var/tmp/portage/sys-fs/zfs-fuse-0.5.0/work/zfs-fuse-0.5.0/src bandicoot2 src # grep -rl Werror . ./SConstruct bandicoot2 src # grep Werror SConstruct env['LINKFLAGS'] = Split('-pipe -Wall -Werror') env['CCFLAGS'] = Split('-pipe -Wall -Werror -std=c99 -Wno-switch -Wno-unused -Wno-missing-braces -Wno-parentheses -Wno-uninitialized -fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DTEXT_DOMAIN=\\"zfs-fuse\\" -DLINUX_AIO') So -Werror seems it's coming from the package... or do I interpret something wrong? Just as a test, I started the emerge stopping the build with ctrl-z before the compilation started. I edited the SConstruct file and removed the -Werror from both LINKFLAGS and CCFLAGS (ok, I know this is not really the right way, but as a quick test, it's sufficient for me), then allowed the build to continue. It ran through without problems. bandicoot2 ~ # emerge -v --tree -a sys-fs/zfs-fuse * IMPORTANT: 3 news items need reading for repository 'gentoo'. * Use eselect news to read news items. These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild N ] sys-fs/zfs-fuse-0.5.0 USE="-debug -doc" 0 kB Total: 1 package (1 new), Size of downloads: 0 kB Would you like to merge these packages? [Yes/No] y >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-fs/zfs-fuse-0.5.0 * zfs-fuse-0.5.0.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking zfs-fuse-0.5.0.tar.bz2 to /var/tmp/portage/sys-fs/zfs-fuse-0.5.0/work * Applying fix_zdb_path.patch ... [ ok ] * Applying fix_zfs-fuse_path.patch ... [ ok ] * Applying fix_ztest_path.patch ... [ ok ] >>> Source unpacked in /var/tmp/portage/sys-fs/zfs-fuse-0.5.0/work ^Z [2]+ Stopped emerge -v --tree -a sys-fs/zfs-fuse bandicoot2 ~ # vim /var/tmp/portage/sys-fs/zfs-fuse-0.5.0/work/zfs-fuse-0.5.0/src/SConstruct bandicoot2 ~ # fg emerge -v --tree -a sys-fs/zfs-fuse >>> Compiling source in /var/tmp/portage/sys-fs/zfs-fuse-0.5.0/work/zfs-fuse-0.5.0/src ... scons: Reading SConscript files ... scons: done reading SConscript files. scons: Building targets ... 8<--- successful build and install Now there is a plethora of other problems, such as error messages, a zpool that I can't mount, and so on, however I will investigate and report these to the developers of zfs-fuse. *** This bug has been marked as a duplicate of bug 260941 *** |