Menu ▾ ▴

#220 e2fsprogs fails to compile with non-standard GCC patch

closed-wont-fix
nobody
None
5
2008-08-22
2008-07-23
Magnus Granberg
No

On x86_64
/usr/lib/gcc/x86_64-pc-linux-gnu/4.2.3/../../../../x86_64-pc-linux-gnu/bin/ld:
../../lib/libuuid.a(gen_uuid.o): relocation R_X86_64_TPOFF32 against `a local
symbol' can not be used when making a shared object; recompile with -fPIC
../../lib/libuuid.a: could not read symbols: Bad value collect2: ld returnerade
avslutningsstatus 1 make[2]: *** [tst_uuid] Fel 1
On x86
sandra uuid # scanelf -a tst_uuid
TYPE PAX PERM ENDIAN STK/REL/PTL TEXTREL RPATH BIND FILE
ET_DYN ---xe- 0755 LE RW- R-- RW- TEXTREL - NOW tst_uuid
sandra uuid #
The package will fail on the new gcc 4.x Gentoo hardened toolchain when it moves upstrem.
e2fsprogs 1.41 have the bug to.
static libs need to be linkt whit -fPIC
more info
http://bugs.gentoo.org/show_bug.cgi?id=232601

Discussion

  • Magnus Granberg

    Magnus Granberg - 2008-07-23

    make static libs link whit -fPIC

     
    e2fsprogs-make-libs.a-fpic.patch

  • Theodore Ts'o

    Theodore Ts'o - 2008-07-23

    Logged In: YES
    user_id=628
    Originator: NO

    This is a problem that is caused by a non-standard gcc, I take it. "This hardened GCC" is a non-standard patch which is not in the upstream gcc, right?

    In that case, why should all e2fsprogs users suffer with a slowdown caused by a reduction of the x86's pathetically small register file by another 25%? If Gentoo wants to use this non-standard GCC patch, then let it carry this patch....

    The only way I can see taking this patch in e2fsprogs upstream is if it is an configure option, ideally one with a test that can detect the use of this non-standard gcc patch.

     

  • Theodore Ts'o

    Theodore Ts'o - 2008-07-23
    • summary: [PATCH] sys-fs/e2fsprogs-1.4X.X fails to compile on x86_64 --> e2fsprogs fails to compile with non-standard GCC patch
     

  • Theodore Ts'o

    Theodore Ts'o - 2008-08-22
    • status: open --> closed-wont-fix