public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: compiler options cleanup - improve tool chain support
Date: Mon, 24 Aug 2009 14:59:09 +0200	[thread overview]
Message-ID: <20090824145909.0dbe7f8a@marrow.netinsight.se> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202E3915D98@SC-VEXCH1.marvell.com>

On Mon, 24 Aug 2009 05:41:59 -0700
Prafulla Wadaskar <prafulla@marvell.com> wrote:

> I get following erro only if I execute following build command
> make mrproper; make sheevaplug_config; make USE_PRIVATE_LIBGCC=no
> CROSS_COMPILE=armv5tel-redhat-linux-gnueabi- 2> warn.txt
> 
> And cat warn.txt 
> armv5tel-redhat-linux-gnueabi-ld: cannot find -lgcc
> make: *** [u-boot] Error 1
> 
> Whereas,
> if I unset first USE_PRIVATE_LIBGCC then I do not get this error and build is through
> My invocation may be wrong but shouldn't it treat USE_PRIVATE_LIBGCC=no as unset?

Well, I also got confused by this, but went through Wolfgangs exercise
program. The top-level Makefile treats USE_PRIVATE_LIBGCC like this:

   # Add GCC lib
   ifdef USE_PRIVATE_LIBGCC
   ifeq ("$(USE_PRIVATE_LIBGCC)", "yes")
   PLATFORM_LIBGCC = -L $(OBJTREE)/lib_$(ARCH) -lgcc
   else
   PLATFORM_LIBGCC = -L $(USE_PRIVATE_LIBGCC) -lgcc
   endif
   else
   PLATFORM_LIBGCC = -L $(shell dirname `$(CC) $(CFLAGS) -print-libgcc-file-name`) -lgcc
   endif
   PLATFORM_LIBS += $(PLATFORM_LIBGCC)
   export PLATFORM_LIBS

and in this case, since USE_PRIVATE_LIBGCC is defined, but is not
"yes", we will use it to set the linker search path. And indeed, it
tries to link with

   arm-unknown-linux-gnu-ld -Bstatic -T u-boot.lds [...] -L no -lgcc -Map u-boot.map -o u-boot

which ... will fail.

// Simon

  reply	other threads:[~2009-08-24 12:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 11:17 [U-Boot] [PATCH] ARM: compiler options cleanup - improve tool chain support Wolfgang Denk
2009-08-17 13:00 ` Tom
2009-08-17 13:25   ` Wolfgang Denk
2009-08-17 15:26   ` Dirk Behme
2009-08-17 19:43 ` ksi at koi8.net
2009-08-17 20:17 ` Magnus Lilja
2009-08-17 20:27   ` Wolfgang Denk
2009-08-18 17:08     ` Magnus Lilja
2009-08-18 21:18       ` Wolfgang Denk
2009-08-18 11:06 ` Gaye Abdoulaye Walsimou
2009-08-18 11:22   ` Wolfgang Denk
2009-08-20 15:27   ` Andrzej Wolski
2009-08-18 11:45 ` Gaye Abdoulaye Walsimou
2009-08-18 18:50 ` Tom
2009-08-18 21:19   ` Wolfgang Denk
2009-08-21 21:12 ` Wolfgang Denk
2009-08-24  8:59   ` Simon Kagstrom
2009-08-24 10:01     ` Wolfgang Denk
2009-08-24 11:28       ` Prafulla Wadaskar
2009-08-24 11:56         ` Wolfgang Denk
2009-08-24 12:41           ` Prafulla Wadaskar
2009-08-24 12:59             ` Simon Kagstrom [this message]
2009-08-24 13:05             ` Wolfgang Denk
2009-08-24 11:38       ` Simon Kagstrom
2009-08-24 12:01         ` Wolfgang Denk
2009-08-24 12:49           ` Simon Kagstrom
2009-08-25  7:12       ` Simon Kagstrom
2009-09-04 20:05         ` Wolfgang Denk
2009-09-07  6:23           ` Simon Kagstrom
2009-09-07  8:59             ` Prafulla Wadaskar
2009-09-07  9:15               ` Simon Kagstrom

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=20090824145909.0dbe7f8a@marrow.netinsight.se \
    --to=simon.kagstrom@netinsight.net \
    --cc=u-boot@lists.denx.de \
    /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