sys/io.h

Hello,
I was trying to compile a package from source rpm with
y2pmbuild.
Compilation failed with a message, that 'sys/io.h' is
missing. I looked
around in ARCHIVES.gz, and for other architectures it's in
glibc-devel,
but for PPC it's not there. What is the reason for it, and
how it could
be worked around?
Bye,
CzP

Ps:
 g++ -DHAVE_CONFIG_H -I. -I. -I../../../config -D_REENTRANT
-I../../../base/include -I../../../base/unix/include
-I../../../lib/utf8
-I../../../ui/include -I../../../lmc/include
-I../../../io/include
-I../../../mdb -I./sba -O2 -g -fmessage-length=0
-D_FORTIFY_SOURCE=2 -O2
-g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -MT rio.lo -MD -MP
-MF
.deps/rio.Tpo -c sba/rio.cpp  -fPIC -DPIC -o .libs/rio.o
sba/rio.cpp:66:21: error: sys/io.h: No such file or
directory

On Mon, Oct 02, Peter Czanik wrote:

> I was trying to compile a package from source rpm with
y2pmbuild.
> Compilation failed with a message, that 'sys/io.h' is
missing. I looked
> around in ARCHIVES.gz, and for other architectures it's
in glibc-devel,
> but for PPC it's not there. What is the reason for it,
and how it could
> be worked around?

This header contains non-portable i386 specific things. The
package has
to be rewritten to do the hardware IO properly.

Hello,

Olaf Hering írta:
> This header contains non-portable i386 specific things.
The package has
> to be rewritten to do the hardware IO properly.
>   
Thanks. I'm recompiling Packman packages for PPC and already
have a
growing list of uncompilable software (
h
ttp://wiki.links2linux.de/en/index.php/Packman:PPC ). At
the end I'll
try to find developers on PPC related forums, like
PPCZone.org, or even
here, to provide fixes to original developers, who don't
have access to
PPC hardware...
Bye,
CzP

On Mon, Oct 02, Peter Czanik wrote:

> I was trying to compile a package from source rpm with
y2pmbuild.
> Compilation failed with a message, that 'sys/io.h' is
missing. I looked
> around in ARCHIVES.gz, and for other architectures it's
in glibc-devel,
> but for PPC it's not there. What is the reason for it,
and how it could
> be worked around?

This header contains non-portable i386 specific things. The
package has
to be rewritten to do the hardware IO properly.

Hello,

Olaf Hering írta:
> This header contains non-portable i386 specific things.
The package has
> to be rewritten to do the hardware IO properly.
>   
Thanks. I'm recompiling Packman packages for PPC and already
have a
growing list of uncompilable software (
h
ttp://wiki.links2linux.de/en/index.php/Packman:PPC ). At
the end I'll
try to find developers on PPC related forums, like
PPCZone.org, or even
here, to provide fixes to original developers, who don't
have access to
PPC hardware...
Bye,
CzP

Hello,

larrystotlernetscape.net írta:
> Are your packages optimized for the G4?  How well does
that translate to the G3s?  Since I am not a programmer,
> I'm not really sure about a lot of these things.  Also,
I have a couple of Macs that I could do some re-compiling
> for you if you could give me instructions on how you do
it.  The fastest I have right now is only 400Mhz, 
> but I am looking for a faster processor around 1Ghz
shortly.  Thanx 
>   
Currently I use a 1Ghz G4 CPU (a Pegasos), but hope to
upgrade that to a
dual 970MP in a few months 

The packages are not optimized for the G4, at least not
intentionally.
Some packages use Altivec optimizations automatically, if
PPC is
detected, and as another non programmer, I can't help on
this. But most
of the packages should work fine on a G3.

Bye,
CzP

Hello,

larrystotlernetscape.net írta:
> Are your packages optimized for the G4?  How well does
that translate to the G3s?  Since I am not a programmer,
> I'm not really sure about a lot of these things.  Also,
I have a couple of Macs that I could do some re-compiling
> for you if you could give me instructions on how you do
it.  The fastest I have right now is only 400Mhz, 
> but I am looking for a faster processor around 1Ghz
shortly.  Thanx 
>   
Currently I use a 1Ghz G4 CPU (a Pegasos), but hope to
upgrade that to a
dual 970MP in a few months 

The packages are not optimized for the G4, at least not
intentionally.
Some packages use Altivec optimizations automatically, if
PPC is
detected, and as another non programmer, I can't help on
this. But most
of the packages should work fine on a G3.

Bye,
CzP

-----Original Message-----
 From: pczanikfang.fa.gau.hu
 
 >Currently I use a 1Ghz G4 CPU (a Pegasos), but hope to
upgrade that to a
 > dual 970MP in a few months  The
packages are not optimized for the G4, at least not
intentionally.h
 > Some packages use Altivec optimizations automatically,
if PPC is 
 >detected, and as another non programmer, I can't help
on this. But most 
 >of the packages should work fine on a G3. 
 
 When I compile stuff on my G3s, It always shows it is
compiling for Altivec. I had always assumed that if you
compile something for your hardware that it would compile it
for that system's particular optimizations. Like if you
compile for a P3, you don't get SSE2 compiled in since the
P3 doesn't support SSE2. Seems like compiling in Altivec
support on G3 systems would bloat the end result some. I
would have expected the ./configure script would detect
stuff like the G3 vs G4 and optimize accordingly.
 
 The packages do work, but I have had problems with MPlayer.
I would expect a G3/466 to be able to play an XviD since a
P-II/400 can, but maybe it has to do with the code being
more optimized for the x86 and less optimized for the
PPCs...... I dunno.
     
____________________________________________________________
____________
Check Out the new free AIM(R) Mail -- 2 GB of storage and
industry-leading spam and email virus protection.

-----Original Message-----
 From: pczanikfang.fa.gau.hu
 
 >Currently I use a 1Ghz G4 CPU (a Pegasos), but hope to
upgrade that to a
 > dual 970MP in a few months  The
packages are not optimized for the G4, at least not
intentionally.h
 > Some packages use Altivec optimizations automatically,
if PPC is 
 >detected, and as another non programmer, I can't help
on this. But most 
 >of the packages should work fine on a G3. 
 
 When I compile stuff on my G3s, It always shows it is
compiling for Altivec. I had always assumed that if you
compile something for your hardware that it would compile it
for that system's particular optimizations. Like if you
compile for a P3, you don't get SSE2 compiled in since the
P3 doesn't support SSE2. Seems like compiling in Altivec
support on G3 systems would bloat the end result some. I
would have expected the ./configure script would detect
stuff like the G3 vs G4 and optimize accordingly.
 
 The packages do work, but I have had problems with MPlayer.
I would expect a G3/466 to be able to play an XviD since a
P-II/400 can, but maybe it has to do with the code being
more optimized for the x86 and less optimized for the
PPCs...... I dunno.
     
____________________________________________________________
____________
Check Out the new free AIM(R) Mail -- 2 GB of storage and
industry-leading spam and email virus protection.

Hello,

larrystotlernetscape.net írta:
>   The packages do work, but I have had problems with
MPlayer. I would expect a G3/466 to be able to play an XviD
since a P-II/400 can, but maybe it has to do with the code
being more optimized for the x86 and less optimized for the
PPCs...... I dunno.
>   
Check out Xine, as they have also some good PPC developers
on board.
There are many different user interfaces for it, both for
KDE and Gnome,
but I still prefer xine-ui, which is easy to use and does
not need much
resources. Bye,
CzP

Hello,

larrystotlernetscape.net írta:
>   The packages do work, but I have had problems with
MPlayer. I would expect a G3/466 to be able to play an XviD
since a P-II/400 can, but maybe it has to do with the code
being more optimized for the x86 and less optimized for the
PPCs...... I dunno.
>   
Check out Xine, as they have also some good PPC developers
on board.
There are many different user interfaces for it, both for
KDE and Gnome,
but I still prefer xine-ui, which is easy to use and does
not need much
resources. Bye,
CzP