From: "David S. Miller" <davem@davemloft.net>
To: roland@redhat.com
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH]: Missing Sparc Implies
Date: Sat, 25 Feb 2006 01:45:00 -0000 [thread overview]
Message-ID: <20060224.174518.102972954.davem@davemloft.net> (raw)
In-Reply-To: <20060225014143.62DA3180A66@magilla.sf.frob.com>
From: Roland McGrath <roland@redhat.com>
Date: Fri, 24 Feb 2006 17:41:43 -0800 (PST)
> > From: Roland McGrath <roland@redhat.com>
> > Date: Fri, 24 Feb 2006 16:47:08 -0800 (PST)
> >
> > > I don't think ought to be necessary. If it is, I'd like to fix the
> > > configure magic so it's not. Those Implies files from the main source
> > > should cause those add-on directories to be searched too.
> >
> > This doesn't happen in the top-level either, that's why we need
> > sysdeps/unix/sysv/linux/sparc/sparc32/sparcv9b/Implies and friends
> > eventhough we have sysdeps/sparc/sparc32/sparcv9b/Implies.
>
> I'm not following you. The main tree tree has
> sysdeps/unix/sysv/linux/sparc/sparc32/sparcv9b/Implies already.
> Another one should not be required in the add-on too.
> The one would not be required either if we used sparcv9/sparcv9b instead.
I guess I don't understand how the "machine=" specification in the
configure scripts work... They look like file path names that the
build machinery tries one by one like this:
machine=a/b/c/d
step 1) try $(foo)/a/b/c/d
step 2) try $(foo)/a/b/c
step 3) try $(foo)/a/b
step 4) try $(foo)/a
You seem to be suggesting that it works another way.
next prev parent reply other threads:[~2006-02-25 1:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 23:47 David S. Miller
2006-02-25 0:47 ` Roland McGrath
2006-02-25 1:24 ` David S. Miller
2006-02-25 1:41 ` Roland McGrath
2006-02-25 1:45 ` David S. Miller [this message]
2006-02-25 1:46 ` Roland McGrath
2006-02-25 1:58 ` David S. Miller
2006-02-25 2:00 ` Roland McGrath
2006-02-25 2:07 ` David S. Miller
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=20060224.174518.102972954.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).