FreeBSD_HEAD_amd64_gcc4.9 - Build #711 - Failure:
Build information:
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/711/
Full change log:
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/711/changes
Full build log:
$ make kernel-toolchain
...
===> gnu/usr.bin/cc/cc_tools (depend)
make[4]: "/usr/devel/svn/stable/9/share/mk/bsd.own.mk" line 233: warning:
unsetting WITH_CTF
cc -O2 -pipe -O2 -fno-strict-aliasing -pipe -fno-omit-frame-pointer -I.
-DGCCVER=\"4.2\" -DIN_GCC -DHAVE_CONFIG_H
Hi,
With recent amd64 11.0-current system (as of earlier this week) I can
reproduciblycw
get a SIGSEGV when running a command such as
$ dtc -o zb.dtb /usr/src/sys/boot/fdt/dts/arm/zedboard.dts
Segmentation fault (core dumped)
I've investigated the issue and found that the problem is at line
> On Oct 23, 2015, at 07:10, George Abdelmalik
> wrote:
>
> Hi,
>
> With recent amd64 11.0-current system (as of earlier this week) I can
> reproduciblycw
> get a SIGSEGV when running a command such as
>
> $ dtc -o zb.dtb
FreeBSD_HEAD_i386 - Build #1489 - Failure:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1489/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1489/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1489/console
Change summaries:
[sorry for top-posting *again*]
Just for the records, doing `make make` and then using the resulting make binary
seems to have solved the problems.
On 23/10/2015 13:27, Andriy Gapon wrote:
>
> Oh, hrrm:
>
> --- libbackend.a ---
> building static backend library
> nm: 'print-rtl.o': No such
FreeBSD_HEAD_i386 - Build #1490 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1490/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1490/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1490/console
Change summaries:
Oh, hrrm:
--- libbackend.a ---
building static backend library
nm: 'print-rtl.o': No such file or directory
nm: 'rtl.o': No such file or directory
nm: 'vec.o': No such file or directory
ar: warning: can't open file: vec.o: No such file or directory
ar: warning: can't open file: rtl.o: No such
FreeBSD_HEAD_amd64_gcc4.9 - Build #712 - Fixed:
Build information:
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/712/
Full change log:
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/712/changes
Full build log:
On Fri, 2015-10-23 at 09:14 -0700, Garrett Cooper wrote:
> > On Oct 23, 2015, at 07:10, George Abdelmalik <
> > gabdelma...@uniridge.com.au> wrote:
> >
> > Hi,
> >
> > With recent amd64 11.0-current system (as of earlier this week) I
> > can reproduciblycw
> > get a SIGSEGV when running a
In message <20151023192353.ga95...@cons.org>, Martin Cracauer writes:
>If you want a secure filesystem I think that at this particular time
>it would be entirely reasonable to use both gbde and geli stacked on
>top of each other[...]
Nobody is going to break through the GELI or GBDE
If I can open the soapbox for a moment.
If you want a secure filesystem I think that at this particular time
it would be entirely reasonable to use both gbde and geli stacked on
top of each other, assuming you have CPU/battery to spare. (there
should be enough cores but the battery might be
> > It looks like a problem with WITHOUT_MANCOMPRESS.
> > I am looking into it.
> A fix is now committed. It has been broken since June.
> Regards,
> Bryan Drewery
Thanks for the fix, computer is now busy with NetBSD update from 6.99.44 (16
months old) to 7.99.21 for both amd64 and i386, but
13 matches
Mail list logo