X11 paths for Solaris [was: OpenType with CFF outlines]

[Tom Kacvinsky]

Solaris is nasty in the sense that it doesn't put X binaries
into a path that the freetype2 configurator recoginizes.

What I did for myself (because I don't have root on machines
here at the AMS :( ) is the following:

> cd ~
> mkdir X11
> cd X11
> ln -s /usr/openwin/bin
> cd bin
> set path = (`pwd` $path)
> cd <your path to freetype2 'root' directory>
> make; make

By having ~/X11/bin in the path, and ~/X11/bin "contain" the
system X binaries, my ftview problems went away.

I had been meaning to send mail to the freetype developers about
Solaris' nasty X11 binary path crap (why can't they use a standard
path for such things?), and now is as good a time as any...

Werner, David: will this be addressed in the release configuration
stuff?  Will you be using autoconf/libtool?

Thanks,

Tom

On Sun, 25 Jun 2000, Sivan Toledo wrote:

> 
> Yes, it's probably a Linux problem. I was able to compile the same
> snapshot on Solaris and ftlint runs fine (the X demos break because
> of some other problem that I haven't figured out).
> 
> Sivan
> 
> On Sun, 25 Jun 2000, Tom Kacvinsky wrote:
> 
> > I have the OT FDK; I'll try those fonts when I get to work tomorrow.
> > But I suspect they will view fine.All other roman OTFs have viewed
> > fine for me.I am running the snapshot on a Solaris 7 box, so the
> > problem you are experiencing might very well be a Linux libc problem.
> > 
> > As for OpenType CID fonts, there is still some more work to be done on
> > parsing CFF CID fonts.I am not sure if there is an archive of this
> > list, so I'll send you the message I sent the list about this.
> > 
> > Tom
> > 
> > On Sun, 25 Jun 2000, Sivan Toledo wrote:
> > 
> > >
> > > Actually, I get segmentation faults on TektonPro and on AGaramondPro,
> > > from the OpenType FDK, but not on the other fonts in the OT FDK,
> > > Heisi Mincho, originally a CID font. Ftview displays this one,
> > > but the glyphs print on top of one another, apparently because of
> > > wrong advance widths. (The original CID font works fine, the problem
> > > is only with the OT font).
> > >
> > > Sivan
> > >
> > > On Sun, 25 Jun 2000, Sivan Toledo wrote:
> > >
> > > >
> > > > Tom,
> > > >
> > > > thanks. I got the CVS snapshot but it crashes on otf files with
> > > > a segmentation fault (that's on a Red Hat 6.1). Here is the
> > > > stack (this one is for ftlint, same behavior for the other ones)
> > > >
> > > > #00x40094cf5 in __mempcpy (dstpp=0x0, srcpp=0x4001329f, len=3425)
> > > > at ../sysdeps/generic/mempcpy.c:57
> > > > #10x4008b0cf in _IO_file_xsgetn (fp=0x8082b40, data=0x0, n=4294966855)
> > > > at fileops.c:854
> > > > #20x4008c046 in _IO_sgetn (fp=0x8082b40, data=0x0, n=4294966855)
> > > > at genops.c:431
> > > > #30x400879e4 in _IO_fread (buf=0x0, size=1, count=4294966855,
> > > > fp=0x8082b40)
> > > > at iofread.c:42
> > > > #40x806e417 in ft_io_stream (stream=0x8082b10, offset=671, buffer=0x0,
> > > > count=4294966855) at src/base/ftsystem.c:210
> > > > #50x804b7a5 in FT_Access_Frame (stream=0x8082b10, count=4294966855)
> > > > at src/base/ftstream.c:206
> > > > #60x804e0b0 in FT_Extract_Frame (stream=0x8082b10, count=4294966855,
> > > > pbytes=0xbffff75c) at src/base/ftstream.c:158
> > > > #70x804f113 in T2_Get_Name (index=0x8083f30, element=0)
> > > > at src/cff/t2load.c:222
> > > > #80x804f85b in T2_Load_CFF_Font (stream=0x8082b10, face_index=0,
> > > > font=0x8083f20) at src/cff/t2load.c:488
> > > > #90x80520be in T2_Init_Face (stream=0x8082b10, face=0x8082bf8,
> > > > face_index=0,
> > > > num_params=0, params=0x0) at src/cff/t2objs.c:127
> > > > #10 0x804a30d in FT_Open_Face (library=0x807f300, args=0xbffffa48,
> > > > face_index=0, aface=0x807f0f4) at src/base/ftobjs.c:1139
> > > > #11 0x804cc8d in FT_New_Face (library=0x807f300,
> > > > ---Type <return> to continue, or q <return> to quit---
> > > >pathname=0xbffffd40 "yyy.otf", face_index=0, aface=0x807f0f4)
> > > > at src/base/ftobjs.c:1214
> > > > #12 0x8048b25 in main (argc=3, argv=0xbffffbf4) at src/ftlint.c:86
> > > >
> > > > This is on TektonPro-Regular.otf, which indeed is bundled with InDesign
> > > > (InDesign 1.0 in my case, I did not upgrade). I also get the same
> > > > behavior on the 2 otf sample files in the Adobe OpenType Dev Kit.
> > > >
> > > > Sivan
> > > >
> > > > On Sat, 24 Jun 2000, Tom Kacvinsky wrote:
> > > >
> > > > > Isn't TektonPro-Regular the font that comes with InDesign?
> > > > >
> > > > > If so, the latest CVS snapshot should handle it just fine...
> > > > >
> > > > > Tom
> > > > >
> > > > > On Thu, 22 Jun 2000, Sivan Toledo wrote:
> > > > >
> > > > > >
> > > > > > The latest beta seems to have support for CFF/Type2 outlines
> > > > > > but thedemo programs won't rasterize an opentype font with
> > > > > > CFF outlines (TektonPro-Regular.otf, for example). It just
> > > > > > complains that it's not a font file.
> > > > > >
> > > > > > Sivan
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > 
>