[gs-devel] xefitra various gs860 Makefile and build questions

[lazer1]

On 09-Oct-09, Ralph Giles wrote:
>On Fri, Oct 9, 2009 at 11:38 AM, lazer1 <lazer1 at blueyonder.co.uk> wrote:

>> 1. is it possible to remove the usage of file links from the entire build,
>> eg the archive for a start uses file links, and "make install" uses some?
>>
>> As that requires the usage of a filesystem with *nix compliant links,

>The unix install script does assume it's running on a unix system,
>yes. Links are used to maintain the same file under multiple names;
>it's not just about saving space.

the links at the moment are:

for the main gs860 archive I need to run the following script:

#!/bin/sh
cd ghostscript-8.60
cp src/configure.ac configure.ac
cp /usr/share/libtool/config.guess ijs/config.guess
cp /usr/share/libtool/config.sub   ijs/config.sub
cp /usr/share/libtool/ltmain.sh    ijs/ltmain.sh
cp /usr/share/automake/missing     ijs/missing
cp /usr/share/automake/install-sh  ijs/install-sh
cp src/Makefile.in                 Makefile.in
cd ..

to achieve the effect of the links, looking more carefully I see that the

/usr/share ones are in fact links from outside the archive,

(its very confusing how cp does the args in a different order from ln)

could those be moved from the archive to the configure or makefile?

or is that a problem for the ijs project?


for "make install" the link error messages are:


ln: cannot create symbolic link `ps2pdf12.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf13.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf12.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf13.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `eps2eps.1' to `ps2ps.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf12.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf13.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `eps2eps.1' to `ps2ps.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf12.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf13.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf12.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf13.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `eps2eps.1' to `ps2ps.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf12.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf13.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `eps2eps.1' to `ps2ps.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf12.1' to `ps2pdf.1': Operation not
supported by device
ln: cannot create symbolic link `ps2pdf13.1' to `ps2pdf.1': Operation not
supported by device


(some devices support links, but I access the same volume from 3 completely
different OS's and the only devices available to all 3 systems dont support
links!)

for this latter set of documentation files it was too much effort to do a cp
script
and I didnt bother!

(besides I tend to read the script directly to determine how to use it)

I think the above 2 lists are the entirety of the links, the first set is the

entirety for the main archive, and the second set are the ones which are
clearly
visible in "make install"

its possible there may be some further ones that have evaded notice.


>If you use the msvc32.mak top level makefile it uses settings
>compatible with Windows filesystems.

they seem to be using ; as a separator


, seems to function here. with : the gs binary thinks its a list of volumes!