..and I'm ON! Questions, questions:

1) Simple things like moving windows around can consume fr�n 20 to 80% of CPU
power in X Windows. This hold true running both Gnome and KDE. The name of the
process is just plain "X". Before Mandrake 6.0 (with all the latest fixes) i
used Redhat 5.2. I can't recall it having the same problem, but I might just
not have noticed.

My hardware is a P120 with S3 Trio 64V+ videocard (using the Xfree86-S3 thingies
that come with the distribution)

2) I can't get the damned thing to compile anything! It always comes down to
this:

loading cache ./config.cache
checking host system type... i586-unknown-linux
checking target system type... i586-unknown-linux
checking build system type... i586-unknown-linux
checking cached information... ok
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... missing
checking for working automake... found
checking for working autoheader... missing
checking for working makeinfo... missing
checking for gcc... gcc
checking whether the C compiler (gcc -g ) works... no

configure: error: installation or configuration problem: C compiler cannot
create executables.  

My guess is this has something to do with pgcc which has, until very
recently, been one of my main sources of enthusiasm considering
Mandrake.

Still, just writing "gcc" seems to work fine..

[root@fysgr473 ssh-2.0.13]# gcc
pgcc: No input files
[root@fysgr473 ssh-2.0.13]#      

3) Speakfreely. If I remember right this is distributed with Redhat..maybe I
should complain to someone else.
Anyhow.. I have a Soundblaster AWE 64 VE which definately is full-duplex. I
know, because I use Speakfreely for Windows and it says in the sound cards'
configure panels, as well.

Very annoyingly however, the OSS sounddrivers distributed with Redhat and
Mandrake DOESN'T seem to support full duplex, and I can't get Speakfreely to
work properly.

I know there's some switch use can use for half-duplex when compiling it, but
that wouldn't be using the hardware fully (and I couldn't get it to compile).
No, go with the RPM, I'd say.

/ Carl

--
--------------------------------------------------------------
Ille, qui solus vadit
http://www.ing.umu.se/~en98ced
--------------------------------------------------------------

Reply via email to