from their use
of __ identifiers) so I think you could just copy them to the
program and it would work on the Hurd or any other system.
> I dont really understand how endian issues are handled in linux, but i
> dont think it should be a problem under the Hurd because its just on one
> pl
On Sun, Oct 29, 2000 at 06:37:05PM +1100, Glenn McGrath wrote:
>
> I guess i should just find a way to ignore endian related code when
> compiling under the Hurd.
Not at all. In addition to what Nils said, there is a very easy way to find
the endianess of the system with an autoconf check at comp
gt; would be a waste of cpu time, if possible at all. (Some cpu:s can use
> either byteorder, but not x86).
>
> > I guess i should just find a way to ignore endian related code when
> > compiling under the Hurd.
> >
> > Anyone have any pointers to good docs on endian issue
pu:s can use
either byteorder, but not x86).
> I guess i should just find a way to ignore endian related code when
> compiling under the Hurd.
>
> Anyone have any pointers to good docs on endian issues?
Basically most endian dependent code are performance hacks (and most
I'v
The partitioning program im looking at makes calls to __cpu_le16 which
is defined in the /usr/include/linux/byteorder/ directroy but i cant see
an equivalent under the Hurd anywhere.
I dont really understand how endian issues are handled in linux, but i
dont think it should be a problem under the
5 matches
Mail list logo
