From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Randolph Chung <tausq@debian.org>
Cc: "B. Douglas Hilton" <bdhilton@charter.net>,
debian-hppa@lists.debian.org,
parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: Compiling glide-2001.01.26 on hppa
Date: Sat, 24 Aug 2002 18:37:51 -0400 [thread overview]
Message-ID: <20020824223751.GA16590@systemhalted> (raw)
In-Reply-To: <20020824180137.GB25592@tausq.org>
> > cc -O6 -m486 -fomit-frame-pointer -funroll-loops \
> > -fexpensive-optimizations -ffast-math -DBIG_OPT -I. \
> > -I/usr/src/glide-2001.01.26/build-tree/glide2x/swlibs/include \
> > -I/usr/src/glide-2001.01.26/build-tree/glide2x/cvg/include \
> > -DENDB -DX11 -Wall -fPIC -DPIC -c -o fx64.o fx64.c
> >
> > cc1: Invalid option `486'
> >
> >
> > My question is, what incantation should I use on hppa to
> > replace the '-O6 -m486 -f...' CFLAGS?
>
> i would suggest just using "-O2" for now....
>
> randolph
>
The issues revolves around the fact that the source tree and
assembly for some of pieces you want to build are meant for x86 boxes.
Though from a cusory glance it looks like the .c files are present for
these bits (so you can revert to those).
Right off the top:
tvg/makefile.linux:CFLAGS = -O -m486 -fomit-frame-pointer $(LCDEFS) $(LCOPTS) $(LCINC)
glide2x/sst1/init/initvg/makefile.unix:CFLAGS = -O -m486 -fomit-frame-pointer $(LCDEFS) $(LCOPTS) $(LCINC)
glide2x/swlibs/include/make/3dfx.linux.mak:CNODEBUG = -O6 -m486 -fomit-frame-pointer -funroll-loops \
glide2x/swlibs/include/make/3dfx.mak:CNODEBUG = -O6 -m486 -fomit-frame-pointer -funroll-loops \
glide2x/swlibs/include/make/3dfx.mak:CNODEBUG = -O6 -m486 -fomit-frame-pointer -funroll-loops \
glide2x/swlibs/include/make/makefile.autoconf.bottom:GLIDE_DEBUG_GCFLAGS = -O6 -m486
glide3x/swlibs/include/make/3dfx.linux.mak:CNODEBUG = -O6 -m486 -fomit-frame-pointer -funroll-loops \
glide3x/swlibs/include/make/3dfx.mak:CNODEBUG = -O6 -m486 -fomit-frame-pointer -funroll-loops \
glide3x/swlibs/include/make/3dfx.mak:CNODEBUG = -O6 -m486 -fomit-frame-pointer -funroll-loops \
glide3x/swlibs/include/make/makefile.autoconf.bottom:GLIDE_DEBUG_GCFLAGS = -O6 -m486
swlibs/include/make/3dfx.linux.mak:CNODEBUG = -O6 -m486 -fomit-frame-pointer -funroll-loops \
swlibs/include/make/3dfx.mak:CNODEBUG = -O6 -m486 -fomit-frame-pointer -funroll-loops \
swlibs/include/make/3dfx.mak:CNODEBUG = -O6 -m486 -fomit-frame-pointer -funroll-loops \
swlibs/include/make/makefile.autoconf.bottom:GLIDE_DEBUG_GCFLAGS = -O6 -m486
These files will give you some grief and need to be changed; remove the -m486 bit.
You either need to produce .dpatch's for the deb to use or stop building
the deb and do it by hand with the upstream source.
You've got me all excited about seeing this work :) I have a Vodoo1 (Monster3D)
PCI card that I might be tempted to ressurect.
Hope this helps. Sorry about there not being a _magic_ switch :)
c.
next prev parent reply other threads:[~2002-08-24 22:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-24 17:55 [parisc-linux] Compiling glide-2001.01.26 on hppa B. Douglas Hilton
2002-08-24 18:01 ` [parisc-linux] " Randolph Chung
2002-08-24 18:01 ` Randolph Chung
2002-08-24 22:37 ` Carlos O'Donell [this message]
2002-08-27 4:02 ` Christopher C. Chimelis
2002-08-27 4:02 ` Christopher C. Chimelis
2002-08-24 22:37 ` Carlos O'Donell
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=20020824223751.GA16590@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=bdhilton@charter.net \
--cc=debian-hppa@lists.debian.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.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.