Date: Thu, 13 Mar 1997 01:50:02 -0800 (PST) From: Eivind Eklund <eivind@dimaga.com> To: freebsd-ports Subject: Re: ports/2936: The teTeX port runs strup on /usr/local/bin Message-ID: <199703130950.BAA17694@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/2936; it has been noted by GNATS. From: Eivind Eklund <eivind@dimaga.com> To: asami@vader.cs.berkeley.edu (Satoshi Asami) Cc: freebsd-gnats-submit@freebsd.org Subject: Re: ports/2936: The teTeX port runs strup on /usr/local/bin Date: Wed, 12 Mar 1997 23:48:11 +0100 At 03:30 PM 3/11/97 -0800, Satoshi Asami wrote: > * I get errors for missing inimf, virmf, install-info, xdvi.bin, texinfo-12, > * web2c/mf.log, and web2c/mf.base. > > * Did it package OK when you reverted? > >You are right -- I reverted the patch but I still can't build it. I >have the same problem with or without your patch. However, the list >of errors is different, I have a bunch of bin/* files missing. > >------- >===> Building package for teTeX-0.4 >tar: can't add file bin/gftodvi : No such file or directory >tar: can't add file bin/gftopk : No such file or directory >tar: can't add file bin/mft : No such file or directory >tar: can't add file bin/pktogf : No such file or directory >tar: can't add file bin/pktype : No such file or directory >tar: can't add file bin/vftovp : No such file or directory >tar: can't add file bin/vptovf : No such file or directory >tar: can't add file bin/gftype : No such file or directory >tar: can't add file bin/pltotf : No such file or directory >tar: can't add file bin/tftopl : No such file or directory >tar command failed with code 256 >------- > >I put the log in > >ftp://han.cs.berkeley.edu/pub/tetex.log.gz > >If you can take a look, it will be appreciated. My system is >RELENG_2_2 (naturally, it's the packages-2.2 building machine). Compiler dying with signal 6. There is something DEFINEATLY weird about this port; everything looks OK, it compiles on some machine but not others, and the EXACT SAME COMMANDS written in a shell will compile the things that fail consistently under gmake (at least on my box). Can you try that for your errors? Eivind Eklund perhaps@yes.no http://maybe.yes.no/perhaps/ eivind@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703130950.BAA17694>