All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)?
Date: Tue, 21 Sep 2004 22:40:24 -0700	[thread overview]
Message-ID: <41511048.9000603@kegel.com> (raw)
In-Reply-To: <20040921105745.GJ9106@holomorphy.com>

William Lee Irwin III wrote:
>>Look like arch/sparc/boot/Makefile is too old.
>>vmlinux.lds.s were renamed to vmlinux.lds 2004/08/15 - maybe you need to
>>checkout that file?
> 
> I don't see this kind of issue in current 2.6.x; what's going on?

Figured it out.  It was user error.  I had an outdated patch.
Sorry for the noise.  Next time I'll check my patches more carefully.
- Dan

p.s. For what it's worth, I only need to apply five patches to
vanilla 2.6.8 to get past various build errors:
      60     258    2483 kaz-types.patch
      50     207    2088 linux-2.6.8-arm-nonofpu.patch
     683    2328   27265 linux-2.6.8-build_on_case_insensitive_fs-1.patch
     285    1215   10145 linux-2.6.8-m68k-kludge.patch
      28     122    1028 linux-2.6.8-noshared-kconfig.patch
The build_on_case_insensitive_fs patch is the one that was out of date.

-- 
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change

  reply	other threads:[~2004-09-22  5:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21  6:03 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)? Dan Kegel
2004-09-21 10:50 ` Sam Ravnborg
2004-09-21 10:57   ` William Lee Irwin III
2004-09-22  5:40     ` Dan Kegel [this message]
2004-09-24 20:19       ` Sam Ravnborg
2004-10-07  5:57   ` Building on case-insensitive systems and systems where -shared doesn't work well (was: Re: 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)?) Dan Kegel
2004-10-16 21:00     ` Sam Ravnborg
2004-10-16 19:06       ` Russell King
2004-10-16 21:24         ` Sam Ravnborg
2004-10-16 19:40           ` Russell King
2004-10-16 19:04             ` Building on case-insensitive systems and systems where -shared doesn't work well Dan Kegel
2004-10-16 22:04             ` Building on case-insensitive systems and systems where -shared doesn't work well (was: Re: 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)?) Sam Ravnborg
2004-10-17 16:57               ` Herbert Poetzl
2004-10-17 16:42                 ` Building on case-insensitive systems and systems where -shared doesn't work well Dan Kegel
2004-10-17 18:29                   ` Herbert Poetzl
2004-10-17 17:47                     ` Dan Kegel
2004-10-17 19:06                       ` Herbert Poetzl
2004-10-17 19:32                         ` Dan Kegel
2004-10-31 21:10       ` Building on case-insensitive systems and systems where -shared doesn't work well (was: Re: 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)?) Sam Ravnborg

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=41511048.9000603@kegel.com \
    --to=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=wli@holomorphy.com \
    /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.