mldonkey on gentoo (not compiling)


Results 1 to 6 of 6

Thread: mldonkey on gentoo (not compiling)

  1. #1
    Join Date
    Mar 2003
    Location
    West Texas
    Posts
    586

    mldonkey on gentoo (not compiling)

    emerging mldonkey

    dies on package 'lablgtk-1.2.5'

    gcc 3.3.4 20040623 (Gentoo Linux 3.3.4-r1)
    glibc 2.3.4-20040808-r1

    heres the error:

    ocamlc.opt -I /usr/lib/ocaml/lablGL -w s -c gtkInit.ml
    ocamlmktop -I /usr/lib/ocaml/lablGL -o lablgtktop unix.cma str.cma lablgl.cma -I . lablgtk.cma lablgtkgl.cma lablgnome.cma lablglade.cma gtkInit.cmo
    Error on dynamically loaded library: libnvidia-tls.so.1: cannot handle TLS data
    make[1]: *** [lablgtktop] Error 2
    rm varcc.ml
    make[1]: Leaving directory `/var/tmp/portage/lablgtk-1.2.5/work/lablgtk-1.2.5/src'
    make: *** [all] Error 2

    !!! ERROR: dev-ml/lablgtk-1.2.5 failed.
    !!! Function src_compile, Line 35, Exitcode 2
    !!! (no error message)
    !!! If you need support, post the topmost build error, NOT this status message.
    JustLinux IRC Channel: irc.freenode.net #justlinux

  2. #2
    Join Date
    Nov 2004
    Posts
    2
    you can try with:

    export LD_ASSUME_KERNEL=2.3.98

    and then emerging mldonkey.

  3. #3
    Join Date
    Mar 2003
    Location
    West Texas
    Posts
    586
    Originally posted by markel
    you can try with:

    export LD_ASSUME_KERNEL=2.3.98

    and then emerging mldonkey.
    what will that do?
    JustLinux IRC Channel: irc.freenode.net #justlinux

  4. #4
    Join Date
    Aug 2004
    Location
    Salem, OR
    Posts
    368
    emerge --inject dev-ml/lablgtk-1.2.5 this will hide the conflicting package from portage. Then emerge mldonkey.
    Registered Linux User #365191

  5. #5
    Join Date
    Nov 2004
    Posts
    2
    The problem is located in the nvidia tls nvidia library that doesn't support the new tls implementation (glibc 2.3)
    a little explanation of the LD_ASSUME_KERNEL

    the LD_ASSUME_KERNEL is an environment variable (is not hardcoded) used by ld,
    every shared library can tell the ld in glibc which minimum OS ABI (Application Binary Interface) version is needed.
    The information about the minimum OS ABI version is encoded in a ELF (you can see it with 'readelf -an ./test |grep -i abi')


    from the NVIDIA README guidelines driver:

    Q: I want to use Valgrind with OpenGL applications, but my
    distribution uses ELF TLS, and Valgrind cannot yet deal with NVIDIA's
    ELF TLS OpenGL.

    A: You can set the environment variable LD_ASSUME_KERNEL to something
    below "2.3.99" (for example: `export LD_ASSUME_KERNEL 2.3.98`).

    NVIDIA's OpenGL libraries contain an OS ABI ELF note that indicates
    the minimum kernel version that is required to use the library.

    The ELF TLS OpenGL libraries have an OS ABI of 2.3.99 (the first
    Linux kernel that contained the necessary LDT support for ELF TLS),
    while the non ELF TLS OpenGL libraries contain an OS ABI of 2.2.5.

    The run-time loader will not load libraries with an OS ABI greater
    than the current kernel version. The LD_ASSUME_KERNEL environment
    variable can be used to override the kernel version that the run-time
    loader uses in this test.

    By setting LD_ASSUME_KERNEL to any kernel version below 2.3.99,
    you can force the loader to not use the ELF TLS OpenGL libraries,
    and fall back to the regular OpenGL libraries.

    If, for some reason, you need to remove this OS ABI note from the
    NVIDIA OpenGL libraries, you can do so by passing the .run file the
    "--no-abi-note" option during installation.



    Marcello

  6. #6
    Join Date
    Mar 2003
    Location
    West Texas
    Posts
    586
    thanks markel, when i dont have to run to work, ill try it
    JustLinux IRC Channel: irc.freenode.net #justlinux

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •