From: Takashi Oe <toe@unlserve.unl.edu>
To: Ken Offer <koffer@arlut.utexas.edu>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Problem with LinuxPPC Kernel 2.4.2 build
Date: Tue, 27 Feb 2001 10:52:08 -0600 (CST) [thread overview]
Message-ID: <Pine.A41.3.96LJ1.1b7.1010227104958.75940C-100000@unlserve.unl.edu> (raw)
In-Reply-To: <3A9BD79D.5BA06B7C@arlut.utexas.edu>
On Tue, 27 Feb 2001, Ken Offer wrote:
> Hi all,
>
> I downloaded the latest kernel and attempted to build it (i.e.
> ftp://ftp.fsmlabs.com/pub/linuxppc/linuxppc_2_4.snap.tar.bz2 20117 Kb
> Tue Feb 27 06:07:00 2001). After a while, along comes the curious
> error:
>
> make[1]: Entering directory `/usr/src/linuxppc_2_4_2/arch/ppc/coffboot'
> gcc -D__KERNEL__ -I/usr/src/linux/include -D__powerpc__ -c -o
> coffcrt0.o coffcrt0.S
> gcc -D__KERNEL__ -I/usr/src/linux/include -D__powerpc__ -O -fno-builtin
> -D__KERNEL__ -I/usr/src/linux/include -D__powerpc__ ppc -c -o start.o
> start.c
> gcc: cannot specify -o with -c or -S and multiple compilations
> make[1]: *** [start.o] Error 1
> make[1]: Leaving directory `/usr/src/linuxppc_2_4_2/arch/ppc/coffboot'
> make: *** [zImage] Error 2
>
> I am using gcc 2.95.3. Should I be using another version of the
> compiler that can handle the "-c" and "-S" options together, or is there
> a bug in the Makefile?
It's not a gcc problem. Maybe, wait a day or two and refetch the archive?
Takashi Oe
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-27 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 16:36 Problem with LinuxPPC Kernel 2.4.2 build Ken Offer
2001-02-27 16:52 ` Takashi Oe [this message]
[not found] ` <3A9C0793.2AEBE8B0@arlut.utexas.edu>
2001-02-27 22:16 ` LinuxPPC Kernel 2.4.2 build (multiple compilations error) Ken Offer
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=Pine.A41.3.96LJ1.1b7.1010227104958.75940C-100000@unlserve.unl.edu \
--to=toe@unlserve.unl.edu \
--cc=koffer@arlut.utexas.edu \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).