All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Aloni <da-x@colinux.org>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Generation of *.s files from *.S files in kbuild
Date: Thu, 12 Aug 2004 22:25:35 +0300	[thread overview]
Message-ID: <20040812192535.GA20953@callisto.yi.org> (raw)

Hello, 

Is the generation of *.s files from *.S files in the kernel
build system a wide spread phenomenon? As far as I can see
only vmlinux.lds.s is built that way in my default i386 config.

It causes problems when trying to cross-build a kernel on a 
file system that has case-insensitive filenames, or on a GNU
port that is case insensitive (such as Cygwin).

If anyone wondered, I'm trying to cross build a Linux kernel
on a Cygwin system using a Linux native toolchain, in order
to make development of the Windows port of coLinux easier
for some people.

-- 
Dan Aloni
da-x@colinux.org

             reply	other threads:[~2004-08-12 19:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12 19:25 Dan Aloni [this message]
2004-08-13  0:37 ` Generation of *.s files from *.S files in kbuild Benno
2004-08-13  5:04   ` Sam Ravnborg
2004-08-13  8:09     ` [PATCH 1/2] " Dan Aloni
2004-08-13  9:24       ` [PATCH 1/2] #2 (Generation of *.s files from *.S files in kbuild) Dan Aloni
2004-08-13 18:33         ` Sam Ravnborg
2004-08-13 19:09           ` Dan Aloni
2004-08-13 19:17             ` Sam Ravnborg
2004-08-14 19:46           ` [PATCH] [#3 1/2] Generate vmlinux.lds instead of vmlinux.lds.s Dan Aloni
2004-08-15 18:35             ` Sam Ravnborg
2004-08-14 19:49           ` [PATCH] [#3 2/2] " Dan Aloni
2004-08-13  8:12     ` Generation of *.s files from *.S files in kbuild Dan Aloni

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=20040812192535.GA20953@callisto.yi.org \
    --to=da-x@colinux.org \
    --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.