From: Dan Kegel <dank@kegel.com>
To: arjanv@redhat.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8 link failure for powerpc-970?
Date: Tue, 21 Sep 2004 20:20:09 -0700 [thread overview]
Message-ID: <4150EF69.1060007@kegel.com> (raw)
In-Reply-To: <1095669339.2800.3.camel@laptop.fenrus.com>
Arjan van de Ven wrote:
> On Mon, 2004-09-20 at 10:24, Dan Kegel wrote:
>
>>I'm trying to verify that I can build toolchains and compile
>>and link kernels for a large set of CPU types using simple kernel config files.
>>I'm also somewhat foolishly trying to do all this with gcc-3.4.2.
>>So any problems I run into are a bit hard to pin down to
>>compiler, kernel, or user error, since this is mostly new territory for me.
>
>
> use this patch
> --- linux-2.6.8/arch/ppc64/Makefile~ 2004-09-03 13:02:48.372244432 +0200
> +++ linux-2.6.8/arch/ppc64/Makefile 2004-09-03 13:02:48.372244432 +0200
> @@ -28,5 +28,7 @@
> LDFLAGS_vmlinux := -Bstatic -e $(KERNELLOAD) -Ttext $(KERNELLOAD)
> CFLAGS += -msoft-float -pipe -mminimal-toc -mtraceback=none
> +CFLAGS += $(call cc-option,-mcall-aixdesc)
That didn't help. In fact, cc-option is undefined, so it did nothing.
I tried correcting this to check_gcc:
--- linux-2.6.8/arch/ppc64/Makefile.old 2004-09-20 07:04:35.000000000 -0700
+++ linux-2.6.8/arch/ppc64/Makefile 2004-09-20 07:06:38.000000000 -0700
@@ -28,6 +28,7 @@
LDFLAGS_vmlinux := -Bstatic -e $(KERNELLOAD) -Ttext $(KERNELLOAD)
CFLAGS += -msoft-float -pipe -Wno-uninitialized -mminimal-toc \
-mtraceback=none
+CFLAGS += $(call check_gcc,-mcall-aixdesc)
This actually affected the build in that -mcall-aixdesc was used on many
compiles, but the build still ended with the same errors:
/opt/crosstool/powerpc64-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/bin/powerpc64-unknown-linux-gnu-ld -m elf64ppc -m elf64ppc -Bstatic -e 0xc000000000000000 -Ttext 0xc000000000000000 -T arch/ppc64/kernel/vmlinux.lds.asm
arch/ppc64/kernel/head.o init/built-in.o --start-group usr/built-in.o arch/ppc64/kernel/built-in.o arch/ppc64/mm/built-in.o kernel/built-in.o mm/built-in.o fs/built-in.o ipc/built-in.o security/built-in.o crypto/built-in.o
lib/lib.a arch/ppc64/lib/lib.a lib/built-in.o arch/ppc64/lib/built-in.o drivers/built-in.o sound/built-in.o net/built-in.o --end-group -o .tmp_vmlinux1
arch/ppc64/kernel/built-in.o(.text+0xdc44): In function `.sys32_ipc':
: undefined reference to `.compat_sys_shmctl'
arch/ppc64/kernel/built-in.o(.text+0xdca0): In function `.sys32_ipc':
: undefined reference to `.compat_sys_semctl'
arch/ppc64/kernel/built-in.o(.text+0xdcbc): In function `.sys32_ipc':
: undefined reference to `.compat_sys_msgsnd'
arch/ppc64/kernel/built-in.o(.text+0xdce0): In function `.sys32_ipc':
: undefined reference to `.compat_sys_msgrcv'
arch/ppc64/kernel/built-in.o(.text+0xdd0c): In function `.sys32_ipc':
: undefined reference to `.compat_sys_msgctl'
arch/ppc64/kernel/built-in.o(.text+0xdd28): In function `.sys32_ipc':
: undefined reference to `.compat_sys_shmat'
arch/ppc64/kernel/built-in.o(.text+0xdd3c): In function `.sys32_ipc':
: undefined reference to `.compat_sys_semtimedop'
arch/ppc64/kernel/built-in.o(.text+0xe9d4): In function `.sys32_sysctl':
: undefined reference to `.do_sysctl'
arch/ppc64/kernel/built-in.o(.text+0x10958): In function `.routing_ioctl':
: undefined reference to `.sockfd_lookup'
net/built-in.o(.text+0x278): In function `.verify_compat_iovec':
: undefined reference to `.move_addr_to_kernel'
net/built-in.o(.text+0x724): In function `.scm_detach_fds_compat':
: undefined reference to `.__scm_destroy'
make: *** [.tmp_vmlinux1] Error 1
Got another suggestion?
Thanks,
Dan
--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change
next prev parent reply other threads:[~2004-09-22 3:22 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 [this message]
2004-09-22 16:41 ` Dan Kegel
2004-09-22 22:27 ` Herbert Poetzl
2004-09-23 5:24 ` Dan Kegel
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=4150EF69.1060007@kegel.com \
--to=dank@kegel.com \
--cc=arjanv@redhat.com \
--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 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.