public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "Ingo T. Storm" <it@lapavoni.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.5 does not link on Ruffian (alpha)
Date: Sun, 27 May 2001 04:49:24 +0200	[thread overview]
Message-ID: <20010527044924.H1834@athlon.random> (raw)
In-Reply-To: <3B0BFE90.CE148B7@kjist.ac.kr> <20010523210923.A730@athlon.random> <022e01c0e5fc$39ac0cf0$2e2ca8c0@buxtown.de> <20010526193649.B1834@athlon.random> <20010526201442.D1834@athlon.random> <3B10521D.346E5886@mandrakesoft.com>
In-Reply-To: <3B10521D.346E5886@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Sat, May 26, 2001 at 09:02:21PM -0400

On Sat, May 26, 2001 at 09:02:21PM -0400, Jeff Garzik wrote:
> Andrea Arcangeli wrote:
> > diff -urN alpha/arch/alpha/kernel/sys_dp264.c alpha-1/arch/alpha/kernel/sys_dp264.c
> > --- alpha/arch/alpha/kernel/sys_dp264.c Sun Apr  1 01:17:07 2001
> > +++ alpha-1/arch/alpha/kernel/sys_dp264.c       Wed May 23 02:43:49 2001
> > @@ -16,15 +16,18 @@
> >  #include <linux/pci.h>
> >  #include <linux/init.h>
> > 
> > +#define __EXTERN_INLINE inline
> > +#include <asm/io.h>
> > +#include <asm/core_tsunami.h>
> > +#undef  __EXTERN_INLINE
> > +
> 
> Why is "__EXTERN_INLINE" defined as "inline" not "extern inline"?

because it must be implemented somewhere for the alpha_mv pointer to
functions and for some reason they are not implemented by
core_tsunami.c in my tree (but they are in mainline and that's right).

> I simply added "extern" and things started working (as noted in my
> previous message in this thread)..

defining it as `extern inline' is completly equivalent to backing out
the patch I posted, see core_tsunami.h:

#ifndef __EXTERN_INLINE
#define __EXTERN_INLINE extern inline
#define __IO_EXTERN_INLINE
#endif

Of course your patch works like a charm too. A cleaner fix is to backout my
patch because core_tsunami.h will define it to `extern inline'
atuomatically.

Tomorrow I'll go through the log generated by the script that did the
binary search for me while I was out to find out what patch in my tree
caused me to write the posted patch to get all compilations right.

Andrea

  reply	other threads:[~2001-05-27  2:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23 18:16 Swap strangeness using 2.4.5pre2aa1 G. Hugh Song
2001-05-23 19:09 ` Andrea Arcangeli
2001-05-26 15:20   ` 2.4.5 does not link on Ruffian (alpha) Ingo T. Storm
2001-05-26 17:36     ` Andrea Arcangeli
2001-05-26 18:14       ` Andrea Arcangeli
2001-05-27  1:02         ` Jeff Garzik
2001-05-27  2:49           ` Andrea Arcangeli [this message]
2001-05-27 16:41             ` Andrea Arcangeli
2001-05-27 19:22               ` Andrea Arcangeli
2001-05-27 21:16                 ` Magnus Naeslund(f)
2001-05-26 22:03     ` [PATCH] " Jeff Garzik
2001-05-26 22:48       ` Jeff Garzik
2001-05-27 23:39         ` Richard Henderson
2001-05-27 23:54           ` Jeff Garzik
2001-05-28  1:05             ` Richard Henderson
2001-05-23 22:34 ` Swap strangeness using 2.4.5pre2aa1 Rik van Riel

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=20010527044924.H1834@athlon.random \
    --to=andrea@suse.de \
    --cc=it@lapavoni.de \
    --cc=jgarzik@mandrakesoft.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