All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: RE: Problem compiling 2.6.12
Date: Thu, 23 Jun 2005 22:26:19 +0100	[thread overview]
Message-ID: <42BB28FB.1010907@blueyonder.co.uk> (raw)

Is /usr/src/linux a symlink to linux-2.6.12 .... "ls -ld linux" shows that.
"which gcc" would tell if /usr/local/bin/gcc is being used.
"gcc -v" to show the version.
Something looks confused, the above would be helpful.
Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot
Retired IBM Mainframes and Sun Servers Tech Support Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks

             reply	other threads:[~2005-06-23 21:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 21:26 Sid Boyce [this message]
     [not found] <Pine.LNX.4.62.0506240856460.10920@eagle.netwrx1.com>
     [not found] ` <42BC1C43.3040505@blueyonder.co.uk>
     [not found]   ` <Pine.LNX.4.62.0506241258500.20958@eagle.netwrx1.com>
     [not found]     ` <42BC9FF1.1010400@blueyonder.co.uk>
     [not found]       ` <5nerb117olj7kahv0k8b1vss382ini6bfr@4ax.com>
2005-06-26  0:39         ` Problem compiling 2.6.12 Sid Boyce
  -- strict thread matches above, loose matches on Subject: below --
2005-06-22 19:37 Nick Warne
2005-06-22 21:30 ` Adrian Bunk
2005-06-22 21:53   ` Nick Warne
2005-06-23  9:53     ` Adrian Bunk
2005-06-23 11:08     ` Nix
2005-06-22 15:28 George Kasica
2005-06-22 15:59 ` Jesper Juhl
2005-06-22 16:44   ` Adrian Bunk
2005-06-22 19:15     ` George Kasica
2005-06-22 19:26     ` Jesper Juhl
2005-06-22 19:14   ` George Kasica
2005-06-22 19:45     ` Richard B. Johnson
2005-06-22 16:42 ` Adrian Bunk
2005-06-22 19:22   ` George Kasica
2005-06-22 21:33     ` Adrian Bunk

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=42BB28FB.1010907@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --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 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.