-Original Message-
From: Lowell Gilbert
I just saw on the ports list that it has just been fixed.
Looks like a typo in ports/Mk/bsd.port.mk.
Sorry for doubting you...
No worries, was pretty stumped myself for a while there. Time to subscribe
to ports@ too then I reckon.
-Reko
_
"Reko Turja" writes:
> Ghost in the machine? :D
I just saw on the ports list that it has just been fixed.
Looks like a typo in ports/Mk/bsd.port.mk.
Sorry for doubting you...
Good luck.
___
freebsd-questions@freebsd.org mailing list
http://lists.free
From: Fernando Apesteguía
Did you see a message like "Found saved configuration for $port"?
On perl, which I configured manually, but on others please see later in the
message.
Did you try to see what happens if you run "make rmconfig" on those ports?
===> No user-specified options configur
"Reko Turja" writes:
> -Original Message-
> From: Lowell Gilbert
>
>> The defaults haven't changed, so something must have happened locally.
>> Check whether you've got BATCH defined in make.conf, and whether
>> /var/db/ports contains configurations for those ports.
>
> That's the strang
On Tue, Jul 17, 2012 at 5:48 PM, Reko Turja wrote:
> -Original Message- From: Lowell Gilbert
>
>
>> The defaults haven't changed, so something must have happened locally.
>> Check whether you've got BATCH defined in make.conf, and whether
>> /var/db/ports contains configurations for those
-Original Message-
From: Lowell Gilbert
The defaults haven't changed, so something must have happened locally.
Check whether you've got BATCH defined in make.conf, and whether
/var/db/ports contains configurations for those ports.
That's the strange thing... Virgin system, just update
"Reko Turja" writes:
> I just installed new 9.0 machine from scratch, cvsupped ports, fetched
> index and started building portupgrade. Both perl and ruby built with
> default options, without running config. No changes in port building
> steps nor workaround for this POLA violation anywhere in
I just installed new 9.0 machine from scratch, cvsupped ports, fetched index
and started building portupgrade. Both perl and ruby built with default
options, without running config. No changes in port building steps nor
workaround for this POLA violation anywhere in the UPDATING etc. as far as
