linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Troy Benjegerdes <hozer@drgw.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: arch/ppc/boot broken include in currenty 2_4_devel
Date: Wed, 28 Nov 2001 16:22:43 -0600	[thread overview]
Message-ID: <20011128162242.M23942@altus.drgw.net> (raw)


Somehow, the

CFLAGS	+= -fno-builtin -D__BOOTER__ -I$(TOPDIR)/arch/$(ARCH)/boot/include

line in arch/ppc/boot/Makefile is not getting picked up, causeing me
problems like:

make[3]: Entering directory
`/scratch/mvp/linuxppc_2_4_galileo/arch/ppc/boot/lib'
ppc_8xx-gcc -D__KERNEL__ -I/scratch/mvp/linuxppc_2_4_galileo/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -D__powerpc__ -fsigned-char -msoft-float
-pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -O2 -ggdb   -c -o
zlib.o zlib.c
zlib.c: In function `inflateEnd':
zlib.c:330: too many arguments to function
zlib.c: At top level:
zlib.c:337: parse error before `('


because it's picking up the wrong zlib.h.

I've been messing around with the makefile, but I can't get it to do
anything that seems sensible.

--
Troy Benjegerdes | master of mispeeling | 'da hozer' |  hozer@drgw.net
-----"If this message isn't misspelled, I didn't write it" -- Me -----
"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's
why I draw cartoons. It's my life." -- Charles Shulz

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-11-28 22:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28 22:22 Troy Benjegerdes [this message]
2001-11-28 22:40 ` arch/ppc/boot broken include in currenty 2_4_devel Mark A. Greer
2001-11-28 23:04 ` Troy Benjegerdes

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=20011128162242.M23942@altus.drgw.net \
    --to=hozer@drgw.net \
    --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).