From: Juan Quintela <quintela@mandrakesoft.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ralf Baechle <ralf@linux-mips.org>, mipslist <linux-mips@linux-mips.org>
Subject: Re: [PATCH]: for poor sools with old I2 & 64 bits kernel
Date: 21 Dec 2002 21:07:18 +0100 [thread overview]
Message-ID: <m2lm2jdtl5.fsf@demo.mitica> (raw)
In-Reply-To: <Pine.GSO.3.96.1021221194520.7158B-100000@delta.ds2.pg.gda.pl>
>>>>> "maciej" == Maciej W Rozycki <macro@ds2.pg.gda.pl> writes:
maciej> On 20 Dec 2002, Juan Quintela wrote:
ralf> Applied slightly modified. I removed two other unused targets.
>>
>> Please, add that back, and things will indeed compile :)
maciej> Ralf did that right -- it's annoying to have the COFF image for mips64
maciej> built in the mips tree. Unlike the intermediate object files, this target
maciej> is visible to a non-developer. But a few bits are missing, indeed. How
maciej> about the following patch? It's a trivial modification of what I use for
maciej> about half a year now.
BTW, are you using mips64 in a r4k? If so, do you need any additional
patches?
I am having some memory corruption :(
maciej> --
maciej> + Maciej W. Rozycki, Technical University of Gdansk, Poland +
maciej> +--------------------------------------------------------------+
maciej> + e-mail: macro@ds2.pg.gda.pl, PGP key available +
maciej> patch-mips-2.4.20-pre6-20021220-mips64-ecoff-0
maciej> diff -up --recursive --new-file linux-mips-2.4.20-pre6-20021220.macro/arch/mips64/boot/Makefile linux-mips-2.4.20-pre6-20021220/arch/mips64/boot/Makefile
maciej> --- linux-mips-2.4.20-pre6-20021220.macro/arch/mips64/boot/Makefile 2002-06-26 03:04:47.000000000 +0000
maciej> +++ linux-mips-2.4.20-pre6-20021220/arch/mips64/boot/Makefile 2002-12-21 14:23:32.000000000 +0000
maciej> @@ -22,11 +22,11 @@ all: vmlinux.ecoff addinitrd
maciej> vmlinux.ecoff: $(CONFIGURE) elf2ecoff $(TOPDIR)/vmlinux
maciej> ./elf2ecoff $(TOPDIR)/vmlinux vmlinux.ecoff $(E2EFLAGS)
maciej> -elf2ecoff: elf2ecoff.c
maciej> - $(HOSTCC) -o $@ $^
maciej> +elf2ecoff: $(TOPDIR)/arch/mips/boot/elf2ecoff.c
maciej> + $(HOSTCC) -I$(TOPDIR)/arch/mips/boot -I- -o $@ $^
maciej> -addinitrd: addinitrd.c
maciej> - $(HOSTCC) -o $@ $^
maciej> +addinitrd: $(TOPDIR)/arch/mips/boot/addinitrd.c
maciej> + $(HOSTCC) -I$(TOPDIR)/arch/mips/boot -I- -o $@ $^
maciej> # Don't build dependencies, this may die if $(CC) isn't gcc
maciej> dep:
It is better than mine.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2002-12-23 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 20:04 [PATCH]: for poor sools with old I2 & 64 bits kernel Juan Quintela
2002-12-19 21:01 ` Thiemo Seufer
2002-12-19 21:11 ` Juan Quintela
2002-12-19 21:28 ` Thiemo Seufer
2002-12-19 21:40 ` Juan Quintela
2002-12-19 22:22 ` Thiemo Seufer
2002-12-20 2:44 ` Ralf Baechle
2002-12-20 14:48 ` Juan Quintela
2002-12-21 18:55 ` Maciej W. Rozycki
2002-12-21 20:07 ` Juan Quintela [this message]
2002-12-21 21:28 ` Maciej W. Rozycki
2002-12-21 22:14 ` Juan Quintela
2002-12-21 22:49 ` Maciej W. Rozycki
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=m2lm2jdtl5.fsf@demo.mitica \
--to=quintela@mandrakesoft.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@linux-mips.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