[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Jul 29 15:37:58 2003 
Subject:Re: Debian Unstable and Poplog 
From:john duncan 
Volume-ID:1030729.03 

On Sun, 27 Jul 2003 23:44:23 +0000, Aaron Sloman wrote:


>
> 
> Glad to hear that problem is solved.
> 
>>              I gave the new tarball a try but on Debian I have to
>> comment out poplink_cmnd from LINK_MOTIF_POPLOG, which is a problem since
>> where it is seems to be over written whenever I change it.
> 

(snip)

       O.K Aaron,
                 I could not get your new scripts to do the right
thing by Debian Unstable, it would not install. I have managed to rewrite
INSTALL_MOTIF_POPLOG so that it does and links with OpenMotif 3.0.1 not
Lesstif ( no more X TOOLKIT Warnings ).
                 I am untarring the main tarball in /usr/local/poplog/src
then cd linux-poplog and then zcat linux-poplog.tar.gz | tar xf -
                 Then I go to
/usr/local/poplog/src/linux-poplog/linux-poplog
and alter INSTALL_MOTIF_POPLOG for bash and comment out the call to
LINK_MOTIF_POPLOG and uncomment what is needed from LINK_MOTIF_POPLOG.
                 Same as the last tarball on Debian Unstable it gives
errors and what has been going on I think is that while the system images
are made in $popsys the standard images end up in $poplocalbin where the
installation scripts can't find them.
                 I no longer have an old install of Poplog so can not
check to see what should be in $poplocalbin just after installation but I
have clisp.psv pml.psv prolog.psv xved.psv xvedpro.psv startup.psv in
there. Is this right?
                I am still looking to see if I understand this right.
                                         All the best,
                                           John Duncan