Date: Tue, 21 Jun 2011 00:31:23 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: ports-committers@FreeBSD.org, ports@FreeBSD.org Subject: Re: gcc-clang issue (was: cvs commit: ports/sysutils/e2fsprogs Makefile) Message-ID: <4DFFCA3B.4030307@FreeBSD.org> In-Reply-To: <201106202202.p5KM2ro0040297@repoman.freebsd.org> References: <201106202202.p5KM2ro0040297@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I'v commited this half an hour ago:
> mandree 2011-06-20 22:02:53 UTC
>
> FreeBSD ports repository
>
> Modified files:
> sysutils/e2fsprogs Makefile
> Log:
> [1] USE_GCC=4.2+, to avoid clang. Port needs -lgcc and -lgcc_s explicitly.
> [...]
[1] is actually (a) a quick excuse and (b) based on the assumption that
USE_GCC will override a clang default ports compiler.
I HAVE tried clang, and got a particular kind of linker errors, namely
that unrelated .o files redefine the same unrelated symbols - and a
crc32.o file redefining libext2fs symbols is curious, to put it mildly.
I currently suspect that there are "inline" handling differences between
clang and gcc, combined with definitions ("implementations") in .h
files, and possibly either different linker behaviour with clang, or
actually different symbols.
Has anyone seen similar issues (duplicate symbol errors) after switching
to clang?
Haven't had time to check things in detail, and thought I'd commit
USE_GCC right away to unwedge the build for future -exp runs.
--
Matthias Andree
ports committer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DFFCA3B.4030307>