From owner-freebsd-ports@FreeBSD.ORG Mon Dec 29 09:30:58 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BF1CB5B3; Mon, 29 Dec 2014 09:30:58 +0000 (UTC) Received: from spectrum.skysmurf.nl (spectrum.skysmurf.nl [82.95.125.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 293A718CB; Mon, 29 Dec 2014 09:30:57 +0000 (UTC) Received: from spectrum.skysmurf.nl (spectrum.skysmurf.nl [82.95.125.145]) by spectrum.skysmurf.nl (8.14.9/8.14.9) with SMTP id sBT9Uls3014279; Mon, 29 Dec 2014 10:30:47 +0100 (CET) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Mon, 29 Dec 2014 10:30:47 +0100 Date: Mon, 29 Dec 2014 10:30:47 +0100 From: "A.J. 'Fonz' van Werven" To: Dimitry Andric Subject: Re: [x11-wm/fvwm2] Build failure with Clang Message-ID: <20141229093047.GA3583@spectrum.skysmurf.nl> References: <20141226203851.GA833@spectrum.skysmurf.nl> <4F54394C-79C8-4471-B82A-250FC950F9DA@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline In-Reply-To: <4F54394C-79C8-4471-B82A-250FC950F9DA@FreeBSD.org> X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.5.23 (2014-03-12) Cc: FreeBSD ports mailing list X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2014 09:30:58 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dimitry Andric wrote: >> now building x11-wm/fvwm2 with Clang fails with a linking error at >> FvwmGtk. But with lang/gcc48 it rather strangely builds just fine. >=20 > I've tried building this port with various options enabled and disabled, > but I cannot reproduce your linking errors. If I would have to guess, I > would say that either Fvwm or gtk headers are using inline functions, > and are counting on "gnu89" inline semantics. >=20 > If that is the case, you can try to add the following line to > x11-wm/fvwm2/Makefile: >=20 > USE_CSTD=3D gnu89 Thanks, that did fix it. I still find it puzzling, though. As far as I can tell, the port itself hasn't changed except for the Imlib and/or PNG dependencies. And those built perfectly fine without USE_CSTD=3Dgnu89. So I'm at a loss as to what could have been changed that makes Fvwm2 suddenly require gnu89. AvW --=20 Imbibo, ergo sum. --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUoR9HAAoJEAfP7gJTaCe8QKcQALFJXxAolLL+Gc03OSqgfuEm +lz0xgYtOAF43hGmfUGIDC6dBkMqQ+QxTst6/rUqFqAAlDxL6tEBnOeW8rAQvmE6 be9NDxX5RN6ftGOfpGESgb2+RZWT9qvGXqHMvTNZN4SyDlNnQpu3m7pmxiif5B85 mqKVNgMwelFCDApWbryErvRtI01prisXWVYJnXE4CTwPfZ7mE+Xh8Ql1VrNVXPgO hBgIxLYaXtTTZwbF0pY6UvjN562BRde3R4fUYkr5oUT6VCOMDhzxjzNOHihPl6Ep ohHpjrsoOOqtjin5BrlUzX6ahsHngJNXKlMkx0cIyTPYnRSLn3DpO3oDeTxhwj50 DtedQSYPp+jyQfCVNFiu6uk6okTPcGPQwnvy6HId+5qPYRnJ5U2XOhP5N6Ext13y SQT/G/oyJvfexOwboKuhcjdVn4Bu03LoyA9tDFxnhq7OM8L6pupKwqYR0wuqLwwd SeXK4RL2xsOFpNgh1y8UbfmoLUcW4hv9V7gB4a1fAfiib+kl6RlyDeB87iHBwWv7 Wnsf12NmrwbGeNqJjBJwz71Lj7FBZJp3WsLcysW0gWiXKKl5v7o9jd0e276w1/OS /sef0fLCE9t3VSbvlwsnehhxFRy8oIk9ZbzESkSPpmFkalSgSh+NhuS0kwP+dzta wMgkmOfezusqtRwtHrNz =DSml -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV--