llvm dev - Aug 2009 - [LLVMdev] llvm-gcc-4.2-2.5 fails to build from source on arm: MACHO_DYNAMIC_NO_PIC_P undeclared

Thanks. Do you have fixes for the other ARM bloopers? This is the
forthcoming Debian version and it's now dying on arm-gnueabi when it
links cc2-dummy saying

libbackend.a(arm.o): In function `current_file_function_operand':
/home/martin/arm/llvm-gcc-4.2-2.5/build-gcc/gcc/../../llvm-gcc-4.2-2.5/gcc/config/arm/arm.c:3506:
undefined reference to `ENCODED_SHORT_CALL_ATTR_P'
libbackend.a(arm.o): In function `arm_is_longcall_p':
/home/martin/arm/llvm-gcc-4.2-2.5/build-gcc/gcc/../../llvm-gcc-4.2-2.5/gcc/config/arm/arm.c:3581:
undefined reference to `ENCODED_LONG_CALL_ATTR_P'
collect2: ld returned 1 exit status

cheers

   M

Hello, Martin
> Thanks. Do you have fixes for the other ARM bloopers? This is the
> forthcoming Debian version and it's now dying on arm-gnueabi when it
> links cc2-dummy saying
Please use the current Top-of-the-Tree version. I was successfully
built cross llvm-gcc for arm-elf / arm-gnu-linux-eabi target triples.

-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University

On 8/3/09, Anton Korobeynikov <anton at korobeynikov.info>
wrote:
>  > Thanks. Do you have fixes for the other ARM bloopers? This is the
>  > forthcoming Debian version and it's now dying on arm-gnueabi when
it
>  > links cc1-dummy saying
>
> Please use the current Top-of-the-Tree version.
Sorry, that's not an option as I'm trying to fix the Debian version,
which uses "stable" releases. Each Debian build takes 6 hours, so
finding and fixing these bugs one by one is quite a long process.

llvm-gcc-4.2-2.5 is failing to build from source on arm, sparc,
powerpc and ia64, only succeeding on i386 and amd64:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=llvm-gcc-4.2;dist=unstable
so it looks like the 2.5 release was never properly tested before it
was published.

If the issues and fixes are "known", can you make them known to the
public, for example by producing a 2.5.1 with the worst bugs fixed, or
by documenting the issues and patches in the "Known problems" section?
It would be a big help to all the distro maintainers.

Thanks & sorry to be the bringer of bad news...

   M