Recipe to build seamonkey with clang: seamonkey-2.17 / clang-9999+lto / llvm-9999 build issues 1) currently live ebuilds from trunk are versioned llvm-3.3svn keyword -9999 versions in /etc/paludis/keywords.conf and build them 2) make ar, nm tools of binutils use llvm linker plugins see bug #462554 3) patch mozcoreconf-2.eclass to allow passing -O4 as an optimization flag see bug #462488 4) enable clang/llvm environment for seamonkey in /etc/paludis/bashrc case "${CATEGORY}/${PN}" in www-client/seamonkey) ;& "USE-CLANG-AND-LLVM") CC="clang" CXX="clang++" CFLAGS="${CFLAGS/-O?/-O4}" LDFLAGS="${LDFLAGS} -Wl,-z,norelro" ;; esac CXXFLAGS="${CFLAGS}" LDFLAGS="${CFLAGS} ${LDFLAGS}" 5) enable the following use flags in /etc/paludis/use.conf www-client/seamonkey custom-cflags www-client/seamonkey custom-optimization 6) for epatch_user to find, place the source patch attached in /etc/portage/patches/www-client/seamonkey-2.17 NOTE: seamonkey has the same issue with methodjit like FF has described in bug #462608. The ebuild patch is similar to the one needed for FF 19.0.2, just the directory structure differs, i.e. ${S}/mozilla/modules/libpref/.. instead of ${S}/modules/libpref/.. Reproducible: Always
Created attachment 344664 [details, diff] /etc/portage/patches/www-client/seamonkey-2.17/seamonkey-2.17-clang3.3svn.patch
Created attachment 344666 [details, diff] seamonkey-2.17.ebuild.patch
If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system. Thank You for your support and understanding The Mozilla Team
