mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Alex Davis <alex14641@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Issues with linux-2.6.2
Date: Fri, 6 Feb 2004 22:37:08 +0100	[thread overview]
Message-ID: <20040206223708.A2992@pclin040.win.tue.nl> (raw)
In-Reply-To: <20040206212205.46151.qmail@web40501.mail.yahoo.com>; from alex14641@yahoo.com on Fri, Feb 06, 2004 at 01:22:05PM -0800

On Fri, Feb 06, 2004 at 01:22:05PM -0800, Alex Davis wrote:

> I have a few issues with 2.6.2. Ths first issue is when upgrading from 2.4, I had to create 
> the symlinks:
> 
>    ln -s /usr/include/asm /usr/src/linux/include/asm-i386
>    ln -s /usr/include/asm-generic /usr/src/linux/include/asm-generic
> 
> This requirement was not mentioned in any documentation I could find.

No, because it is wrong. A very unwise thing to do.

> The second issue is when trying to build util-linux-2.11z I get the following error:
> 
> cc -pipe -O2 -mcpu=i486 -fomit-frame-pointer -I../lib -Wall -Wmissing-prototypes
> -Wstrict-prototypes -I/usr/include/ncurses -DNCH=0   -D_FILE_OFFSET_BITS=64 -DSBINDIR=\"/sbin\"
> -DUSRSBINDIR=\"/usr/sbin\" -DLOGDIR=\"/var/log\" -DVARPATH=\"/var\"
> -DLOCALEDIR=\"/usr/share/locale\" -O2  -s  blockdev.c   -o blockdev
> blockdev.c:70: error: parse error before '[' token
> blockdev.c:70: error: initializer element is not constant

And this is your punishment.

Andries

  parent reply	other threads:[~2004-02-06 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 21:22 Alex Davis
2004-02-06 21:35 ` Valdis.Kletnieks
2004-02-09 22:09   ` Ed Tomlinson
2004-02-06 21:37 ` Andries Brouwer [this message]
2004-02-09 17:41   ` Mike Black
2004-02-09 18:59     ` Andries Brouwer
  -- strict thread matches above, loose matches on Subject: below --
2004-02-09 17:57 Alex Davis
2004-02-06 21:21 Alex Davis

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=20040206223708.A2992@pclin040.win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=alex14641@yahoo.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

all inboxes | Powered by JetHome®