[Quick top post:]
Reverting to -r326192 and rebuilding avoided the issue.
Prior notes:
On 2017-Nov-25, at 12:02 PM, Mark Millard wrote:
> For example,
>
> /usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/tmp/usr/include/stdio.h:449:47:
> error: function definition is not allowed here
>
===
Mark Millard
markmi at dsl-only.net
On 2017-Nov-25, at 1:10 PM, Pedro Giffuni wrote:
> On 11/25/17 15:28, Pedro Giffuni wrote:
>>
>> ...
>>
>> I have seen problems on arm with zstd though.
>>
> For the record:
> arm.armv6 buildworld failed, check _.arm.armv6.buildworld for details
>
On 25 Nov 2017, at 22:10, Pedro Giffuni wrote:
>
> On 11/25/17 15:28, Pedro Giffuni wrote:
>>
>> ...
>>
>> I have seen problems on arm with zstd though.
>>
> For the record:
> arm.armv6 buildworld failed, check _.arm.armv6.buildworld for details
>
> ===> lib/libzstd (all)
> Assertion fail
On 11/25/17 15:28, Pedro Giffuni wrote:
...
I have seen problems on arm with zstd though.
For the record:
arm.armv6 buildworld failed, check _.arm.armv6.buildworld for details
===> lib/libzstd (all)
Assertion failed: (LiveCPSR && "CPSR liveness tracking is wrong!"),
function UpdateCPS
Thank you for the report ...
On 11/25/17 15:15, Mark Millard wrote:
[Quick top post:]
Reverting to -r326192 and rebuilding avoided the issue.
Prior notes:
On 2017-Nov-25, at 12:02 PM, Mark Millard wrote:
For example,
/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/tmp/usr/include
For example,
/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/tmp/usr/include/stdio.h:449:47:
error: function definition is not allowed here
static __inline int __sputc(int _c, FILE *_p) {
for:
/*
* The __sfoo macros are here so that we can
* define function versions in the C library.
*/
Hi,
There is a source tree in svn at projects/pnfs-planb-server which adds support
for configuring a single Metadata Server (MDS) and multiple Data Servers (DS)
to create a simple pNFS service. (In a pNFS server the Read/Write operations
are separated from the rest of the metadata operations and g
> Hello,
>
> I decided to try to run some bhyve VM's on my machine and bridge
> them to a guest vlan on my main interface. I also want to support
> running bhyve VM's on the untagged part of the interface as well
> (this is the key problem as I'll describe later).
>
> I configure it as you'd exp