Closed boegel closed 8 years ago
I'm seeing unexpected output when running gcc when XALT is active, looks like debug printing somewhere in XALT:
gcc
$ ml Currently Loaded Modules: 1) cluster/swalot (S) 5) ifort/2016.1.150-GCC-4.9.3-2.25 9) imkl/11.3.1.150-iimpi-8.1.5-GCC-4.9.3-2.25 13) libreadline/6.3-intel-2016a 17) Tk/8.6.4-intel-2016a-no-X11 2) GCCcore/4.9.3 6) iccifort/2016.1.150-GCC-4.9.3-2.25 10) intel/2016a 14) ncurses/6.0-intel-2016a 18) GMP/6.1.0-intel-2016a 3) binutils/2.25-GCCcore-4.9.3 7) impi/5.1.2.150-iccifort-2016.1.150-GCC-4.9.3-2.25 11) bzip2/1.0.6-intel-2016a 15) Tcl/8.6.4-intel-2016a 19) Python/3.5.1-intel-2016a 4) icc/2016.1.150-GCC-4.9.3-2.25 8) iimpi/8.1.5-GCC-4.9.3-2.25 12) zlib/1.2.8-intel-2016a 16) SQLite/3.9.2-intel-2016a 20) XALT/1.5.1-devel Where: S: Module is Sticky, requires --force to unload or purge $ which gcc /apps/gent/CO7/haswell-ib/software/GCCcore/4.9.3/bin/gcc $ which ld.gold /user/scratch/gent/vsc400/vsc40023/easybuild_REGTEST/CO7/haswell-ib/software/XALT/1.5.1-devel/bin/ld.gold $ gcc ~/hello.c /lib/../lib64/crt1.o /lib/../lib64/crti.o /vscmnt/gent_vulpix_apps/_apps_gent/CO7/haswell-ib/software/GCCcore/4.9.3/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.9.3/crtbegin.o /tmp/ccDtoUHd.o /apps/gent/CO7/haswell-ib/software/GCCcore/4.9.3/lib64/../lib64/libgcc_s.so /lib64/libc.so.6 /usr/lib64/libc_nonshared.a(elf-init.oS) /lib64/ld-linux-x86-64.so.2 /apps/gent/CO7/haswell-ib/software/GCCcore/4.9.3/lib64/../lib64/libgcc_s.so /vscmnt/gent_vulpix_apps/_apps_gent/CO7/haswell-ib/software/GCCcore/4.9.3/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.9.3/crtend.o /lib/../lib64/crtn.o /tmp/vsc40023_2016_06_24_12_35_53_d6264aa5-3ee7-4171-91ee-598a75b2b4f8/xalt.o /user/scratch/gent/vsc400/vsc40023/easybuild_REGTEST/CO7/haswell-ib/software/XALT/1.5.1-devel/lib64/xalt_initialize.o /user/scratch/gent/vsc400/vsc40023/easybuild_REGTEST/CO7/haswell-ib/software/XALT/1.5.1-devel/lib64/xalt_syshost.o /user/scratch/gent/vsc400/vsc40023/easybuild_REGTEST/CO7/haswell-ib/software/XALT/1.5.1-devel/lib64/xalt_quotestring.o /user/scratch/gent/vsc400/vsc40023/easybuild_REGTEST/CO7/haswell-ib/software/XALT/1.5.1-devel/lib64/xalt_fgets_alloc.o
fixed in cb718f1d7a3ee1968884c7aa5504e2fa42db4d2d by @rtmclay, thanks!
I'm seeing unexpected output when running
gcc
when XALT is active, looks like debug printing somewhere in XALT: