Date: Mon, 05 Sep 2011 15:42:55 +0400 From: Ruslan Mahmatkhanov <cvs-src@yandex.ru> To: Ivan Klymenko <fidaj@ukr.net> Cc: ports@freebsd.org, Roman Divacky <rdivacky@freebsd.org> Subject: Re: [ANNOUNCE]: clang compiling ports, take 2 Message-ID: <4E64B5BF.9090509@yandex.ru> In-Reply-To: <20110904101252.526de5ef@nonamehost.> References: <20110725155920.GA83490@freebsd.org> <4E631DBF.9000106@yandex.ru> <20110904101252.526de5ef@nonamehost.>
next in thread | previous in thread | raw e-mail | index | archive | help
Ivan Klymenko wrote on 04.09.2011 11:12: > В Sun, 04 Sep 2011 10:42:07 +0400 > Ruslan Mahmatkhanov<cvs-src@yandex.ru> пишет: > >> Roman Divacky wrote on 25.07.2011 19:59: >>> Hi! >>> >>> >>> Flz@ just run another exp-build with CC=clang and CXX=clang++. The >>> results can be seen here: >>> >>> >>> http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/ >>> >>> >>> Since the last run we've managed to fix the biggest offenders but >>> that uncovered others that need fixing. The "Reason" column was >>> extended and now shows "assumes_gcc" which is the lowest hanging >>> fruit :) >>> >>> A lot of these failures are trivial to fix (ie. assumes_gcc reason) >>> and prevent a lot of other ports from building. >>> >>> It would be great if you could skim over the list to see if some of >>> the ports you maintain are broken and possibly try to fix them. A >>> small introduction into the Clang+Ports can be read at: >>> http://wiki.freebsd.org/PortsAndClang. >>> >>> Please focus on the biggest offenders (ie. ports that prevent the >>> most other ports from building). >>> >>> Thank you for helping us again! >>> >>> Roman Divacky >>> >> >> Hi, i maintain port (sysutils/rdup) that is failing with clang: >> http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/rdup-1.1.11_1.log >> >> But it's hard to realize to me how to fix this. I've tried irc >> (#freebsd-clang and #freebsd-ports on irc.oftc.net) - and nobody >> hangs there. >> >> Can please anybody help? >> > > Maybe this will help: > *rdup_entry = *rdup_entry; Thank you all for suggestions, i already wrote to an rdup author and waiting for response. -- Regards, Ruslan Tinderboxing kills... the drives.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E64B5BF.9090509>