Linux development keeps clobbering poplog!
Matthias Scheutz reported that he cant start pop11 or basepo11 in
FC4 + the latest kernel 2.6.16
I confirmed this by installing this pre-built version on my FC4
desktop:
Date Name Origin Kernel SWSusp
2006/03/30 2.6.16-1.2069_FC4 FC4-Update 2.6.16.1 2.2.1
at Mathias Hensler's download page:
http://mhensler.de/swsusp/download_en.php
trying to run basepop11, or corepop produces an unstoppable stream
of access violation messages (I have to suspend and kill).
Everything works fine on an earlier build from the same repository
2006/03/03 2.6.15-1.1833_FC4 FC4-Update 2.6.15.5 2.2 FC4
I wonder if this is another of Redhat's security fixes?
I won't be able to do anything with that. It needs someone familiar
with something like gdb, which I have never used.
I am inclined to abandon Fedora and move to Ubuntu or Suse to avoid
these hassles.
A visitor a few days ago had no problem installing V15.6 on the
latest (I think?) Suse. The installation script just worked.
(But we still need to make changes to remove all traces of var-args:
I can no longer run
$usepop/pop/extern/lib/mklibpop
It complains about
$usepop/pop/extern/lib/c_core.c
Aaron
|