On Sun, November 2, 2014 7:20 pm, Freddie Cash wrote:
> It's installing into the staing directory in order to create the binary
> package that actually gets installed. More the full install path.
>
> This is the STAGING work that went on this year.
> On Nov 2, 2014 7:02 PM, "Waitman Gobble" wrote
It's installing into the staing directory in order to create the binary
package that actually gets installed. More the full install path.
This is the STAGING work that went on this year.
On Nov 2, 2014 7:02 PM, "Waitman Gobble" wrote:
>
> On Sun, November 2, 2014 5:23 pm, Chris H wrote:
> > On S
On Sun, November 2, 2014 5:23 pm, Chris H wrote:
> On Sun, 2 Nov 2014 08:35:33 -0800 "Waitman Gobble"
>
> wrote
>
>> Issue, help appreciated. Missed day two of MeetBSD sorry alot going on
>> today. Day one was great.
>>
>> I'm updating a port and noticed that 'make' is actually calling install
>>
On Sun, 2 Nov 2014 08:35:33 -0800 "Waitman Gobble"
wrote
> Issue, help appreciated. Missed day two of MeetBSD sorry alot going on
> today. Day one was great.
>
> I'm updating a port and noticed that 'make' is actually calling install in
> my program Makefile. seems strange. It's not registering
I wonder if that has anything with the
"child process terminated abnrmally" I saw when starting a
"make build" in most any, or a number of, port(s) recently... on another v9
machine.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.or
