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

[lazer1]

the questions probably apply to 870 etc, but to avoid ambiguity 

I refer to 860. 


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,

todays hard drives are huge, using cp instead of links wont make a lot of 

difference to disk usage, and means one can use any filesystem.


or better still design the build to evade duplicates whether by cp or links.

at the moment I have to look out for link error messages and do the links
manually with cp

30 years ago it was worth using a file link to save 50K, but today you can
waste 100MB without anyone noticing.

especially if the duplicates are just temporary build time duplicates.



2. With the Makefile, GS_LIB_DEFAULT uses : as a separator, but that can cause

problems with filesystems which use : for a volume name

instead could that be replaced by , which probably isnt used in any builds

under normal usage I think 

a to z
A to Z
0 to 9
_
:
\ 
and / 

shouldnt 

be used as separators


3. There is no X11 on the system here, but in the Makefile, 
GS_LIB_DEFAULT=........:/usr/openwin/lib/X11/fonts/Type1:/usr/openwin/lib/X11/fonts/TrueType

2 X11 dependencies have appeared!



4. with the Makefile, I find RESOURCE_LIST=Resource/CMap/ Resource/ColorSpace/
Resource/Decoding/ Resource/Font/ Resource/ProcSet/ Resource/IdiomSet/
Resource/CIDFont/


But when I look in Resource/ I see just CMap ColorSpace Decoding and Encoding


ie in the above list: Font ProcSet IdiomSet and CIDFont dont seem to exist

and 

Encoding does exist but isnt in the list

any reason for these 2 wierdnesses?


5. During the build, for contrib/pcl3/eprn/pagecount.c I needed to manually
set

#define RECORD_LOCKING_NOT_IMPLEMENTED 1

before

#include <fcntl.h>

the configure doesnt appear to have dealt with this



thanks for any comments on the above