public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Bryan Hundven <bryanhundven@gmail.com>
To: Danny Gale <Daniel.Gale@coloradoengineeringinc.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Multilib problem
Date: Tue, 04 Feb 2014 00:39:00 -0000	[thread overview]
Message-ID: <CAJ+oik3wBpFsjeJT97N_OA_ow_Joj1DWcCFD0dobCaLE57a5OA@mail.gmail.com> (raw)
In-Reply-To: <52E199A8.2020305@coloradoengineeringinc.com>

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.)

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

  parent reply	other threads:[~2014-02-04  0:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 22:37 Danny Gale
2014-01-24 17:16 ` Harold Grovesteen
2014-01-24 22:28 ` Cody P Schafer
2014-01-24 22:35   ` Cody P Schafer
2014-01-24 23:00     ` Ray Donnelly
2014-02-03 18:39     ` Danny Gale
2014-02-03 22:17       ` Cody P Schafer
2014-02-04  2:49   ` Bryan Hundven
2014-02-04  0:39 ` Bryan Hundven [this message]
     [not found]   ` <52F03B5F.1000504@coloradoengineeringinc.com>
     [not found]     ` <CAJ+oik0PQd_0e6=RrdeTpg550pa3FJP0s=t8A5mD-Vten4jRNA@mail.gmail.com>
2014-02-04  1:08       ` Bryan Hundven
2014-02-04  1:11         ` Bryan Hundven
2014-02-04  1:12           ` Bryan Hundven
2014-02-04 17:45             ` Danny Gale
2014-02-04 18:29               ` Bryan Hundven
2014-02-04 18:39                 ` Ray Donnelly
2014-02-04 22:18                   ` Cody P Schafer
2014-02-12  6:01                   ` Bryan Hundven
2014-02-12  7:52                     ` Ray Donnelly
     [not found]                 ` <52F13ECA.7060803@coloradoengineeringinc.com>
2014-02-07  7:42                   ` Bryan Hundven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ+oik3wBpFsjeJT97N_OA_ow_Joj1DWcCFD0dobCaLE57a5OA@mail.gmail.com \
    --to=bryanhundven@gmail.com \
    --cc=Daniel.Gale@coloradoengineeringinc.com \
    --cc=crossgcc@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).