From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] linker script preprocessing problem
Date: Wed, 22 Nov 2000 02:29:32 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205763@msgid-missing> (raw)
In order to compile the test10 kernel with current FSF binutils/gcc sources,
I needed to add the -traditional option to the command that preprocesses the
linker scripts. Otherwise the cpp output isn't valid linker input because it
has been tokenized for C.
The output looks a little strange, so there might be a temporary FSF gcc
instability here, but in general you should always use -traditional when
preprocessing something that isn't C source code. Or else use something
that isn't C specific, like m4.
arch/ia64/Makefile:
*** Makefile~ Mon Oct 9 17:54:53 2000
--- Makefile Tue Nov 21 17:49:45 2000
*************** vmlinux: arch/$(ARCH)/vmlinux.lds
*** 96,102 ****
arch/$(ARCH)/vmlinux.lds: arch/$(ARCH)/vmlinux.lds.S FORCE
$(CPP) -D__ASSEMBLY__ -C -P -I$(HPATH) -I$(HPATH)/asm-$(ARCH) \
! arch/$(ARCH)/vmlinux.lds.S > $@
FORCE: ;
--- 96,102 ----
arch/$(ARCH)/vmlinux.lds: arch/$(ARCH)/vmlinux.lds.S FORCE
$(CPP) -D__ASSEMBLY__ -C -P -I$(HPATH) -I$(HPATH)/asm-$(ARCH) \
! arch/$(ARCH)/vmlinux.lds.S -traditional > $@
FORCE: ;
reply other threads:[~2000-11-22 2:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590678205763@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@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