This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Complicated config puzzle (m68k-apollo-bsd, v810, aix4.3+ maintainers please reply)
- From: Nathanael Nerode <neroden at twcny dot rr dot com>
- To: gcc at gcc dot gnu dot org
- Cc: gdb at sources dot redhat dot com, binutils at sources dot redhat dot com
- Date: Sat, 9 Nov 2002 18:47:29 -0500
- Subject: Complicated config puzzle (m68k-apollo-bsd, v810, aix4.3+ maintainers please reply)
- Reply-to: neroden at twcny dot rr dot com
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