From: Casper H.S. Dik on


Is the catopen() file created on SPARC or on x86?

Both need a different file.

The catopen files are binary files and they can only be
used on system with same-endian.

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
From: mukesh on
On Nov 6, 7:17 pm, Casper H.S. Dik <Casper....(a)Sun.COM> wrote:
> Is the catopen() file created on SPARC or on x86?
>
> Both need a different file.
>
> The catopen files are binary files and they can only be
> used on system with same-endian.
>
> Casper
> --
> Expressed in this posting are my opinions.  They are in no way related
> to opinions held by my employer, Sun Microsystems.
> Statements on Sun products included here are not gospel and may
> be fiction rather than truth.

Hi Casper,

thanks for your quik response !!

the catalog files are created on the respective platform.

FYI:
If exported NLSPATH=/home/expert/msg/%N.cat in that case it works fine
on solaris-opteron.

The question here is why the catopen() library function behaving in
the different way on solaris-opteron and other UNIX platforms(solaris-
sparc, AIX, HPUX, LINUX) ?


-
Mukesh
From: Barry Margolin on
In article
<7a46ae7d-621a-4b82-bff8-2aba41b014c3(a)l2g2000yqd.googlegroups.com>,
mukesh <mukeshmca2(a)gmail.com> wrote:

> On Nov 6, 7:17�pm, Casper H.S. Dik <Casper....(a)Sun.COM> wrote:
> > Is the catopen() file created on SPARC or on x86?
> >
> > Both need a different file.
> >
> > The catopen files are binary files and they can only be
> > used on system with same-endian.
> >
> > Casper

Casper, did you read the truss he posted? It got an error from open(),
so how can the file format be relevant?

>
> Hi Casper,
>
> thanks for your quik response !!
>
> the catalog files are created on the respective platform.
>
> FYI:
> If exported NLSPATH=/home/expert/msg/%N.cat in that case it works fine
> on solaris-opteron.
>
> The question here is why the catopen() library function behaving in
> the different way on solaris-opteron and other UNIX platforms(solaris-
> sparc, AIX, HPUX, LINUX) ?

For some reason, those other platforms are adding a .cat suffix, even
though it wasn't in your NLSPATH value. I don't see any mention of this
default suffix in the POSIX specification, I guess it's an extension.

So if your catalog filename ends in .cat, you need to include that in
either NLSPATH or in the name argument to catopen(), rather than depend
on this non-portable behavior.

--
Barry Margolin, barmar(a)alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
From: mukesh on
On Nov 7, 7:17 am, Barry Margolin <bar...(a)alum.mit.edu> wrote:
> In article
> <7a46ae7d-621a-4b82-bff8-2aba41b01...(a)l2g2000yqd.googlegroups.com>,
>
>  mukesh <mukeshm...(a)gmail.com> wrote:
> > On Nov 6, 7:17 pm, Casper H.S. Dik <Casper....(a)Sun.COM> wrote:
> > > Is the catopen() file created on SPARC or on x86?
>
> > > Both need a different file.
>
> > > The catopen files are binary files and they can only be
> > > used on system with same-endian.
>
> > > Casper
>
> Casper, did you read the truss he posted?  It got an error from open(),
> so how can the file format be relevant?
>
>
>
> > Hi Casper,
>
> > thanks for your quik response !!
>
> > the catalog files are created on the respective platform.
>
> > FYI:
> > If exported NLSPATH=/home/expert/msg/%N.cat in that case it works fine
> > on solaris-opteron.
>
> > The question here is why the catopen() library function behaving in
> > the different way on solaris-opteron and other UNIX platforms(solaris-
> > sparc, AIX, HPUX, LINUX) ?
>
> For some reason, those other platforms are adding a .cat suffix, even
> though it wasn't in your NLSPATH value.  I don't see any mention of this
> default suffix in the POSIX specification, I guess it's an extension.
>
> So if your catalog filename ends in .cat, you need to include that in
> either NLSPATH or in the name argument to catopen(), rather than depend
> on this non-portable behavior.
>
> --
> Barry Margolin, bar...(a)alum.mit.edu
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***
> *** PLEASE don't copy me on replies, I'll read them in the group ***

Other platforms are not adding .cat suffix rather they are returning
-1, it is succeeding only on solaris -x86 platform. That's why I
thought of posting this issue.

Why catopen() behaves in different way on solaris-x86 than other UNIX
platforms(including solaris-sparc).
Is there any implementaion specific issue.
if yes .. then in that case I think atleast it should consistent
across both the solaris-x86 and the solaris-sparc platforms.

-
Mukesh
From: Casper H.S. Dik on
Barry Margolin <barmar(a)alum.mit.edu> writes:

>In article
><7a46ae7d-621a-4b82-bff8-2aba41b014c3(a)l2g2000yqd.googlegroups.com>,
> mukesh <mukeshmca2(a)gmail.com> wrote:

>> On Nov 6, 7:17�pm, Casper H.S. Dik <Casper....(a)Sun.COM> wrote:
>> > Is the catopen() file created on SPARC or on x86?
>> >
>> > Both need a different file.
>> >
>> > The catopen files are binary files and they can only be
>> > used on system with same-endian.
>> >
>> > Casper

>Casper, did you read the truss he posted? It got an error from open(),
>so how can the file format be relevant?

I didn't react to that posting; but yes, it looks like the file wasn't
even there.

>For some reason, those other platforms are adding a .cat suffix, even
>though it wasn't in your NLSPATH value. I don't see any mention of this
>default suffix in the POSIX specification, I guess it's an extension.

But why does it work differently between Solaris SPARC & x86?

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.