All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Carlsson <ulfc@bun.falkenberg.se>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: Richard Hartensveld <richard@infopact.nl>,
	"linux@cthulhu.engr.sgi.com" <linux@cthulhu.engr.sgi.com>
Subject: Re: Compilation errors
Date: Wed, 3 Feb 1999 21:43:26 +0100	[thread overview]
Message-ID: <19990203214326.A3430@bun.falkenberg.se> (raw)
In-Reply-To: <Pine.LNX.3.96.990203121206.16014B-100000@lager.engsoc.carleton.ca>; from Alex deVries on Wed, Feb 03, 1999 at 12:12:47PM -0500

On Wed, Feb 03, 1999 at 12:12:47PM -0500, Alex deVries wrote:
> On Wed, 3 Feb 1999, Richard Hartensveld wrote:
> 
> >                  from init/main.c:15:
> > /usr/src/linux/include/linux/sched.h:528: `current' undeclared (first
> > use this function)
> > /usr/src/linux/include/linux/sched.h:528: (Each undeclared identifier is
> > reported only once
> > /usr/src/linux/include/linux/sched.h:528: for each function it appears
> 
> Use egcs and you will have no problems.  You'll be a better person, too.

You may update the specs file instead if you want, and gcc will work. Ask me and
I'll send you the updated specs file.

- Ulf

  reply	other threads:[~1999-02-03 20:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-03 14:31 Compilation errors Richard Hartensveld
1999-02-03 17:12 ` Alex deVries
1999-02-03 20:43   ` Ulf Carlsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-05  2:59 Peter Teoh
2008-07-01 11:21 compilation errors Jean-Francois Moine
2022-04-01  9:35 Compilation errors Fabio M. De Francesco
2022-04-01 10:13 ` Stefano Brivio
2022-04-01 12:01   ` Fabio M. De Francesco
2022-04-01 12:57     ` Stefano Brivio
2022-04-01 13:07       ` Fabio M. De Francesco
2022-04-01 16:09         ` Alison Schofield
2022-04-01 17:58           ` Fabio M. De Francesco
2022-04-01 14:39       ` Fabio M. De Francesco

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=19990203214326.A3430@bun.falkenberg.se \
    --to=ulfc@bun.falkenberg.se \
    --cc=adevries@engsoc.carleton.ca \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=richard@infopact.nl \
    /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.