Skip to content

Should we link to libm? #601

@KristofferC

Description

@KristofferC

Looking at the sysimage that comes with julia, it links with libm:

❯ ldd sys.so 
        linux-vdso.so.1 (0x00007ffe7819d000)
        libjulia-internal.so.1 => not found
        libjulia.so.1 => not found
        libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f4147fa7000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4147e59000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f4147e3e000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4147c52000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f4151a29000)

But the ones from PackageCompiler does not:

❯ ldd sys.so # PackageCompiler sysimage
        linux-vdso.so.1 (0x00007fff7b6e7000)
        libjulia-internal.so.1 => not found
        libjulia.so.1 => not found
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa75e9de000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fa76790c000)

Perhaps this is the cause of https://discourse.julialang.org/t/packagecompiler-create-app-function-failing-on-slurm-cluster-error-undefined-reference-to-ceil/69344? We should figure out what causes the difference is between the sysimage provided by PackageCompiler and the official distribution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions