This is the mail archive of the libc-hacker@sourceware.org mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
From: Roland McGrath <roland@redhat.com>
Date: Fri, 24 Feb 2006 17:08:23 -0800 (PST)
> > I've sent a patch for scripts/config.sub to config-patches the other
> > day, so that part of adding sparcv9v and sparc64v should show up
> > eventually.
>
> As a rule we don't put in new configuration support until the canonical
> config.sub groks it.
config.sub really puts an unreasonable monkey wrench into the works
for doing development of new build targets for any GNU package.
It ususally takes about a week for a config.sub patch get handled,
integrated, and propagated into the necessary trees. Nothing impedes
forward progress quite like this thing.
> > This adds the "sparcv9v-*" and "sparc64v-*" build targets, the
> > optimized memcpy/memset for that platform, and the necessary Implies
> > files.
>
> I think this would be better done without Implies files. Just use
> machine=sparc/sparc32/sparcv9/sparcv9v and the right things should happen.
Will that actually work?
I thought "machine=" takes a file path name, not a list of compatible
targets. For example:
sparcv8plus | sparcv8plusa | sparcv9)
base_machine=sparc machine=sparc/sparc32/sparcv9 ;;
I read that as meaning: search ${foo}/sparc/sparc32/sparcv9, else
${foo}/sparc/sparc32, else ${foo}/sparc
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |