This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ct-ng: CLooG link failure in canadian-cross context


Bwrnhard, All,

On Wednesday 28 July 2010 11:51:54 Bernhard Pfund wrote:
> I'm trying to create a powerpc-e500v2-linux-uclibcspe toolchain for a Windows 
> host, using the canadian build-mode from ct-ng (hg tree from July 26.). I've
> successfully built the Linux host version and the additional i686-pc-mingw32
> chain, but now I'm stuck with a CLooG linker failure in step 3. of Yann's 
> 'recipe' for canadian builds:
[--SNIP--]
> For some reason the linker is looking for c++ interfaces in libppl_c.a, which is 
> IMO obviously bound to go wrong. Anyone seen this behaviour before?
> Any hints greatly appreciated!

> [Canadian config powerpc-e500v2Can-linux-uclibcspe]

I'll come back to that later, when I have time to look at it.
I'm afraid it won't be before the WE, as I'm trying to get 1.8.0 out
in time (saturday if I stick to the plan).

> P.S. I had to modify ct-ng to get the uclibcspe configuration to work in the 
> first place, but I can't see any relation to the error I'm experiencing now.

> [QUICK AND DIRTY HACKS]
> --- gcc.sh_sav  2010-07-26 15:54:10.000000000 +0200
> +++ gcc.sh      2010-07-26 15:55:54.000000000 +0200
[--SNIP libmudflap--]

Nice idea. I've turned that into a config knob: build libmudflap or not?

> --- powerpc.sh_sav      2010-07-28 11:49:09.000000000 +0200
> +++ powerpc.sh  2010-07-26 14:35:20.000000000 +0200
> @@ -10,6 +10,10 @@
>       case "${CT_LIBC},${CT_ARCH_POWERPC_SPE}" in
>           glibc,|eglibc,)   CT_TARGET_SYS=gnu;;
>           glibc,y|eglibc,y) CT_TARGET_SYS=gnuspe;;
> +        uClibc) CT_TARGET_SYS=uclibc;;
> +        uClibc,y) CT_TARGET_SYS=uclibcspe;;
> +        newlib) CT_TARGET_SYS=elf;;
> +        newlib,y) CT_TARGET_SYS=elfspe;;

Are you sure about the uclibcspe thing? If I refer to the ARM EABI case,
the correct tuple ends in -uclibcgnueabi. And if we follow that for
the PPC SPE case, then we'd get -uclibcgnuspe. As for elfspe, do we
really expect people to run bare-metal on such a machine ?

> [Config powerpc-e500v2-linux-uclibcspe]

Oh, you did build that one successfully, didn't you? So it seems the
uclibcspe stuff is correct, then. Hmmm. Debian is doing that as well:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575158

So OK. Let's queue that for after 1.8.0...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'



--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]