From: Brian Gerst <bgerst@quark.didntduck.org>
To: Andrew Morton <akpm@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH] Remove last reference to LDFLAGS_BLOB
Date: Tue, 19 Oct 2004 22:01:06 -0400 [thread overview]
Message-ID: <4175C6E2.1080201@quark.didntduck.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 92 bytes --]
Nothing uses LDFLAGS_BLOB anymore, now that the arm binutils are fixed.
--
Brian Gerst
[-- Attachment #2: ldflags_blob --]
[-- Type: text/plain, Size: 1695 bytes --]
diff -urN linux-2.6.9-bk/arch/m32r/Makefile linux/arch/m32r/Makefile
--- linux-2.6.9-bk/arch/m32r/Makefile 2004-10-18 20:34:14.000000000 -0400
+++ linux/arch/m32r/Makefile 2004-10-19 17:40:55.614157644 -0400
@@ -5,7 +5,6 @@
LDFLAGS :=
OBJCOPYFLAGS := -O binary -R .note -R .comment -S
LDFLAGS_vmlinux := -e startup_32
-LDFLAGS_BLOB := --format binary --oformat elf32-m32r
CFLAGS += -pipe -fno-schedule-insns
CFLAGS_KERNEL += -mmodel=medium
diff -urN linux-2.6.9-bk/usr/initramfs_data.S linux/usr/initramfs_data.S
--- linux-2.6.9-bk/usr/initramfs_data.S 2003-12-17 21:59:42.000000000 -0500
+++ linux/usr/initramfs_data.S 2004-10-19 17:41:16.191659582 -0400
@@ -1,28 +1,6 @@
/*
initramfs_data includes the compressed binary that is the
filesystem used for early user space.
- Note: Older versions of "as" (prior to binutils 2.11.90.0.23
- released on 2001-07-14) dit not support .incbin.
- If you are forced to use older binutils than that then the
- following trick can be applied to create the resulting binary:
-
-
- ld -m elf_i386 --format binary --oformat elf32-i386 -r \
- -T initramfs_data.scr initramfs_data.cpio.gz -o initramfs_data.o
- ld -m elf_i386 -r -o built-in.o initramfs_data.o
-
- initramfs_data.scr looks like this:
-SECTIONS
-{
- .init.ramfs : { *(.data) }
-}
-
- The above example is for i386 - the parameters vary from architectures.
- Eventually look up LDFLAGS_BLOB in an older version of the
- arch/$(ARCH)/Makefile to see the flags used before .incbin was introduced.
-
- Using .incbin has the advantage over ld that the correct flags are set
- in the ELF header, as required by certain architectures.
*/
.section .init.ramfs,"a"
next reply other threads:[~2004-10-20 2:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 2:01 Brian Gerst [this message]
2004-10-20 8:05 ` [PATCH] Remove last reference to LDFLAGS_BLOB Russell King
2004-10-20 17:59 ` Marcelo Tosatti
2004-10-30 23:29 ` Sam Ravnborg
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=4175C6E2.1080201@quark.didntduck.org \
--to=bgerst@quark.didntduck.org \
--cc=akpm@osdl.org \
--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