Hi,
On Tue, Apr 11, 2006 at 03:16:43PM -0700, Nexenta Systems, Inc. wrote:
> One of the issues we originally encountered is the artifact
> associated with SunOS 5.x (Solaris) ports of many OSS packages,
> in that they follow the following scheme:
>
> {i386,sparc}-{sun,pc}-solaris2.xx
This is the normalized form.
> For example, gcc/gcj/binutils config.guess implements such
> a logic. In many instances, however, dpkg-architecture output
> is used instead to override config.guess. When this is done
> with the default i486-solaris (for $DEB_HOST_GNU_TYPE), all
> of the Solaris-specific code end up getting disabled.
As I explained in the other mail config.sub should normalize those.
The question then is, have you added the that triplet recently to
config.*, because then it may be just a matter of time until it gets
propagated to all affected packages. We had to wait some time when we
added the triplet for GNU/kFreeBSD, or request packages to updates
those files.
Otherwise, why it does not get normalized correctly?
> One thing that I would like to add/correct with respect to
> our original proposal, is that the solaris2.11 string is not
> hard-coded and instead derived from uname (see "xx" above)
> at dpkg-architecture runtime. This should be addressed in
> the final patch.
Do you really need the complete release in the triplet? Is some
package checking for it for specific features? Can those features be
detected if present instead of relying on the system?
> If you think this is horribly broken, please advise us on
> an alternative (and the least invasive) solution.
See below. :) It's mostly that I don't see the need for special casing
solaris here, when all other arches have the same structure.
regards,
guillem
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
