Hi Aaron,
When I read that changes had been to the linking mechanism on
Linux Poplog I thought I would check if they changed anything
when installing Linux Poplog on FreeBSD and DragonFly BSD.
It looks as though something has but the work-around is easy
enough. The procedure is the same until you get to the stage
that you wish to run ./INSTALL_EVERYTHING_WITH_MOTIF ; this
will fail if run now so run the steps manually,
bash2.05b# zcat linux-poplog/linux-poplog.tar.gz | tar xf -
bash2.05b# ln -s linux-poplog/startup .
bash2.05b# cd linux-poplog
Now change LINK_MOTIF_POPLOG in this directory in the
following way. If you have a minimal Linux set-up like me
you won't have an editor so will have to exit out of the
/compat/linux chroot to use one and then chroot back in.
(snip)
ln -sf /usr/X11R6/lib/libXm.so.3 $popexternlib/libXm.so
echo ' Motif libXm.so.3 found and linked to $popexternlib/libXm.so'
## Not sure the rest is needed
## rm -f $usepop/pop/com/popenv* # COMMENT #
## cp -p $usepop/pop/com/motif3/* $usepop/pop/com # THESE #
## echo 'Altered $usepop/pop/com/popenv* for Motif 3' # OUT #
elif [ -f /usr/X11R6/lib/libXm.so.2 ]
then
ln -sf /usr/X11R6/lib/libXm.so.2 $popexternlib/libXm.so
echo ' Motif libXm.so.2 found and linked to $popexternlib/libXm.so'
## Not sure the rest is needed
## rm -f $usepop/pop/com/popenv* # COMMENT #
## cp -p $usepop/pop/com/motif2/* $usepop/pop/com # THESE #
## echo 'Altered $usepop/pop/com/popenv* for Motif 2' # OUT #
(snip)
Then run the scripts in this directory like so,
bash2.05b# ./INSTALL_POPLOG LINK_MOTIF_POPLOG
since I am using the default install directory.
This is on DragonFly BSD linking with Motif. I haven't tried
linking without Motif but looking at LINK_NOMOTIF_POPLOG it
should be ok. I expect the same to occur on FreeBSD since the
DragonFly people use the FreeBSD ports system but I no longer
have a FreeBSD installation to check with.
All the best,
John Duncan
>From proy@conceptualspeech.com Tue Jan 11 21:41:56 2005
Path: news.demon.co.uk!mutlu.news.demon.net!peer-uk.news.demon.net!kibo.news.demon.net!demon!news-lond.gip.net!news.gsl.net!gip.net!news.tele.dk!news.tele.dk!small.news.tele.dk!lnewsoutpeer01.lnd.ops.eu.uu.net!lnewsinpeer00.lnd.ops.eu.uu.net!emea.uu.net!feed1.jnfs.ja.net!feed2.jnfs.ja.net!jnfs.ja.net!warwick!news-out.ftel.co.uk!bhamcs!not-for-mail
From: "Philippe Roy" <proy@conceptualspeech.com>
Newsgroups: comp.lang.pop
Subject: running "bye" on OS X
Date: Tue, 11 Jan 2005 21:41:56 +0000 (UTC)
Organization: School of Computer Science, The University of Birmingham
Lines: 51
Message-ID: <cs1h74$qpi$1@soapbox.cs.bham.ac.uk>
X-Trace: soapbox.cs.bham.ac.uk 1105479716 27442 147.188.194.39 (11 Jan 2005 21:41:56 GMT)
X-Complaints-To: abuse@cs.bham.ac.uk
X-Relay-Info: Relayed through cs.bham.ac.uk MAIL->NEWS gateway
Xref: news.demon.co.uk comp.lang.pop:1373
[Forwarded from pop-forum]
Hi! Great advances in the poplog port to OS X.
We now have it initializing, and the console is prompting for commands.
We do have a new problem.
When we type an instruction the system does not
execute it correctly, we are trying to figure out what is
happening, so we modified the function sysPUSHQ in
vm_plant.p in order to evaluate the "bye" instruction
by adding this line:
cucharout(\n'), printf (item, "sysPUSHQ": %P),
cucharout(`\n`);
And we also modified sysexit in sysexit.p by adding
this line:
cucharout(`\n`), printf('Entro a sysexit'),
cucharout(`\n`);
when we execute newpop11 on LINUX and type the command
"bye" on the console we have the following printing
result:
SyspushQ: sysexit
SyspushQ: (
SyspushQ: )
SyspushQ: ;
Entro a sysexit
And after that, it exits the application normally.
On OS X we get this results:
SyspushQ: sysexit
SyspushQ: (
SyspushQ: )
SyspushQ: ;
What should happen then is sysexit being called. We would
like to know what exactly should be called once these SyspushQ
are done.
thanks a lot for any help you can give us!
====
Aaron Sloman, ( http://www.cs.bham.ac.uk/~axs/ )
|