From: Arnd Bergmann <arnd@bergmann-dalldorf.de>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] klibc for 2.5.59 bk
Date: Mon, 17 Feb 2003 18:12:33 +0100 [thread overview]
Message-ID: <200302171732.SAA00873@post.webmailer.de> (raw)
In-Reply-To: 20030217031008$270a@gated-at.bofh.it
Kai Germaschewski wrote:
> should work fine (reminder: "make KBUILD_VERBOSE=0 ..." will give you much
> more readable output), but I probably broke some non-x86 architectures
> in the process.
I just tried building on s390x and only needed this trivial fix. Unfortunately,
2.5.61 does not boot on s390x yet, so I could not do run-time tests.
Arnd <><
===== usr/lib/socketcalls.pl 1.4 vs edited =====
--- 1.4/usr/lib/socketcalls.pl Sun Feb 16 06:09:33 2003
+++ edited/usr/lib/socketcalls.pl Mon Feb 17 18:24:39 2003
@@ -39,7 +39,7 @@
print OUT "\tjmp __socketcall_common\n";
print OUT "\t.size ${name},.-${name}\n";
} else {
- open(OUT, "> ${obj}/${name}.c")
+ open(OUT, "> ${obj}/socketcalls/${name}.c")
or die "$0: Cannot open socketcalls/${name}.c\n";
print OUT "#include \"socketcommon.h\"\n\n";
next parent reply other threads:[~2003-02-17 17:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030217031008$3e63@gated-at.bofh.it>
[not found] ` <20030217031008$270a@gated-at.bofh.it>
2003-02-17 17:12 ` Arnd Bergmann [this message]
2003-02-07 4:59 [RFC] klibc for 2.5.59 bk Greg KH
2003-02-07 5:06 ` H. Peter Anvin
2003-02-07 5:10 ` Greg KH
2003-02-07 15:00 ` Alex Riesen
2003-02-09 12:57 ` Greg KH
2003-02-17 3:06 ` Kai Germaschewski
2003-02-17 5:50 ` Jeff Garzik
2003-02-17 18:02 ` Sam Ravnborg
2003-02-17 18:07 ` H. Peter Anvin
2003-02-17 18:36 ` Jeff Garzik
2003-02-17 18:57 ` Sam Ravnborg
2003-02-17 19:24 ` Jeff Garzik
2003-02-18 8:58 ` H. Peter Anvin
2003-02-18 9:17 ` Jeff Garzik
2003-02-18 9:36 ` Stelian Pop
2003-02-18 9:37 ` Stelian Pop
2003-02-18 9:46 ` Jeff Garzik
2003-02-18 9:45 ` Jeff Garzik
2003-02-18 9:56 ` Stelian Pop
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=200302171732.SAA00873@post.webmailer.de \
--to=arnd@bergmann-dalldorf.de \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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.