[LLVMdev] Changes to Debian's linker object files breaks building LLVM [crti.o, crt1.o, crtn.o]

Eli Friedman eli.friedman at gmail.com
Wed Aug 24 19:15:50 PDT 2011


On Wed, Aug 24, 2011 at 6:36 PM, Marc J. Driftmeyer <mjd at reanimality.com> wrote:
> I've got a simple workaround which obviously everyone will figure out:
>
> mdriftmeyer at horus:/usr/lib$ sudo ln -s x86_64-linux-gnu/crti.o crti.o
> mdriftmeyer at horus:/usr/lib$ sudo ln -s x86_64-linux-gnu/crt1.o crt1.o
> mdriftmeyer at horus:/usr/lib$ sudo ln -s x86_64-linux-gnu/crtn.o crtn.o
>
> My real question concerns whether or not I should file a bug report against
> Debian not having a transition path or other means in Debian's
> update-alternatives infrastructure to update those paths and make them
> available system-wide or whether LLVM needs to be aware of this move and
> update autotools configurations files for make to traverse.

clang currently has some extremely ugly hacks to figure out how to
link a program under Linux, and they tend to frequently break; see
lib/Driver/ToolChains.cpp in clang.  I think there's been some
discussion of trying to do something more sane, but nobody has stepped
up to do the work.

-Eli



More information about the llvm-dev mailing list