mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Paul Mundt <lethal@linux-sh.org>, Sam Ravnborg <sam@ravnborg.org>,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] sh: fix LIBGCC
Date: Sat, 2 Aug 2008 01:25:46 +0300	[thread overview]
Message-ID: <20080801222546.GJ19682@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <20080801222217.GD13448@linux-sh.org>

On Sat, Aug 02, 2008 at 07:22:17AM +0900, Paul Mundt wrote:
> On Sat, Aug 02, 2008 at 01:13:44AM +0300, Adrian Bunk wrote:
> > Commit f15cbe6f1a4b4d9df59142fc8e4abb973302cf44
> > (sh: migrate to arch/sh/include/) moved KBUILD_CFLAGS
> > (which is used by LIBGCC) below LIBGCC, causing build
> > errors like the following:
> > 
> > <--  snip  -->
> > 
> > ...
> >   LD      .tmp_vmlinux1
> > arch/sh/kernel/built-in.o: In function `module_clk_recalc':
> > clock-sh4.c:(.text+0x80f0): undefined reference to `__udivsi3_i4i'
> > ...
> > make[1]: *** [.tmp_vmlinux1] Error 1
> > 
> > <--  snip  -->
> > 
> > Reported-by: Adrian Bunk <bunk@kernel.org>
> > Signed-off-by: Adrian Bunk <bunk@kernel.org>
> > 
> That's interesting, none of my compilers had difficulty with it, whereas
> it seems your toolchain couldn't report the libgcc location at all.
>...

It did report /usr/local/DIR/gcc-sh-4.3.1/lib/gcc/sh-linux/4.3.1/libgcc.a,
but that's not for all configurations the correct one.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2008-08-01 22:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 22:13 Adrian Bunk
2008-08-01 22:22 ` Paul Mundt
2008-08-01 22:25   ` Adrian Bunk [this message]

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=20080801222546.GJ19682@cs181140183.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®