Aaron Sloman wrote:
> I ran the patches on a version of v15.6 poplog to update the sources for
> AMD64, then rebuilt the tar file and modified the install script to
> recompile the poplog sources after un-tarring.
>
>
> I now have a test version of poplog v15.6 for AMD64
>
> (So this takes a little longer to install than the 32 bit version,
> which has the sources precompiled).
>
> One person on the South Birmingham Linux user group volunteered to test
> it on an AMD64 running gentoo linux.
>
> As far as I can tell from the log file he sent me, everything worked
> except the attempt to run popling_cmnd before recompiling the sources,
> naturally. (I'll change the install script later.)
>
> I.e. all the saved images got built in $usepop/pop/lib/psv as expected,
> but when he tried to run pop11 he got a segmentation fault (i.e. the
> saved image would not start).
>
> I had the same behaviour when I tried to install poplog on Fedora core 2,
> and I concluded that it was due to some interaction with the 2.6 linux
> kernel.
>
> However others have run poplog on 2.6 kernels, including Suse 9.1
>
The patch was developed on Madrake 9.2 upgraded to stock 2.6.8.1 kernel,
with libc-2.3.2. AFAIK this libc do not support NPTL. So one possible
problem is NPTL. Another is 'stack randomization' -- newer distributions
put program stack at random location. Poplog tries to move it to a
fixed location, assuming that the space it used previously is still
available.
> If anyone who has an AMD64 machine running a 64bit linux would like to
> check out the package the instructions are below, and also available in
>
> http://www.cs.bham.ac.uk/research/poplog/amd64/AREADME.txt
>
> NOTE:
> I have the impression from the patch used to make the AMD64 version
> that the X11 libraries are in a different directory, i.e.
>
> /usr/X11R6/lib64
>
> so I have changed the checking script to look there instead of in
>
> /usr/X11R6/lib
>
Actually, one should check both places. "Pure" 64-bit distributions
use the same location as 32-bit systems. Systems supporting both
32-bit and 64-bit binaries frequently use ".../lib64" directories
for 64-bit libraries, but there is considerable variation.
--
Waldek Hebisch
hebisch@math.uni.wroc.pl
|