How to determine the history of a port

want to help the user, but I have no idea how the change that broke the build was added to the Makefile. How do I find the history so I can find out who added the problematic line and figure out what they actually meant? --Paul Hoffman ___ freebsd

Installing Ruby suggestion

e you do a "make reinstall". Having that second step take a long time means that there is a longer time that there is no Ruby on the system. Could the RDoc step be done during "make" instead of "make install"? --Paul Hoffman __

Re: Installing Ruby suggestion

At 4:16 PM -0700 8/20/10, Stanislav Sedov wrote: >On Fri, 20 Aug 2010 18:55:33 -0400 >Eitan Adler mentioned: > >> On Thu, Aug 19, 2010 at 2:30 PM, Paul Hoffman wrote: >> > Greetings again. When doing a "make install", it takes *forever* in the >> >

Wanted: binary build of Emacs without X11

ystem. If I go to /usr/ports/editors/emacs and build with WITHOUT_X11, I still need to install a bunch of building tools that are basically unneeded by anything other than building Emacs. It would be nice if the prebuilt binaries had an emacs-nox11. --Paul Ho

Re: Wanted: binary build of Emacs without X11

At 11:36 AM -0500 9/7/08, Scot Hetzel wrote: On 9/7/08, Paul Hoffman <[EMAIL PROTECTED]> wrote: Greetings again. I'm not sure if this request should be done to this mailing list or as a PR, but here goes. I run FreeBSD as a server, not as a desktop. Some of my users want Emacs.

How do I tell what arguments were given to configure?

Greetings again. I am trying to trace down a bug that I think is happening in a port. I have captured the output of "make", but I don't see in it what arguments are being given to the port's "configure" script. Where do I find that? ___ freebsd-ports@f

Re: How do I tell what arguments were given to configure?

Thanks for all the replies. I was, in fact, able to determine that the configuration arguments for this port are broken, and have submitted a bug report with the fix. FWIW, the port is lang/python30. It is *not* built with UCS-4 support even when you tell it to be due to bad config arguments. _

Can't build new PHP

ROOT-opus:/usr/ports/lang/php5# make reinstall ===> Vulnerability check disabled, database not found ===> Found saved configuration for php5-5.2.1_3 => php-5.2.2-mail-header.patch doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from http://choon.net/opensource/php/. fetch:

Cannot make security/nss

x27; gmake[1]: *** [libs] Error 2 gmake[1]: Leaving directory `/usr/ports/security/nss/work/nss-3.11.4/mozilla/security/nss/cmd' gmake: *** [libs] Error 2 *** Error code 2 Any clues would be appreciated. --Paul Hoffman ___ freebsd-ports@free

devel/nspr fails 'make test' but builds OK

At the end of 'make', it suggests running 'make test'. I did so, and in the middle it reports: forktestFAILED forktest: Wait one second before accept forktest: Wait one second before connect forktest: Accepting connection

Re: Cannot make security/nss

At 8:08 AM -0500 1/10/07, Mikhail Teterin wrote: = /usr/local/lib/libplc4.so: undefined reference to `gethostbyname_r' = /usr/local/lib/libplc4.so: undefined reference to `getprotobyname_r' = /usr/local/lib/libplc4.so: undefined reference to `gethostbyname2_r' = /usr/local/lib/libplc4.so: undefin

Modifying a port and keeping the mods across updates

this that will live beyond the next cvsup? I know how to use 'patch' to apply patches, but not yet to create them. --Paul Hoffman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscri

Re: Modifying a port and keeping the mods across updates

At 11:37 PM -0600 1/19/07, Scot Hetzel wrote: On 1/19/07, Paul Hoffman <[EMAIL PROTECTED]> wrote: Greetings again. I have a two-part question that may be a ports FAQ, but I couldn't find such a beast. (1) For a particular port, I need to change the the MAKE_ENV to make it build the

Re: Modifying a port and keeping the mods across updates

folks in the NSS world as well. If the security/nss port maintainer is on this list, it would be really grand to have NSS_ENABLE_ECC as an option in the port itself. --Paul Hoffman ___ freebsd-ports@freebsd.org mailing list http://lists.free

Re: ports requiring OpenSSL not honouring OpenSSL from ports

umented* feature of make.conf. I'll turn in a pr for it. --Paul HOffman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ports requiring OpenSSL not honouring OpenSSL from ports

On May 1, 2014, at 8:26 AM, Uwe Doering wrote: > On 01.05.14 16:33, Paul Hoffman wrote: >> I'll turn in a pr for it. docs/189199 > Good idea. I would think that this should be mentioned at least in > "pkg-descr" of the "openssl" port, where it gets displ

Fwd: ports/189208: Add a mention of WITH_OPENSSL_PORT to the pkg-descr of security/openssl

wouldn't know where to look in the code, so I can't figure out which is right. But it is clear that this is worth clarifying both in the openssl pkg-descr *and* in the make.conf man page. --Paul Hoffman Begin forwarded message: > From: din...@freebsd.org > Subject: Re: ports/189208: