From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc@gcc.gnu.org
Cc: gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Complicated config puzzle (m68k-apollo-bsd, v810, aix4.3+ maintainers please reply)
Date: Sat, 09 Nov 2002 15:47:00 -0000 [thread overview]
Message-ID: <20021109234729.GA15157@doctormoo> (raw)
I'm trying to untangle the maze that is toplevel configuration. I need
some advice as to desired behavior.
For the *host* m68k-apollo-bsd, currently
host=build: sets BISON=yacc
host!=build: sets BISON=bison
BISON represents a build-side tool, correct?
So we should set BISON=yacc whenever this is the *build* machine, right?
For the *target* aix >= 4.3, currently
host=build: sets AR_FOR_TARGET=ar -X32_64
sets NM_FOR_TARGET=nm -B -X32_64
host!=build: sets AR_FOR_TARGET=${target_alias}-ar
sets NM_FOR_TARGET=${target_alias}-nm
This just doesn't seem right at all. Under what circumstances do we
want these flags? It looks like they're always valid for GNU ar, GNU
nm, AIX ar, and AIX nm; I'm guessing we want them even in the Canadian
case.
I'm further guessing that we want ${target_alias}-ar whenever
build!=target, with the flags added.
I can do this. :-)
For the *target* v810*, currently
host=build: sets CC_FOR_TARGET=ca732 -ansi
sets AS_FOR_TARGET=as732
sets AR_FOR_TARGET=ar732
host!=build: sets CC_FOR_TARGET = ${target_alias}-gcc
sets AS_FOR_TARGET = ${target_alias}-as
sets AR_FOR_TARGET = ${target_alias}-ar
This also looks wrong (very, very wrong), but I'm not sure what to do
with it. I'll hazard a guess that the '732' compilers should be used
when build=target=v810* and not otherwise? But I could easily be wrong.
These three points are the next things holding up the top level
autoconfiscation. Hope to have them resolved soon.
--Nathanael
next reply other threads:[~2002-11-09 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 15:47 Nathanael Nerode [this message]
2002-11-09 18:57 ` Ian Lance Taylor
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=20021109234729.GA15157@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
/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