From: Sam Ravnborg <sam@ravnborg.org>
To: Tom <fivemiletom@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH 2.6.21.3] kbuild: fix build for cygwin
Date: Tue, 28 Aug 2007 21:34:16 +0200 [thread overview]
Message-ID: <20070828193416.GB32202@uranus.ravnborg.org> (raw)
In-Reply-To: <4669A0BD.8050104@gmail.com>
On Fri, Jun 08, 2007 at 11:32:29AM -0700, Tom wrote:
> From: Tom Enderes <enderes@gmail.com>
>
> The kernel build failed on cygwin hosts, because cygwin has slightly
> different typedefs compared to linux:
> scripts/mod/file2alias.c:518: error: dereferencing pointer to incomplete
> type
> Two files, scripts/mod/file2alias.c and scripts/mod/modpost.h, were
> modified as follows:
> Whever __CYGWIN__ is defined, __uint32 is defined as __uint32_t (instead
> of uint_32_t) and the missing ElfxxSection definitions are added.
> These changes have been tested both on cygwin 1.5.24, hostcc=gcc 3.4.4
> and on FC5, hostcc=gcc 4.1.1-1. Any tests on cygwin, with and without
> this change, were executed with the following set for make:
> HOST_LOADLIBES="-lcurses -lintl".
Hi Tom.
I have revisited this and have made a successfull kernel build on a
windows/cygwin box now.
I had to change two things only:
1) The -lintl workaround was fixed by introducing a little script.
If gcc cannot link a program that sues gettext then NLS is disabled.
2) Elf32_Section and Elf64_Section was replaced by Elfnn_Half
The build succeeds with a number of warnings that I just ignored.
fixdep and friends always get rebuild because kbuild does
not know about the .exe suffix so it does not
see that the binaries exists.
This is annoying and I hope to fix it before the merge.
These change will hit mainline during next merge window
so it will take a while before you can benefit.
For now they are in the kbuild.git tree at git.kernel.org
and will soon be part of -mm.
Sam
prev parent reply other threads:[~2007-08-28 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46608757.4020503@gmail.com>
[not found] ` <20070601212208.GA4559@uranus.ravnborg.org>
[not found] ` <4660971E.5020609@gmail.com>
[not found] ` <12D4B80525C5B744A216276E209921D9CE8016@MIAMI.xi-lite.lan>
2007-06-04 18:45 ` RE : Building kernel 2.6.21.3 for arm on cygwin Tom
2007-06-07 20:47 ` Sam Ravnborg
2007-06-08 15:57 ` Matthieu CASTET
2007-06-08 22:10 ` Sam Ravnborg
2007-06-09 7:51 ` Jan Engelhardt
2007-06-11 7:25 ` Matthieu CASTET
2007-06-08 18:32 ` [PATCH 2.6.21.3] kbuild: fix build for cygwin Tom
2007-06-08 20:15 ` Sam Ravnborg
2007-06-09 1:47 ` Tom
2007-08-28 19:34 ` Sam Ravnborg [this message]
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=20070828193416.GB32202@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=fivemiletom@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.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 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®