[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Wed, 12 May 2004 07:51:56 +1000 
Subject:Re: FreeBSD Poplog without a Linux Partition (For Bernard) 
From:John Duncan 
Volume-ID: 

Aaron Sloman <A.Sloman@cs.bham.ac.uk> writes:

Hi Aaron,

> Responding to John Duncan <agley@optusnet.com.au>
>
> Many thanks for your summary of what freebsd users need to do.
> With your permission, I'd like to put it in file in this
> currently empty directory
>
>     http://www.cs.bham.ac.uk/research/poplog/freebsd/
>

   If you can hold off a bit I will try to refine it a bit. I am on
night shift at the moment and rushed a bit to try and get Bernard in
case he gave Poplog away. See below,

> A few queries/notes:
>
>>           After building these ports you will need some more RPMS to
>> build Linux Poplog under compat_linux, they are
>>
>> tcsh-6.12-2.i386.rpm,
>
> I am hoping to remove the reliance on tcsh/csh, but it is buried not
> only in various static scrips in the poplog tree but also in some
> code that dynamically generates scripts, e.g. the code in
>     $usepop/pop/src/syscomp
>
> which creates this file with linker commands
>     $usepop/pop/pop/poplink_cmnd
>
> (every time you run pglink, or $popsrc/newpop )
>
  That is up to you, I am a bit of a tcsh fan now but realise that
bash is deeply ingrained inside Linux. Tcsh is the default user shell on
FreeBSD now.

>
>> gzip-1.3.3-5.i386.rpm, tar-1.13.25-8.i386.rpm,
>> texutils-2.0.21-5.i386.rpm
>
> I was surprised to see texutils included. That should not be necessary.

  I think that /bin/cat is in textutils.

>
> In the bham extensions to poplog, there are some Ved utilities and teach
> files concerned with using latex, but as far as I know you can build and
> install a complete poplog system without having texutils. (I've never
> tried, though, as I have TeTex on all the systems I use.)
>
>> and openmotif-2.2.2-12.i386.rpm
>
> This is also not essential though it adds to the functionality of
> XVed (scroll-bars and menu buttons, which should now be re-implemented
> another way...).
>

  I like the Motif search facility especially, I have yet to get to grips
with grep in a meaningful way.

> If anyone does not wish to install openmotif just change the
> instruction:
>
>> #bash2.05 ./INSTALL_EVERYTHING_WITH_MOTIF
>
> to
>
>> #bash2.05 ./INSTALL_EVERYTHING_WITHOUT_MOTIF
>
>
>> You could
>> also get whichever RPM contains /bin/more but I got through without it.
>
> 'less' is as good as 'more' and offers more. So you can make 'more' an
> alias for 'less' if 'less' is available!!!
>
>> #bash2.05 ./INSTALL_EVERYTHING_WITH_MOTIF
>
> Nowadays you have the option to specify a non-default installation
> directory, e.g. a personal directory:
>
>> #bash2.05 ./INSTALL_EVERYTHING_WITH_MOTIF ~/popstuff/
 
>>      During the build you will get dropped into the Setpop prompt a few
>> times when temp files can't be deleted. I just kept typing bye however
>> many times it took for the build to resume. The error messages look like
>> this      Can't delete file (Invalid Directory)
>>                             '/tmp/PXT1049.0
>
> Strange. It may be simpler as root to make /tmp a symbolic link to
> a directory that is usable for temporary files.
>
   Having another look this morning I see that there is no /tmp
directory inside the /compat/linux chroot, this could probably be fixed
by making one in there before starting.

>>
>>      There is no /usr/local/bin under /compat/linux so
>> #bash2.05 cd /usr
>> #bash2.05 mkdir -p /usr/local/bin
>> #bash2.05 ln -s /usr/local/poplog/local/setup/bin/poplog
>>       /usr/local/bin/poplog
>
> That link does not have to be in /usr/local/bin.
>
> It could be in any directory containing executables that is on the
> user's $PATH (or whatever freebsd uses as the equivalent to $PATH).
>
> E.g. if the user has a bin directory in ~/bin, the link could be
>
>> #bash2.05 ln -s /usr/local/poplog/local/setup/bin/poplog ~/bin
>
> or change /usr/local/bpoplog/ in there to whichever directory
> was given as the argument to the INSTALL... script.
>
> [A better set of installation scripts would handle all this...]
>
> I need to learn to use configure?

   Using configure would make things worse for installing on FreeBSD I
imagine however much it helped on Linux.

>
>>        But shortly it starts up with Motif working. I have Motif for
>> FreeBSD installed here as well so maybe it gets a bit confused.
>
> In that case, instead of installing a new motif, maybe you can create
> a symbolic link from
>
>     /usr/X11R6/lib/libXm.so
>
> to whereever the motif libXm.so file is???
>
> You can easily check if that would work without going through the whole
> installation. Temporarily rename your openmotif libXm.so and insert
> the link, then try to run poplog with Xved.
>
> If it works, you don't need the openomotif rpm.

     I am not sure what is happening here though Poplog would not be the
only Linux binary to have trouble using Motif under FreeBSD, mostly they
stick with the RedHat 7.1 base for these but that is now too old a libc6
for Poplog. As you say we can easily run without Motif.

                                  All the best,
                                     John Duncan