Dan Mahoney, System Admin wrote:
> On Wed, 29 Jul 2009, Doug Barton wrote:
>
>> Dan Mahoney, System Admin wrote:
>>> The fact that the error occurs AT ALL is the bug and what is
>>> counterintuitive, and many people would not think to try typing "make"
>>> again, and instead would just assume the
On Wed, 29 Jul 2009, Doug Barton wrote:
Dan Mahoney, System Admin wrote:
The fact that the error occurs AT ALL is the bug and what is
counterintuitive, and many people would not think to try typing "make"
again, and instead would just assume the thing's broken.
Ok, I actually misunderstood th
Dan Mahoney, System Admin wrote:
> The fact that the error occurs AT ALL is the bug and what is
> counterintuitive, and many people would not think to try typing "make"
> again, and instead would just assume the thing's broken.
Ok, I actually misunderstood the problem that you were reporting. I
th
On Wed, 29 Jul 2009, Doug Barton wrote:
Mel Flynn wrote:
On Wednesday 29 July 2009 10:57:05 Doug Barton wrote:
Dan Mahoney, System Admin wrote:
I believe Mel is right here. 'make clean ; make config ; make' worked
for me.
As does a second make after getting this error, but it's nonintuitive,
On Wed, 29 Jul 2009, Doug Barton wrote:
Dan Mahoney, System Admin wrote:
I believe Mel is right here. 'make clean ; make config ; make' worked
for me.
As does a second make after getting this error, but it's nonintuitive,
and probably a ports bug.
I'm not sure why 'make clean' is nonintuit
Mel Flynn wrote:
> On Wednesday 29 July 2009 10:57:05 Doug Barton wrote:
>> Dan Mahoney, System Admin wrote:
I believe Mel is right here. 'make clean ; make config ; make' worked
for me.
>>> As does a second make after getting this error, but it's nonintuitive,
>>> and probably a ports bu
On Wednesday 29 July 2009 10:57:05 Doug Barton wrote:
> Dan Mahoney, System Admin wrote:
> >> I believe Mel is right here. 'make clean ; make config ; make' worked
> >> for me.
> >
> > As does a second make after getting this error, but it's nonintuitive,
> > and probably a ports bug.
>
> I'm not s
Dan Mahoney, System Admin wrote:
>> I believe Mel is right here. 'make clean ; make config ; make' worked
>> for me.
>
> As does a second make after getting this error, but it's nonintuitive,
> and probably a ports bug.
I'm not sure why 'make clean' is nonintuitive in the context of
changing OPT
On Wed, 29 Jul 2009, Doug Barton wrote:
Mel Flynn wrote:
On Tuesday 28 July 2009 20:24:27 Dan Mahoney, System Admin wrote:
make: don't know how to make
/usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop
*** Error code 2
Someone else had the same problem, and they also chose ove
Mel Flynn wrote:
> On Tuesday 28 July 2009 20:24:27 Dan Mahoney, System Admin wrote:
>
>> make: don't know how to make
>> /usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop
>> *** Error code 2
>
>> Someone else had the same problem, and they also chose overwrite-base:
>>
>> http://uni
On Tuesday 28 July 2009 20:24:27 Dan Mahoney, System Admin wrote:
> make: don't know how to make
> /usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop
> *** Error code 2
> Someone else had the same problem, and they also chose overwrite-base:
>
> http://unix.derkeiler.com/Mailing-Lists
Hey all,
I'm having a problem on multiple systems:
With a clean port, in dns/bind96:
I get the options screen, I select only "overwrite base" in addition to
the defaults:, and after, I get this:
make: don't know how to make
/usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop
***
12 matches
Mail list logo
