From: Daniel Jacobowitz <dan@debian.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alexander Viro <viro@math.psu.edu>,
Linus Torvalds <torvalds@transmeta.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: 2.5.7-pre2 -- kernel.o(.data+0x300): undefined reference
Date: Sat, 16 Mar 2002 14:18:29 -0500 [thread overview]
Message-ID: <20020316141829.A30617@nevyn.them.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0203160515240.5891-100000@weyl.math.psu.edu> <E16mI91-0006mI-00@the-village.bc.nu>
In-Reply-To: <E16mI91-0006mI-00@the-village.bc.nu>
On Sat, Mar 16, 2002 at 05:39:03PM +0000, Alan Cox wrote:
> > +/* "Conditional" syscalls */
> > +
> > +asmlinkage long sys_nfsservctl(void) __attribute__ ((weak, alias ("sys_ni_syscall")));
> > +asmlinkage long sys_quotactl(void) __attribute__ ((weak, alias ("sys_ni_syscall")));
> > +
>
> This is what Linus threw out before - when David wanted to use it to remove
> all the intermodule crap.
>
> It doesn't work with some architecture binutils
As of at least 2.11.2 (fairly certain) and 2.12 (definite) this should
work on every architecture...
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-03-16 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 8:02 2.5.7-pre2 -- kernel.o(.data+0x300): undefined reference to `sys_nfsservctl' Miles Lane
2002-03-16 8:53 ` Alexander Viro
2002-03-16 10:16 ` [PATCH] " Alexander Viro
2002-03-16 17:39 ` [PATCH] Re: 2.5.7-pre2 -- kernel.o(.data+0x300): undefined reference Alan Cox
2002-03-16 17:39 ` Alexander Viro
2002-03-16 18:01 ` [PATCH] Re: 2.5.7-pre2 -- kernel.o(.data+0x300): undefined Alan Cox
2002-03-16 18:15 ` [PATCH] Re: 2.5.7-pre2 -- kernel.o(.data+0x300): undefined reference Linus Torvalds
2002-03-18 3:20 ` David S. Miller
2002-03-16 19:18 ` Daniel Jacobowitz [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=20020316141829.A30617@nevyn.them.org \
--to=dan@debian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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