Hi!
> > rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were merged
> > into a
> > single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the code is
> > available on https://github.com/s3erios/rtwn repository. Among bugfixes /
> > code deduplication, there some new features too:
>
> This was a side-effect of r307676, which added transformation rules for
> .bco and .llo files (LLVM bytecode in binary and text representation).
>
> Because .SUFFIXES was not updated to match, bmake was actually trying to
> build a ".c.bco" file in the above case...
>
> I committed a fix in r3077
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/809/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 21 Oct 2016, at 20:47, Marcus von Appen wrote:
>
> -CURRENT as of r307731 seems to have some serious flaw with its build
> tool environment. Many ports fail to build with some error similar to
> the following (devel/apr1):
>
> cc -emit-llvm -fno-strict-aliasing -pipe -march=native -DLIBICONV_
On, Fri Oct 21, 2016, Marcus von Appen wrote:
> Hi,
>
> -CURRENT as of r307731 seems to have some serious flaw with its build
> tool environment. Many ports fail to build with some error similar to
> the following (devel/apr1):
>
> cc -emit-llvm -fno-strict-aliasing -pipe -march=native -DLIBICONV_
On, Thu Sep 01, 2016, Andriy Voskoboinyk wrote:
> Hi everyone,
>
> rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were merged
> into a
> single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the code is
> available on https://github.com/s3erios/rtwn repository. Among bugfixes /
>
Since r307157 I'm bugged with sporadic reboots/crashes of all boxes running
CURRENT. That
is different CPU types (XEON C2D, XEON Haswell, XEON IvyBridge, mobile Haswell
and
desktop IvyBridge).
Below, you'll finde some messages I gathered from the console. I hope this is
of any use,
if not: I'm
Hi,
-CURRENT as of r307731 seems to have some serious flaw with its build
tool environment. Many ports fail to build with some error similar to
the following (devel/apr1):
cc -emit-llvm -fno-strict-aliasing -pipe -march=native -DLIBICONV_PLUG
-fstack-protector -c -o .c.bco
cc: error: no input f
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/804/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
