All of lore.kernel.org
 help / color / mirror / Atom feed
From: Levent Serinol <lserinol@yahoo.com>
To: sparclinux@vger.kernel.org
Subject: Re: Fw: [Bugme-new]  [Bug 2205] New: compile failure, gcc 3.2.3,
Date: Mon, 01 Mar 2004 22:11:47 +0000	[thread overview]
Message-ID: <4043B523.2060100@yahoo.com> (raw)
In-Reply-To: <20040301192235.GA4379@mars.ravnborg.org>

Successfully compiled and running 2.6.3, 2.6.3_rc1 (Gentoo 
sparc-dev-sources) 2.6.3-bk8 and 2.6.4-rc1
on Ultra 10 with Gentoo 1.4_rc5 Sparc64.

Try "emerge"ing sparc-dev-sources.





Sam Ravnborg wrote:

> Took this to linux-sparc - someone may have encountered the same.
> 
> I have looked at the build output, and what I see is that
> ld complains about symbols declared weak in the corresponding
> ksymall.c file.
> 
> The quick way is to avoid defining KSYMALL in .config.
> 
> The root cause seems to be caused by a too old binutils, unable
> to deal with weak symbols for sparc64.
> 
> Could you please reply with current version of binutils (ld --version),
> and tell if it succeeeds without KSYMALL defined.
> 
> 	Sam
> 
> 
> Below is relevant part of mail conversation for reference.
> [Note - a make clean/mrporper did not cure it].
> 
> Brian wrote:
> 
>>I may be missing something, but kallsyms doesn't seem to be being run
>>in the sequence you describe.  Therefore, the entire build trace is in:
>>
>>       http://www.stat.ufl.edu/~bb/2.6.3-build_fail.txt
>>
>>                                                       Brian
> 
> 
> 
> On Thu, Feb 26, 2004 at 08:04:55PM -0800, Andrew Morton wrote:
> 
>>hm, kallsyms_addresses is generated by the build.
>>
>>Did you try `make clean' and then redo it all?
>>
>>Sam, `make clean' leaves some dotfiles around in $TOPDIR
>>
>>rw-r--r--    1 akpm     akpm       683158 Feb 26 01:08 .tmp_kallsyms1.S
>>-rw-r--r--    1 akpm     akpm       683158 Feb 26 01:08 .tmp_kallsyms2.S
>>drwxr-xr-x    2 akpm     akpm         4096 Feb 26 03:37 .tmp_versions/
>>
>>
>>Begin forwarded message:
>>
>>Date: Thu, 26 Feb 2004 19:45:54 -0800
>>From: bugme-daemon@osdl.org
>>To: bugme-new@lists.osdl.org
>>Subject: [Bugme-new]  [Bug 2205] New: compile failure, gcc 3.2.3, gentoo SPARC, Sun Ultra 5
>>
>>
>>http://bugme.osdl.org/show_bug.cgi?id"05
>>
>>           Summary: compile failure, gcc 3.2.3, gentoo SPARC, Sun Ultra 5
>>    Kernel Version: 2.6.3
>>            Status: NEW
>>          Severity: high
>>             Owner: other_other@kernel-bugs.osdl.org
>>         Submitter: bb@stat.ufl.edu
>>
>>
>>Distribution: gentoo
>>Hardware Environment: Sun Ultra 5
>>Software Environment: gentoo
>>Problem Description:
>>
>>There were a couple of small compile problems, such as the gcc version
>>check in init/main.c deciding that gcc 3.2.3 was too old, having to
>>expand and remove the SPRINTK macro in reiserfs, and unconfiguring two
>>scsi drivers that failed, but then I hit a showstopper:
>>
>>[...]
>>  CC      arch/sparc64/lib/rwsem.o
>>  AS      arch/sparc64/lib/strlen.o
>>  AS      arch/sparc64/lib/strlen_user.o
>>  AS      arch/sparc64/lib/strncmp.o
>>  AS      arch/sparc64/lib/strncpy_from_user.o
>>  AS      arch/sparc64/lib/xor.o
>>  AR      arch/sparc64/lib/lib.a
>>  GEN     .version
>>  CHK     include/linux/compile.h
>>  UPD     include/linux/compile.h
>>  CC      init/version.o
>>  LD      init/built-in.o
>>  LD      .tmp_vmlinux1
>>kernel/built-in.o(.text+0x208f0): In function `kallsyms_lookup':
>>: undefined reference to `kallsyms_addresses'
>>kernel/built-in.o(.text+0x208f4): In function `kallsyms_lookup':
>>: undefined reference to `kallsyms_addresses'
>>kernel/built-in.o(.text+0x20970): In function `kallsyms_lookup':
>>: undefined reference to `kallsyms_names'
>>kernel/built-in.o(.text+0x20974): In function `kallsyms_lookup':
>>: undefined reference to `kallsyms_num_syms'
>>kernel/built-in.o(.text+0x20978): In function `kallsyms_lookup':
>>: undefined reference to `kallsyms_names'
>>kernel/built-in.o(.text+0x2097c): In function `kallsyms_lookup':
>>: undefined reference to `kallsyms_num_syms'
>>kernel/built-in.o(.text+0x20988): In function `kallsyms_lookup':
>>: undefined reference to `kallsyms_addresses'
>>kernel/built-in.o(.text+0x20990): In function `kallsyms_lookup':
>>: undefined reference to `kallsyms_addresses'
>>kernel/built-in.o(.text+0x20a1c): In function `kallsyms_lookup':
>>: undefined reference to `kallsyms_num_syms'
>>kernel/built-in.o(.text+0x20a2c): In function `kallsyms_lookup':
>>: undefined reference to `kallsyms_addresses'
>>kernel/built-in.o(.text+0x20a7c): In function `kallsyms_lookup':
>>: undefined reference to `kallsyms_addresses'
>>kernel/built-in.o(.text+0x20c24): In function `get_ksymbol_mod':
>>: undefined reference to `kallsyms_num_syms'
>>kernel/built-in.o(.text+0x20c34): In function `get_ksymbol_mod':
>>: undefined reference to `kallsyms_num_syms'
>>kernel/built-in.o(.text+0x20c84): In function `get_ksymbol_core':
>>: undefined reference to `kallsyms_names'
>>kernel/built-in.o(.text+0x20c90): In function `get_ksymbol_core':
>>: undefined reference to `kallsyms_names'
>>kernel/built-in.o(.text+0x20cd4): In function `get_ksymbol_core':
>>: undefined reference to `kallsyms_addresses'
>>kernel/built-in.o(.text+0x20cdc): In function `get_ksymbol_core':
>>: undefined reference to `kallsyms_addresses'
>>kernel/built-in.o(.text+0x20d44): In function `update_iter':
>>: undefined reference to `kallsyms_num_syms'
>>kernel/built-in.o(.text+0x20d48): In function `update_iter':
>>: undefined reference to `kallsyms_num_syms'
>>make: *** [.tmp_vmlinux1] Error 1
>>
>>real    118m4.563s
>>user    114m31.810s
>>sys     3m3.380s
>>
>>Steps to reproduce: make vmlinux
>>
>>------- You are receiving this mail because: -------
>>You are on the CC list for the bug, or are watching someone who is.
> 
> 


  reply	other threads:[~2004-03-01 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01 19:22 Fw: [Bugme-new] [Bug 2205] New: compile failure, gcc 3.2.3, gentoo SPARC, Sun Ultra 5 Sam Ravnborg
2004-03-01 22:11 ` Levent Serinol [this message]
2004-03-01 23:39 ` Keith M Wesolowski

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=4043B523.2060100@yahoo.com \
    --to=lserinol@yahoo.com \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.