[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linrad] gcc 4.0.x / lir01-35 ; Re: [linrad] Re: Linrad on a Debian System ??

Sir Roger & all!

Despite the upcoming Windows-version, Sir Leif seems still to put
a lot of effort into Linrad_Linux. The latest lir01-35 is proving
that. It is now doing a lookup of svgalib-versions and does the
appropriate things related to those during configuring/compiling.

As a trial-and-error pupil regarding Linux I regularly run into
severe problems while updating or changing packages. The last
properly running version has been built as a HD-install with a
Knoppix 4.0.2-EN, svgalib 1.9.23 and lir01-34. The latest version
lir01-35 also works, but exhibits (here) some fuzzy setup issues.

Leif mentioned that some changes were made to lir01-35 due to
compiling problems with certain distributions. Those occurred
probably under gcc 3.3.x .... Now, the above Knoppix contains
originally a gcc version 3.3.6 (you can check it with command
gcc -dumpversion). However, doing update/upgrade to version
4.0.x probably causes the "sanity check" issues [below].

Subsequently (on a couple of PC's) I used the Finnish version of
Knoppix 4.0.2 which had been modified with all possible upgrades
and already included gcc 4.0.2 .... It could not compile either
svgalib or lir01-34/lir01-35. After update/upgrade (gcc 4.0.3)
the situation was unchanged and it reported the preprocessor's
failed sanity check.

This seems to be an endless problem with new upcoming issues.
This calls again for a dedicated machine with a freeze on the
Knoppix_version side as soon as Linrad is up and running.

Regarding lir01-35 I ran into problems with the video resolution
(in the working system [with gcc 3.3.6]). I noticed the option
for more specific horizontal and vertical monitor deflection
frequencies. After a couple of guessed sync parameters I ended up
with a very limited selection of resolutions, finally resulting
in choices below 400 pixels. For some reason I did not manage
to re-enter new values and make changes through S or T parameter
routines, ultimately resulting in a jammed Linrad and reboot...

Thus Linrad still works with the Abit IC-7 and onboard ICH-5 audio
with lir01-34, but not with any newer distros including gcc 4.0.x
Also there is still the "should never happen" error with setad.c
when choosing the 1 RX-channel option (under lir01-34/lir01-35).

Wonder if we will see all this trouble under the upcoming 'Linrad'
for Windows multi-threaded version. Maybe I'm just dreaming....

            Good luck to you all!          73, "Zaba" OH1ZAA/2

P.S. Roger, are you using gcc 4.0.x on any of those Debian PC's?

At 17:42 24.10.2005 -0400, W3SZ wrote:


I have Linrad running on 4 Debian systems at the moment, each with unique

I have not seen that error message.

But each of my systems is 'Sarge'.  I have used kernels from 2.4.x thru
2.6.11 IIRK.

Sarge is now 'stable' and complete.  Why not upgrade to Sarge?

I suspect that the message means that  you don't have the gcc compiler

I am not at my Linux machine, but I think

apt-get update
apt-get install gcc

should take care of it if I am correct.



On Mon, 24 Oct 2005 13:43:43 -0400, Christoph Petermann <cpe@xxxxxxxx>

Hello all,

after big problems with Suse 10.0 I installed Debian (Knoppix 4.0.1 + a
lot of
Add-Ons) on my computer. Next I wanted to reinstall Linrad (1.34). But
here I

NASM compiles OK
SVGALIB seems to install OK
Linrad stops while ./configure like this:

configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.

I see there that some libraries are not ANSI C conform (???)

Anybody here got Linrad on a Debian ("Woody") system running ??

Roger Rehr

This message is sent to you because you are subscribed to
 the mailing list <linrad@xxxxxxxxxxxxxxxxxxxxx>.
To unsubscribe, E-mail to: <linrad-off@xxxxxxxxxxxxxxxxxxxxx>
To switch to the DIGEST mode, E-mail to <linrad-digest@xxxxxxxxxxxxxxxxxxxxx>
To switch to the INDEX mode, E-mail to <linrad-index@xxxxxxxxxxxxxxxxxxxxx>
Send administrative queries to  <linrad-request@xxxxxxxxxxxxxxxxxxxxx>