public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	arjanv@redhat.com
Subject: Re: 2.6.8 link failure for powerpc-970?
Date: Wed, 22 Sep 2004 22:24:21 -0700	[thread overview]
Message-ID: <41525E05.7020506@kegel.com> (raw)
In-Reply-To: <20040922222723.GD30109@MAIL.13thfloor.at>

Herbert Poetzl wrote:
>>>arch/ppc64/kernel/built-in.o(.text+0xdc44): In function `.sys32_ipc':
>>>: undefined reference to `.compat_sys_shmctl'
>>>...
>>
>>Could it be a config problem?  My config file was from 'allnoconfig', I 
>>think, and has
>>$ egrep 'SYSV|COMPAT' .config
>>CONFIG_COMPAT=y
>># CONFIG_SYSVIPC is not set
>>compat_sys_shmctl is in ipc/compat.c, and is enabled by 
>>CONFIG_SYSVIPC_COMPAT,
>>which depends on CONFIG_SYSVIPC, which is off. ...
>>Seems like linking problems are expected unless you turn on
>>CONFIG_SYSVIPC and CONFIG_SYSVIPC_COMPAT.
> 
 > once you figured out what 'default' configs
 > are appropriate for the special archs not working
 > with allyes/noconfig could you send me a note
 > and/or post a link to them somewhere?

Sure.  For ppc64, beyond allnoconfig, I had to enable

CONFIG_SYSVIPC
CONFIG_SYSCTL
CONFIG_NET
... um, but that didn't fix everything.  Now it fails with

...
make -f scripts/Makefile.build obj=arch/ppc64/boot arch/ppc64/boot/zImage
   gzip -f -9 < vmlinux > arch/ppc64/boot/kernel-vmlinux.gz
touch arch/ppc64/boot/kernel-vmlinux.c
   gcc -Wp,-MD,arch/ppc64/boot/.kernel-vmlinux.o.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -Iinclude -fno-builtin  -c -o arch/ppc64/boot/kernel-vmlinux.o arch/ppc64/boot/kernel-vmlinux.c
objcopy  arch/ppc64/boot/kernel-vmlinux.o --add-section=.kernel:vmlinux=arch/ppc64/boot/kernel-vmlinux.gz --set-section-flags=.kernel:vmlinux=contents,alloc,load,readonly,data
   gzip -f -9 < .config > arch/ppc64/boot/kernel-.config.gz
touch arch/ppc64/boot/kernel-.config.c
   gcc -Wp,-MD,arch/ppc64/boot/.kernel-.config.o.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -Iinclude -fno-builtin  -c -o arch/ppc64/boot/kernel-.config.o arch/ppc64/boot/kernel-.config.c
objcopy  arch/ppc64/boot/kernel-.config.o --add-section=.kernel:.config=arch/ppc64/boot/kernel-.config.gz --set-section-flags=.kernel:.config=contents,alloc,load,readonly,data
   gzip -f -9 < System.map > arch/ppc64/boot/kernel-System.map.gz
touch arch/ppc64/boot/kernel-System.map.c
   gcc -Wp,-MD,arch/ppc64/boot/.kernel-System.map.o.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -Iinclude -fno-builtin  -c -o arch/ppc64/boot/kernel-System.map.o arch/ppc64/boot/kernel-System.map.c
objcopy  arch/ppc64/boot/kernel-System.map.o --add-section=.kernel:System.map=arch/ppc64/boot/kernel-System.map.gz --set-section-flags=.kernel:System.map=contents,alloc,load,readonly,data

gcc -Wp,-MD,arch/ppc64/boot/.crt0.o.d -D__ASSEMBLY__ -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -Iinclude -fno-builtin  -traditional -c -o arch/ppc64/boot/crt0.o arch/ppc64/boot/crt0.S

arch/ppc64/boot/crt0.S: Assembler messages:
arch/ppc64/boot/crt0.S:17: Error: no such instruction: `lis 9,_start@h'
...

Um, why is it using the host's gcc?  I ran make with
make V=1 ARCH=ppc64 CROSS_COMPILE=/opt/crosstool/powerpc64-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/bin/powerpc64-unknown-linux-gnu-
so it really should know better, shouldn't it?

I'm too sleepy to figure this out at the moment.
Thanks for any tips ("I'm programming... while I sleep")!
- Dan


-- 
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change

  reply	other threads:[~2004-09-23  5:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20  8:24 2.6.8 link failure for powerpc-970? Dan Kegel
2004-09-20  8:35 ` Arjan van de Ven
2004-09-22  3:20   ` Dan Kegel
2004-09-22 16:41     ` Dan Kegel
2004-09-22 22:27       ` Herbert Poetzl
2004-09-23  5:24         ` Dan Kegel [this message]
2004-09-23 13:12           ` Anton Blanchard
2004-09-23 14:14             ` Dan Kegel
2004-09-23  0:17   ` Anton Blanchard

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=41525E05.7020506@kegel.com \
    --to=dank@kegel.com \
    --cc=arjanv@redhat.com \
    --cc=herbert@13thfloor.at \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox