Bug#596970: clang: can't link after compiling with -O4

Salvo Tomaselli tiposchi at tiscali.it
Wed Sep 15 14:03:30 UTC 2010


Package: clang
Version: 2.7-3
Severity: normal

clang's manpage shows that -O4 is an optimization level to perform link time
optimizations.
To do this, the .o files are in truth LLVM bytecode and at link time the linker
should put them together, perform the optimizations and generate the binary.
Unfortunately the linker seems to expect .o files to be ELF files, so it refuses
to link.

Since clang seems to aim to be compatible with gcc, i guess that changing only
the compiler and the optimization level in the makefile should produce a binary
anyway.

Bye


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'experimental'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.34.6-era (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages clang depends on:
ii  libc6                         2.11.2-6   Embedded GNU C Library: Shared lib
ii  libffi5                       3.0.9-2    Foreign Function Interface library
ii  libgcc1                       1:4.4.4-14 GCC support library
ii  libstdc++6                    4.4.4-14   The GNU Standard C++ Library v3

Versions of packages clang recommends:
pn  llvm-2.7-dev                  <none>     (no description available)
ii  python                        2.6.6-1    interactive high-level object-orie

clang suggests no packages.

-- no debconf information





More information about the Pkg-llvm-team mailing list