Date: Mon, 21 Apr 2008 00:17:39 +0200 From: Alexey Shuvaev <shuvaev@physik.uni-wuerzburg.de> To: Da Rock <rock_on_the_web@comcen.com.au> Cc: freebsd-ports@freebsd.org Subject: Re: FBSD 7, Gnome2-lite port broken Message-ID: <20080420221739.GA1016@localhost.my.domain> In-Reply-To: <1208632603.7272.55.camel@laptop2.herveybayaustralia.com.au> References: <1208632603.7272.55.camel@laptop2.herveybayaustralia.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 20, 2008 at 05:16:43AM +1000, Da Rock wrote: > I've tried checking as far as my knowledge will allow the reason for > this error, but its got me beat. I was installing the above port, and > the config screen came up for one of its dependencies surrounding > ghostscript I believe where it said "don't be stingy on the options > selected as another port might need it later". So I checked them all as > I probably will need them all at some point in the future. Also to note > here there was a majority already selected to begin with. > > Unfortunately, I can't find that screen again to uncheck some options, > and I think its ghostscript-gpl which is failing. It errors on not > finding vga.h and lvga.h files. So I installed all src's from > sysinstall, but NG. > It seems that you have checked lvga256 and vgalib options in ghostscript-gpl configuration dialog. This dialog is not the standart port's OPTIONS dialog and it doesn't remember the options you have choosen between builds. So, to fix the build: cd /usr/ports/print/ghostscript-gpl make clean make install Once you are in this dialog again, just go on with the defaults. BTW, can someone more experienced comment on reasons to have non-standard configure script? Possibly related: are there any non-trivial reasons to have ghostscript (rather significant for many other ports) maintained by ports@ ? Or are there just no volunteers? Alexey.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080420221739.GA1016>