On Tue, Apr 11, 2006 at 03:13:47PM -0700, Erast Benson wrote:
> On Wed, 2006-04-12 at 00:52 +0300, Guillem Jover wrote: 
> to match "debian" part of ostable (see below), i.e. pc-solaris2

Then this should not be really needed (see below).

> Indeed, I forget to add ostable snippet. Here it goes:

No problem.

> Index: ostable
> ===================================================================
> --- ostable     (.../pool/current)      (revision 20425)
> +++ ostable     (.../trunk)     (revision 20425)
> @@ -21,3 +21,4 @@
> netbsd         netbsd          netbsd[^-]*
> openbsd                openbsd         openbsd[^-]*
> hurd           gnu             gnu[^-]*
> +solaris         pc-solaris2     solaris.*

This one should be probably:

solaris         solaris         solaris[^-]*

When combining with the cpu and normalized it should give:

[EMAIL PROTECTED]:~$ /usr/share/misc/config.sub i386-solaris
i386-pc-solaris2

> > > Resulted printouts should be:
> > 
> > > $ dpkg-architecture
> > [...]
> > > DEB_BUILD_GNU_CPU=i486
> > 
> > Why is this different than the one on GNU_TYPE?
> 
> AFAIK, GNU_TYPE != GNU_CPU.

I meant in the way that GNU_CPU + GNU_SYSTEM == GNU_TYPE.

> > > DEB_BUILD_GNU_SYSTEM=solaris
> > 
> > This should match the GNU_TYPE as well, so solaris2.11.
> > 
> > > DEB_BUILD_GNU_TYPE=i386-pc-solaris2.11
> > 
> > The -pc- part should not be here.
> 
> Impossible. --build and --host parameters will be screwed all over.
> which will lead to erroneous platform detection in autoconf scripts.

config.sub takes care of normalizing:

[EMAIL PROTECTED]:~$ /usr/share/misc/config.sub i386-solaris2.11
i386-pc-solaris2.11

The same happens on a GNU/Linux system, when you feed the output from
"gcc -dumpmachine" to config.sub it gets normalized, and that's what
we are using in ostable:

[EMAIL PROTECTED]:~$ gcc -dumpmachine
i486-linux-gnu
[EMAIL PROTECTED]:~$ /usr/share/misc/config.sub i486-linux-gnu
i486-pc-linux-gnu

regards,
guillem


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to