Re: Multilib problem

[Bryan Hundven <bryanhundven at gmail dot com>]

eh,

On Mon, Feb 3, 2014 at 5:11 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
> Danny, list,
>
> On Mon, Feb 3, 2014 at 5:08 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
>> The notice in your email caused me some problems.
>>
>> My message was (with the notice removed):
>>
>> On Mon, Feb 3, 2014 at 5:04 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
>>> Danny,
>>>
>>> On Mon, Feb 3, 2014 at 4:59 PM, Danny Gale
>>> <Daniel.Gale@coloradoengineeringinc.com> wrote:
>>>> We do have another build system on top of CT-NG that pulls it down, patches
>>>> it as necessary, and shoves our configration where it needs to be. Those
>>>> tags you see, like [WORK_DIR], are replaced before we invoke CT-NG.
>>>
>>> Ah, ok. I'll look at the build log again :)
>>>
>>>> The arch-suffix of -e6500 results in "powerpc64-e6500-linux-gnu", which
>>>> seems reasonable to me.
>>>
>>> You should use CT_TARGET_VENDOR instead.
>>>
>>>>
>>>>
>>>> On Monday, February 03, 2014 5:39:29 PM, Bryan Hundven wrote:
>>>>>
>>>>>
>>>>> Hello, Daniel, all,
>>>>>
>>>>> On Thu, Jan 23, 2014 at 2:37 PM, Danny Gale
>>>>> <Daniel.Gale@coloradoengineeringinc.com> wrote:
>>>>>>
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I've successfully compiled my powerpc64-e6500-linux-gnu toolchain!
>>>>>> Hooray!
>>>>>> :)
>>>>>>
>>>>>> Now, the trouble is that U-Boot doesn't support 64-bit powerpc builds, so
>>>>>> the toolchain needs to have multilib enabled. The compiler itself is
>>>>>> built
>>>>>> with no problem, but during the "Building for multilib subdir='32'" step,
>>>>>> the build fails with this error:
>>>>>> [ALL ] ../sysdeps/powerpc/powerpc64/start.S: Assembler messages:
>>>>>> [ALL ] ../sysdeps/powerpc/powerpc64/start.S:50: Error: reloc 1 not
>>>>>> supported by object file format
>>>>>> [ALL ] ../sysdeps/powerpc/powerpc64/start.S:51: Error: reloc 1 not
>>>>>> supported by object file format
>>>>>> [ALL ] ../sysdeps/powerpc/powerpc64/start.S:52: Error: reloc 1 not
>>>>>> supported by object file format
>>>>>>
>>>>>> Those lines in that file look like this:
>>>>>> /* function descriptors so don't need JUMPTARGET */
>>>>>> .quad BP_SYM(main)
>>>>>> .quad __libc_csu_init
>>>>>> .quad __libc_csu_fini
>>>>>>
>>>>>> Anybody know what this could be about, and how to fix it?
>>>>>>
>>>>>> My config and the tail of my log are attached.
>>>>>>
>>>>>> Thanks for your help,
>>>>>> Danny
>>>>>
>>>>>
>>>>>
>>>>> I have some questions about your configuration.
>>>>>
>>>>> In your attached config.txt, you have things like:
>>>>>
>>>>> CT_WORK_DIR="[WORK_DIR]"
>>>>>
>>>>> and an arch suffix "-e6500" (iow: -e6500powerpc64-unknown-linux-gnu)
>>>>> doesn't really make sense to me.
>>>>>
>>>>> I'm surprised this config works at all.
>>>>>
>>>>> Are you making this config with another external tool, such as
>>>>> buildroot or a custom wrapper script? That may make some of my
>>>>> confusion go away.
>>>>>
>>>>> -Bryan
>>>>>
>>>>> (PS, I have an updated config I'll post after I test it.)
>>>>>
>>>>> --
>>>>> Danny Gale
>>>>> Engineer
>> ...
>
> Beyond that, with the attached config, I got the same failure.
> I think Cody is right about the arch name in the tuple.

Forgot to attach. I know that some of the settings are wrong, and I
need to add them from your build log, so: v1

> I'm gonna poke at this for a second.
>
> -Bryan

Attachment: e6500.config
Description: Binary data

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