1275218 - Linux64 build busted @ compile :

Status: RESOLVED WORKSFORME

(SeaMonkey :: Build Config, defect)

Description

[Edmund Wong (:ewong)]

Compile step busted:

   INPUT("../../modules/zlib/src/infback.o")
    INPUT("../../modules/zlib/src/inffast.o")
    INPUT("../../modules/zlib/src/inflate.o")
    INPUT("../../modules/zlib/src/inftrees.o")
    INPUT("../../modules/zlib/src/trees.o")
    INPUT("../../modules/zlib/src/uncompr.o")
    INPUT("../../modules/zlib/src/zutil.o")
    INPUT("StaticXULComponentsEnd/StaticXULComponentsEnd.o")

/builds/slave/c-aurora-lnx64/build/gcc/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.8.5/../../../../x86_64-unknown-linux-gnu/bin/ld: /lib64/libz.so.1: no version information available (required by /builds/slave/c-aurora-lnx64/build/gcc/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.8.5/../../../../x86_64-unknown-linux-gnu/bin/ld)
/builds/slave/c-aurora-lnx64/build/gcc/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.8.5/../../../../x86_64-unknown-linux-gnu/bin/ld: ../../js/src/libjs_static.a(closures.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
../../js/src/libjs_static.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
make[4]: *** [libxul.so] Error 1


Not sure what it is though.  But there's a sprinkling of warnings during
the compile step:

/builds/slave/c-aurora-lnx64/build/gcc/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.8.5/../../../../x86_64-unknown-linux-gnu/bin/as: /lib64/libz.so.1: no version information available (required by /builds/slave/c-aurora-lnx64/build/gcc/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.8.5/../../../../x86_64-unknown-linux-gnu/bin/as)

Comment 1

[Adrian Kalla [:adriank]]

I've seen this many times - and in all cases what helped was to completely remove the build folder, so most like a cache issue...

Comment 2

[Frank-Rainer Grahl (:frg)]

Mentioned in the status meetings for ages now. Is this still a problem?

Comment 3

[Edmund Wong (:ewong)]

(In reply to Frank-Rainer Grahl (:frg) from comment #2)
> Mentioned in the status meetings for ages now. Is this still a problem?

No.. not at this moment.  It was an intermittent thing.  Closing this bug.