Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] freetype: fix for multilib toolchain
Date: Fri, 14 Jan 2011 15:42:50 +0100	[thread overview]
Message-ID: <20110114154250.11a5542c@surf> (raw)
In-Reply-To: <201101140731.30909.minimod@morethan.org>

On Fri, 14 Jan 2011 07:31:28 -0600
"Michael S. Zick" <minimod@morethan.org> wrote:

> I see a: 
> -A ARCH to set the architecture

This option is architecture-specific:

      -A architecture
       --architecture=architecture
           In the current release of ld, this option is useful only for
      the Intel 960 family of architectures.  In that ld configuration,
      the architecture argument identifies the particular architecture
      in the 960 family, enabling some safeguards and modifying the
      archive- library search path.

           Future releases of ld may support similar functionality for
           other architecture families.

> and a:
> -m EMULATION to set the emulation

Here is the list of emulations for a multilib CodeSourcery toolchain
that supports armv4t, armv5t and thumb2 as multilib variants:

$ arm-none-linux-gnueabi-ld -V
GNU ld (Sourcery G++ Lite 2009q1-203) 2.19.51.20090205
  Supported emulations:
   armelf_linux_eabi
   armelfb_linux_eabi

So clearly, the -m option does not allow to choose between the
different multilib variants.

In fact, I don't even see anything in ld that allows to select a
multilib variant. So the link should be using gcc, which then drives ld
(or more precisely collect2) by telling it to use this or that library.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-01-14 14:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14  4:18 [Buildroot] freetype: fix for multilib toolchain Matt Johnson
2011-01-14  8:11 ` Thomas Petazzoni
2011-01-14 12:47   ` Bjørn Forsman
2011-01-14 13:31     ` Michael S. Zick
2011-01-14 14:42       ` Thomas Petazzoni [this message]
2011-01-14 14:44     ` Thomas Petazzoni
2011-01-14 15:40       ` Michael S. Zick
2011-01-14 16:04       ` Matt Johnson

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=20110114154250.11a5542c@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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