Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@mandrakesoft.com>
To: Ralf Baechle <ralf@linux-mips.org>, mipslist <linux-mips@linux-mips.org>
Subject: [PATCH]: for poor sools with old I2 & 64 bits kernel
Date: 19 Dec 2002 21:04:12 +0100	[thread overview]
Message-ID: <m2el8dixmr.fsf@demo.mitica> (raw)


Hi
        this small patch made possible to compile a 64bit kernel for
        people that have old proms that only accept ecoff.  As usual
        stolen from the 32 bits version.

        The easiest way is creating the file in arch/mips/boot,
        otherwise we need to copy elf2ecoff.c to mips64.

Later, Juan.

Index: arch/mips64/Makefile
===================================================================
RCS file: /home/cvs/linux/arch/mips64/Makefile,v
retrieving revision 1.22.2.20
diff -u -r1.22.2.20 Makefile
--- arch/mips64/Makefile	26 Nov 2002 11:19:52 -0000	1.22.2.20
+++ arch/mips64/Makefile	19 Dec 2002 19:48:43 -0000
@@ -255,6 +255,9 @@
 	$(OBJCOPY) -O $(64bit-bfd) --remove-section=.reginfo --change-addresses=0xa800000080000000 $< $@
 endif
 
+vmlinux.ecoff: vmlinux
+	$(MAKE) -C arch/mips/boot $@
+
 zImage: vmlinux
 	@$(MAKEBOOT) zImage
 


-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

             reply	other threads:[~2002-12-19 19:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 20:04 Juan Quintela [this message]
2002-12-19 21:01 ` [PATCH]: for poor sools with old I2 & 64 bits kernel 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
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=m2el8dixmr.fsf@demo.mitica \
    --to=quintela@mandrakesoft.com \
    --cc=linux-mips@linux-mips.org \
    --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