On 22 Oct 2016, at 06:47, Aryeh Friedman wrote:
>
>> 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
On, Fri Oct 21, 2016, Dimitry Andric wrote:
> 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-
> 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
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_
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
