From: Herbert Poetzl <herbert@13thfloor.at>
To: Dan Kegel <dank@kegel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
arjanv@redhat.com
Subject: Re: 2.6.8 link failure for powerpc-970?
Date: Thu, 23 Sep 2004 00:27:23 +0200 [thread overview]
Message-ID: <20040922222723.GD30109@MAIL.13thfloor.at> (raw)
In-Reply-To: <4151AB3D.3040003@kegel.com>
On Wed, Sep 22, 2004 at 09:41:33AM -0700, Dan Kegel wrote:
> Dan Kegel 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.
Hi Dan!
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?
TIA,
Herbert
> >>>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. ...
> >
> >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.
>
> The reference to compat_sys_shmctl seems to be in
> ./arch/ia64/ia32/sys_ia32.c
> ./arch/ppc64/kernel/sys_ppc32.c
> ./arch/x86_64/ia32/ipc32.c
> ./arch/s390/kernel/compat_linux.c
> and appears to not be conditioned on CONFIG_SYSVIPC_COMPAT.
> Seems like linking problems are expected unless you turn on
> CONFIG_SYSVIPC and CONFIG_SYSVIPC_COMPAT.
>
> I turned 'em on and am trying again.
> - Dan
>
> --
> My technical stuff: http://kegel.com
> My politics: see http://www.misleader.org for examples of why I'm for
> regime change
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-09-22 22:27 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 [this message]
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=20040922222723.GD30109@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=arjanv@redhat.com \
--cc=dank@kegel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox