Date: Tue, 29 Feb 2000 10:11:03 -0500 (EST) From: Kenneth W Cochran <kwc@world.std.com> To: "Chris D. Faulhaber" <jedgar@fxp.org> Cc: freebsd-stable@freebsd.org Subject: Re: Trouble installing xpdf port in 3.4-stable Message-ID: <200002291511.KAA04016@world.std.com>
next in thread | raw e-mail | index | archive | help
Wow! That was fast... :) >Date: Tue, 29 Feb 2000 09:28:54 -0500 (EST) >From: "Chris D. Faulhaber" <jedgar@fxp.org> >Subject: Re: Trouble installing xpdf port in 3.4-stable > >On Tue, 29 Feb 2000, Kenneth W Cochran wrote: >> How can I get xpdf? >> >> Even though it shows up in the ports tree, the description says >> it is in both "graphics" & "print" but it is only listed in >> "graphics." >> >> Xpdf is not on *any* of the CDs. I could've sworn it was on >> previous CDs; how did it get left out? I'd think xpdf would be >> a "biggie..." > >Looking at ports/graphics/xpdf/Makefile, you will find: > >.if !defined(PACKAGE_BUILDING) >RESTRICTED= "Contains cryptography" >.endif > >which means that an xpdf package will not be built since it >contains cryptographic code (presumably to decrypt encrypted .pdf's). What? Amazing... I'd never have guessed *that*... I generally stay out of makefiles (at least "officially") & try to rely on the appropriate READMEs, etc. (Ie. I "start out" in "semi-dumb-user" mode... :) >> Configure stops ... >> >> So... What's up here? Btw, xpdf is not the only one that >> (mis)behaves like this; there have been a couple of others, but >> I can't remember them right now... > >It's difficult to debug without any real error messages. Feel >free to send errors/logs/etc to the MAINTAINER (found in the >port's Makefile) and/or ports@FreeBSD.org Done... Thanks... I guess I'll have to wait & see what I might hear from them... -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002291511.KAA04016>