Displaying 5 results from an estimated 5 matches for "tartget".
Did you mean:
target
2009 Aug 04
0
[LLVMdev] llvm-gcc-4.2-2.5 fails to build from source on arm: MACHO_DYNAMIC_NO_PIC_P undeclared
...e a big help to all the distro maintainers.
You might want to stick with next 2.6 release, which is scheduled to
be out within next 1.5 months
I would like to comment on some other bugs as well:
478535: there are no plans to support of legacy IBM S390 platform,
only 64 bit one (that's s390x in tartget triple). The current plans
are to use clang only, not llvm-gcc, however I might be able to find
few hours to give llvm-gcc a try.
539496: There are no plans to support ARMv4 in LLVM. As for ToT ARM
builds of llvm-gcc (both for bare-metal arm-elf and normal
arm-none-linux-gnueabi triples) is broken...
2009 Aug 04
3
[LLVMdev] llvm-gcc-4.2-2.5 fails to build from source on arm: MACHO_DYNAMIC_NO_PIC_P undeclared
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
2009 Aug 21
0
[LLVMdev] llvm-gcc-4.2-2.5 fails to build from source on arm: MACHO_DYNAMIC_NO_PIC_P undeclared
...You might want to stick with next 2.6 release, which is scheduled to
>> be out within next 1.5 months
>>
>> I would like to comment on some other bugs as well:
>> 478535: there are no plans to support of legacy IBM S390 platform,
>> only 64 bit one (that's s390x in tartget triple). The current plans
>> are to use clang only, not llvm-gcc, however I might be able to find
>> few hours to give llvm-gcc a try.
>> 539496: There are no plans to support ARMv4 in LLVM. As for ToT ARM
>> builds of llvm-gcc (both for bare-metal arm-elf and normal
>&g...
2009 Aug 19
5
[LLVMdev] llvm-gcc-4.2-2.5 fails to build from source on arm: MACHO_DYNAMIC_NO_PIC_P undeclared
...o maintainers.
> You might want to stick with next 2.6 release, which is scheduled to
> be out within next 1.5 months
>
> I would like to comment on some other bugs as well:
> 478535: there are no plans to support of legacy IBM S390 platform,
> only 64 bit one (that's s390x in tartget triple). The current plans
> are to use clang only, not llvm-gcc, however I might be able to find
> few hours to give llvm-gcc a try.
> 539496: There are no plans to support ARMv4 in LLVM. As for ToT ARM
> builds of llvm-gcc (both for bare-metal arm-elf and normal
> arm-none-linux-gn...
2009 Aug 21
1
[LLVMdev] llvm-gcc-4.2-2.5 fails to build from source on arm: MACHO_DYNAMIC_NO_PIC_P undeclared
...ick with next 2.6 release, which is scheduled to
>>> be out within next 1.5 months
>>>
>>> I would like to comment on some other bugs as well:
>>> 478535: there are no plans to support of legacy IBM S390 platform,
>>> only 64 bit one (that's s390x in tartget triple). The current plans
>>> are to use clang only, not llvm-gcc, however I might be able to find
>>> few hours to give llvm-gcc a try.
>>> 539496: There are no plans to support ARMv4 in LLVM. As for ToT ARM
>>> builds of llvm-gcc (both for bare-metal arm-elf a...