I'v commited this half an hour ago:
mandree 2011-06-20 22:02:53 UTCFreeBSD 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 _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
