On Sat, Jun 17, 2017 at 04:10:53PM -0700, Bryan Drewery wrote:
> On 6/14/2017 12:14 PM, Bob Willcox wrote:
> > I was attempting to run 'synth status' on my 12-current (drm-next) system
> > and I got this error:
> >
> > root@tavion:0 /> synth status
> > Querying system about current package install
On 6/14/2017 1:50 PM, Bob Willcox wrote:
> On Wed, Jun 14, 2017 at 02:14:45PM -0500, Bob Willcox wrote:
>> I was attempting to run 'synth status' on my 12-current (drm-next) system
>> and I got this error:
>>
>> root@tavion:0 /> synth status
>> Querying system about current package installations.
>
On 6/14/2017 12:14 PM, Bob Willcox wrote:
> I was attempting to run 'synth status' on my 12-current (drm-next) system
> and I got this error:
>
> root@tavion:0 /> synth status
> Querying system about current package installations.
> Stand by, comparing installed packages against the ports tree.
>
Am Sat, 17 Jun 2017 22:20:42 +0200
"O. Hartmann" schrieb:
> Running CURRENT (FreeBSD 12.0-CURRENT #0 r320050: Sat Jun 17 11:03:50 CEST
> 2017 amd64)
> on PCengines APU 2C4: CPU: AMD GX-412TC SOC with recent Sea BIOS.
> The APU is configured as a small router. The tun0 device is spawned from igb0
Running CURRENT (FreeBSD 12.0-CURRENT #0 r320050: Sat Jun 17 11:03:50 CEST 2017
amd64) on
PCengines APU 2C4: CPU: AMD GX-412TC SOC with recent Sea BIOS.
The APU is configured as a small router. The tun0 device is spawned from igb0
and bound
to ppp (providing the conenction to my ISP).
igb1 is th
On 2017-Jun-17, at 3:24 AM, Konstantin Belousov wrote:
> On Fri, Jun 16, 2017 at 08:54:10PM -0700, Mark Millard wrote:
>> On 2017-Jun-16, at 7:48 PM, Konstantin Belousov
>> wrote:
>>
>>> On Fri, Jun 16, 2017 at 05:01:43PM -0700, Mark Millard wrote:
. . .
>>>
>>> UFS uses 32bit inodes, c
On Fri, Jun 16, 2017 at 08:54:10PM -0700, Mark Millard wrote:
> On 2017-Jun-16, at 7:48 PM, Konstantin Belousov
> wrote:
>
> > On Fri, Jun 16, 2017 at 05:01:43PM -0700, Mark Millard wrote:
> >> . . .
> >
> > UFS uses 32bit inodes, changing to 64bit is both pointless currently, and
> > causes on
Hi
I just started to run into this problem with autotools. I am getting this
error running autoreconf -fi
here's the end of the output before unsuccessful exit:
---
configure.ac:54: error: possibly undefined macro