Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Oct 2016 23:55:16 +0200
From:      Dimitry Andric <dim@FreeBSD.org>
To:        Marcus von Appen <mva@FreeBSD.org>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>, Jonathan Anderson <jonathan@freebsd.org>
Subject:   Re: Recent -CURRENT unable to build numerous ports
Message-ID:  <B3B4D779-C25E-4A95-A6C0-4D01A7033F4B@FreeBSD.org>
In-Reply-To: <20161021184451.GA48781@athena.sysfault.org>
References:  <20161021184451.GA48781@athena.sysfault.org>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
On 21 Oct 2016, at 20:47, Marcus von Appen <mva@freebsd.org> 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_PLUG
>  -fstack-protector -c -o .c.bco
> cc: error: no input files
> *** [.c.bco] Error code 1
> [...]
> 
> Since not all ports are affected, I assume some auto[conf|tool|make]
> issue to be triggered. Hints for getting this one solved are highly
> appreciated.

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 r307754.

-Dimitry


[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.30

iEYEARECAAYFAlgKjssACgkQsF6jCi4glqOnfQCgvPNwaSImtHJg9D5EXgQ8fKGc
s9sAoOaPSBN/9X/f5XanZRcUMXp1Bofv
=V0ED
-----END PGP SIGNATURE-----
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B3B4D779-C25E-4A95-A6C0-4D01A7033F4B>