From: Michael Bacarella <mbac@nyct.net>
To: linux-kernel@vger.kernel.org
Subject: New ld must have --oformat instead of -oformat ?
Date: Fri, 16 Mar 2001 18:47:02 -0500 [thread overview]
Message-ID: <20010316184702.A19192@sync.nyct.net> (raw)
Riding the bleeding edge of debian leaves some interesting tastes.
Here's one:
[..much of build process omitted..]
make[1]: Entering directory `/usr/src/linux/arch/i386/boot'
gcc -E -D__KERNEL__ -I/usr/src/linux/include -D__BIG_KERNEL__ -traditional -DSVGA_MODE=NORMAL_VGA bootsect.S -o bbootsect.s
as -o bbootsect.o bbootsect.s
bbootsect.s: Assembler messages:
bbootsect.s:253: Warning: indirect lcall without `*'
ld -m elf_i386 -Ttext 0x0 -s -oformat binary bbootsect.o -o bbootsect
ld: cannot open binary: No such file or directory
make[1]: *** [bbootsect] Error 1
make[1]: Leaving directory `/usr/src/linux/arch/i386/boot'
make: *** [bzImage] Error 2
The line 'ld: cannot open binary: No such file or directory' is puzzling.
I redid the build a few times hoping that it would magically work the
next time (the Windows approach), I got over my fear and thought about it.
# ld -v
GNU ld version 2.11.90.0.1 (with BFD 2.11.90.0.1)
# ld --help 2>&1 | grep oformat
--oformat TARGET Specify target of output file
The Makefile only has one dash. Changing -oformat to --oformat in
arch/i386/boot/Makefile builds the kernel just fine.
Did I stumble onto something that is a non-issue or am I just lucky enough
to be the first one to trip over it?
--
Michael Bacaiella <mbac@nyct.net>
Technical Staff / System Development,
New York Connect.Net, Ltd.
next reply other threads:[~2001-03-16 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 23:47 Michael Bacarella [this message]
2001-03-17 0:12 ` New ld must have --oformat instead of -oformat ? davej
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=20010316184702.A19192@sync.nyct.net \
--to=mbac@nyct.net \
--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.