Re: (ITS#8830) build hardcodes gcc

[hyc@symas.com]

vcunat@gmail.com wrote:
> On 04/01/2018 12:37 PM, Howard Chu wrote:
>> vcunat@gmail.com wrote:
>>> On 04/01/2018 12:12 PM, Howard Chu wrote:
>>>> The rules you patched are only for generating gcov-compatible binari=
es.
>>>> They aren't even invoked by "make test" so I don't see why this has =
any
>>>> impact on your build at all.
>>>>
>>>
>>> The build looks like this:
>>> ...
>>> running tests
>>> ar rs liblmdb.a mdb.o midl.o
>>> gcc -pthread -O2 -g -W -Wall -Wno-unused-parameter -Wbad-function-cas=
t
>>> -Wuninitialized=C3=82 =C3=82  mdb_stat.o liblmdb.a=C3=82  -o mdb_stat
>>> make: gcc: Command not found
>>
>> What's the actual command line you used to invoke this?
>=20
> It should be basically `make` before that part and `make test` in the
> "running tests" part.  Some build flags were passed, too.
>=20
> Hmm, weird, I can't see why make decided to do this, and it doesn't
> happen with Linux+clang locally (I have no direct access to osx now).
> Maybe I'm just tired ATM.  Possibly the full failed build log will shed
> light on this?
> https://logs.nix.ci/?key=3Dnixos/nixpkgs.38289&attempt_id=3De3767f8e-8c=
1e-4404-93b1-d23d9fe429ee
>=20
> If you can't see why, I'll try to revisit this weirdness to avoid
> potential surprises in future.

The log doesn't show the actual command invocations. Most likely your "ma=
ke=20
test" isn't setting CC=3Dgcc. It's probably also doing something else wei=
rd=20
since it's building liblmdb.a twice. Regardless, there is no bug in the L=
MDB=20
Makefile, your build invocations are broken. Closing this ITS.

--=20
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/