Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!yarrina.connect.com.au!munnari.OZ.AU!news.hawaii.edu!ames!agate!overload.lbl.gov!lll-winken.llnl.gov!uwm.edu!vixen.cso.uiuc.edu!newsfeed.internetmci.com!bloom-beacon.mit.edu!senator-bedfellow.mit.edu!news.mit.edu!shivers From: shivers@ai.mit.edu (Olin Shivers) Newsgroups: comp.unix.bsd.freebsd.misc Subject: TeX programs and compilation Followup-To: comp.unix.bsd.freebsd.misc Date: 04 Dec 1995 05:32:26 GMT Organization: Artificial Intelligence Lab, MIT Lines: 19 Distribution: world Message-ID: <SHIVERS.95Dec4003226@lambda.ai.mit.edu> Reply-To: shivers@ai.mit.edu NNTP-Posting-Host: lambda.ai.mit.edu I posted about problems compiling the latest TeX sources, with the "kpathsea" path-searching code. There are two problems compiling dvips(k) on a FreeBSD/XFree86 box. - FreeBSD and XFree86 conflict on their declaration of wchar_t. - FreeBSD and XFree86 conflict on their declaration of sys_errlist[]. Actually the XFree86 include files make an effort to turn off their declarations if the system includes are being included, but the kpathsea author is playing a few games... I think. I didn't have the patience to trace through eight layers of #includes, #ifdef's, and #def's. Ech. You can fix the first problem by defining FOIL_X_WCHAR_T. I cheated on the second one; I just nuked the X include file's declaration for five minutes. The kpathsea documentation discusses the first problem and provides its solution. -Olin