From: "David S. Miller" <davem@redhat.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: george anzinger <george@mvista.com>,
Davide Libenzi <davidel@xmailserver.org>,
Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.46
Date: 04 Nov 2002 22:30:34 -0800 [thread overview]
Message-ID: <1036477834.31982.0.camel@rth.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0211042035330.20254-100000@chaos.physics.uiowa.edu>
On Mon, 2002-11-04 at 18:37, Kai Germaschewski wrote:
> On Mon, 4 Nov 2002, george anzinger wrote:
>
> > I think we need a newer objcopy :(
>
> Alternatively, use this patch. (It's not really needed to force people to
> upgrade binutils when ld can do the job, as it e.g. does in
> arch/i386/boot/compressed/Makefile already).
Does not work for me at all on sparc64, it complains that *.gz has an
unknown file format.
Why not just hexdump the thing into an array of char foo.c file,
then compile that.
next prev parent reply other threads:[~2002-11-05 6:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 23:13 Linux v2.5.46 Linus Torvalds
2002-11-04 23:44 ` Udo A. Steinberg
2002-11-05 11:50 ` [patch] " Gerd Knorr
2002-11-04 23:58 ` Miquel van Smoorenburg
2002-11-05 0:05 ` David T Hollis
2002-11-05 0:10 ` Adrian Bunk
2002-11-05 0:40 ` george anzinger
2002-11-05 0:43 ` Davide Libenzi
2002-11-05 1:15 ` george anzinger
2002-11-05 1:30 ` Davide Libenzi
2002-11-05 2:37 ` Kai Germaschewski
2002-11-05 4:01 ` Skip Ford
2002-11-05 4:17 ` Davide Libenzi
2002-11-05 4:12 ` Skip Ford
2002-11-05 15:58 ` Kai Germaschewski
2002-11-05 6:30 ` David S. Miller [this message]
2002-11-05 9:35 ` Linux v2.5.46 (compile error) Michael Kummer
2002-11-05 9:38 ` Linux v2.5.46 (compile error) (rivafb) Michael Kummer
2002-11-09 1:07 ` James Simmons
2002-11-05 11:09 ` Linux v2.5.46 (compile error) Alan Cox
2002-11-05 16:02 ` Linux v2.5.46 Kai Germaschewski
2002-11-05 16:08 ` Linus Torvalds
2002-11-05 17:25 ` Alan Cox
2002-11-05 16:59 ` David S. Miller
2002-11-06 21:22 ` Robert Love
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=1036477834.31982.0.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=davidel@xmailserver.org \
--cc=george@mvista.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox