Re: [ANNOUNCE]: clang compiling ports, take 2
Michel Talon wrote on 04.09.2011 11:29: Ruslan wrote: Hi, i maintain port (sysutils/rdup) that is failing with clang: I have looked at the problem, it is indeed in rdup source. If you look at rdup git history for rdup-tr.c you will see remove rdup_entry_c from the code, totally unneeded in this modification, the line rdup_entry_c = rdup_entry; which makes sense is (probably automatically) replaced by the line rdup_entry = rdup_entry; which is superfluous. gcc doesn't bark at that while clang does. Thanks, i'll look at this. As i understand, all will be fine if i just revert this line. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
Ivan Klymenko wrote on 04.09.2011 11:12: В Sun, 04 Sep 2011 10:42:07 +0400 Ruslan Mahmatkhanov пишет: 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. ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
On Sun, 04 Sep 2011 12:22:35 +0200 Matthias Andree wrote: > Am 04.09.2011 10:45, schrieb Ivan Klymenko: > > В Sun, 04 Sep 2011 09:34:33 +0200 > > Matthias Andree пишет: > > > >> Am 04.09.2011 09:12, schrieb Ivan Klymenko: > >> > >>> Maybe this will help: > >>> *rdup_entry = *rdup_entry; > >> > >> This is just guessing and probably triggers the same warning unless > >> it's volatile. > >> > >> Have the original author look at it. > > > > This is not guesswork. > > It is DANGEROUS guesswork. Assigning stuff to itself is pointless, so > this is a code bug. > > The only valid exception I know is if you're writing back data to a > command register in a peripheral device, which isn't the case here. > > Fix the bug, not the symptom! I agree, but I can think of another valid exception. System with Hamming correction on the memory, gets a single bit (correctable) error. Need to rewrite the memory contents to reset all the parity bits! (sorry for the drift...) ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
Am 04.09.2011 10:48, schrieb Mark Linimon: > On Sun, Sep 04, 2011 at 05:09:05AM +0200, Gerald Pfeifer wrote: >> Can you advise which value of __FreeBSD_version to use? The official >> list at >> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/freebsd-versions.html >> does not have a reference from what I can see. > > There is no version of FreeBSD that has the gcc build turned off AFAIK. > Nor is there one where cc is clang by default; again AFAIK. > > You can, of course, create a userland that has clang but not gcc if > you manually configure it. > > Please someone correct me if I am wrong. Basically USE_GCC=4.2+ was trying to sidestep clang issues in my ports in the -exp runs, and in this situation, USE_GCC=4.2+ was not installing gcc. How do I do that? ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
Am 04.09.2011 10:45, schrieb Ivan Klymenko: > В Sun, 04 Sep 2011 09:34:33 +0200 > Matthias Andree пишет: > >> Am 04.09.2011 09:12, schrieb Ivan Klymenko: >> >>> Maybe this will help: >>> *rdup_entry = *rdup_entry; >> >> This is just guessing and probably triggers the same warning unless >> it's volatile. >> >> Have the original author look at it. > > This is not guesswork. It is DANGEROUS guesswork. Assigning stuff to itself is pointless, so this is a code bug. The only valid exception I know is if you're writing back data to a command register in a peripheral device, which isn't the case here. Fix the bug, not the symptom! ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
В Sun, 04 Sep 2011 09:34:33 +0200 Matthias Andree пишет: > Am 04.09.2011 09:12, schrieb Ivan Klymenko: > > > Maybe this will help: > > *rdup_entry = *rdup_entry; > > This is just guessing and probably triggers the same warning unless > it's volatile. > > Have the original author look at it. This is not guesswork. All is going without any errors and warnings. setenv |grep clang CC=clang CXX=clang++ cd /usr/ports/sysutils/rdup && make patch rdup_entry = rdup_entry; => *rdup_entry = *rdup_entry; make > build.log ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
On Sun, Sep 04, 2011 at 05:09:05AM +0200, Gerald Pfeifer wrote: > Can you advise which value of __FreeBSD_version to use? The official > list at > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/freebsd-versions.html > does not have a reference from what I can see. There is no version of FreeBSD that has the gcc build turned off AFAIK. Nor is there one where cc is clang by default; again AFAIK. You can, of course, create a userland that has clang but not gcc if you manually configure it. Please someone correct me if I am wrong. mcl ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
Am 04.09.2011 08:42, schrieb Ruslan Mahmatkhanov: > 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? Solution: (Have the author) fix the code to not do stupid things like this: clang -Wall -W -Werror -O2 -pipe -fno-strict-aliasing -I/usr/local/include -DHAVE_CONFIG_H -DLOCALEROOTDIR=\"/usr/local/share/locale\" -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -Os -Wpointer-arith -Wstrict-prototypes -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -c rdup-tr.c rdup-tr.c:205:14: error: explicitly assigning a variable of type 'struct rdup *' to itself [-Werror,-Wself-assign] rdup_entry = rdup_entry; ~~ ^ ~~ 1 error generated. gmake: *** [rdup-tr.o] Error 1 It's probably a logic error, or mistyped. Clang also states that the error manifests itself by: -Wself-assign is part of -Wall or -W (didn't check which one) that triggers this warning -Werror turns all warnings into errors Workarounds are: add -Wno-self-assign, omit -Werror. I don't recommend either. Also ask the author to make sure that "-Werror" is accompanied by "-pedantic" during development upstream so that all mandatory diagnostics are actually enabled, and possibly also with -std=c99 or -std=c89 unless GNU extensions are used. HTH Matthias ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
Am 04.09.2011 09:12, schrieb Ivan Klymenko: > Maybe this will help: > *rdup_entry = *rdup_entry; This is just guessing and probably triggers the same warning unless it's volatile. Have the original author look at it. ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
Am 04.09.2011 05:09, schrieb Gerald Pfeifer:
> On Mon, 25 Jul 2011, Matthias Andree wrote:
>> Namely: if a port sets USE_GCC=4.2+ (for instance, sysutils/busybox does
>> that), the Pointyhat build does not install GCC. I think the bug is in
>> ports/Mk/bsd.gcc.mk which is unaware that there are newer clang-based
>> 9-CURRENT systems without gcc.
>>
>> I hope we can have another -exp run soon that addresses this.
>
> Matthias, sorry for not getting to this earlier. If you look at
> Mk/bsd.port.mk, there is a line
>
> GCCVERSION_040200= 700042 99 4.2
>
> which indicates that GCC 4.2 has been in the base system starting
> with FreeBSD 7.0 (and that magic 42 marker) until the rest of times.
>
> Can you advise which value of __FreeBSD_version to use? The official
> list at
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/freebsd-versions.html
> does not have a reference from what I can see.
Gerald,
I'm not sure if checking one of the OS Version features will be
sufficient. I am unaware of how exactly the Clang switchover is going
to happen, and how we detect it.
Possibly we need to check if ${CC} is part of the base system, and if it
isn't, install a GCC port, at least for now.
Best,
Matthias
___
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"
Re: [ANNOUNCE]: clang compiling ports, take 2
В Sun, 04 Sep 2011 10:42:07 +0400 Ruslan Mahmatkhanov пишет: > 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; ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
Ruslan wrote: > Hi, i maintain port (sysutils/rdup) that is failing with clang: I have looked at the problem, it is indeed in rdup source. If you look at rdup git history for rdup-tr.c you will see remove rdup_entry_c from the code, totally unneeded in this modification, the line rdup_entry_c = rdup_entry; which makes sense is (probably automatically) replaced by the line rdup_entry = rdup_entry; which is superfluous. gcc doesn't bark at that while clang does. -- Michel TALON ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
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? -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
On Mon, 25 Jul 2011, Matthias Andree wrote: > Namely: if a port sets USE_GCC=4.2+ (for instance, sysutils/busybox does > that), the Pointyhat build does not install GCC. I think the bug is in > ports/Mk/bsd.gcc.mk which is unaware that there are newer clang-based > 9-CURRENT systems without gcc. > > I hope we can have another -exp run soon that addresses this. Matthias, sorry for not getting to this earlier. If you look at Mk/bsd.port.mk, there is a line GCCVERSION_040200= 700042 99 4.2 which indicates that GCC 4.2 has been in the base system starting with FreeBSD 7.0 (and that magic 42 marker) until the rest of times. Can you advise which value of __FreeBSD_version to use? The official list at http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/freebsd-versions.html does not have a reference from what I can see. Gerald ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
Am 25.07.2011 17:59, schrieb Roman Divacky: > 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). Greetings, there is one serious issue that spoilt (as discussed with kwm and rene on IRC) a major part of this -exp run. Namely: if a port sets USE_GCC=4.2+ (for instance, sysutils/busybox does that), the Pointyhat build does not install GCC. I think the bug is in ports/Mk/bsd.gcc.mk which is unaware that there are newer clang-based 9-CURRENT systems without gcc. I hope we can have another -exp run soon that addresses this. Thanks. Best regards, Matthias ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
On Mon, Jul 25, 2011 at 8:06 PM, George Liaskos wrote: > Hello! > > I added some jquery for sorting / searching at the latest clang exp run. > http://cybertron.gr/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/index.html > > I hope you 'll find it useful. The table should be sortable already, just click on the column name. -- Florent Thoumie f...@freebsd.org FreeBSD 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
Hi--
On Jul 25, 2011, at 4:31 PM, Raphael Kubo da Costa wrote:
>> http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/
>
> qt4-webkit seems to trigger a clang bug, but the description for clang
> bug only says "See (TBA) for further information". Is there anything we
> (as in kde@) should do?
From:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/qt4-webkit-4.7.3.log
Clang is failing with an internal assertion failure, seems like it's not
parsing something correctly in RenderSlider.cpp, and hitting EOF:
Assertion failed: (FieldNo < FieldCount && "Invalid Field No"), function
getFieldOffset, file
/a/portbuild/amd64/9-exp/builds/20110616185105/src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/include/clang/AST/RecordLayout.h,
line 121.
Stack dump:
0. Program arguments: /usr/bin/clang++ -cc1 -triple
x86_64-unknown-freebsd9.0 -emit-obj -disable-free -main-file-name
RenderSlider.cpp -pic-level 2 -mdisable-fp-elim -relaxed-aliasing -masm-verbose
-mconstructor-aliases -munwind-tables -target-cpu x86-64
-momit-leaf-frame-pointer -coverage-file .obj/release-shared/RenderSlider.o
-resource-dir /usr/bin/../lib/clang/3.0 -D QT_SHARED -D BUILDING_QT__=1 -D
WTF_USE_ACCELERATED_COMPOSITING -D NDEBUG -D QT_NO_CAST_TO_ASCII -D
QT_ASCII_CAST_WARNINGS -D QT3_SUPPORT -D QT_MOC_COMPAT -D
QT_USE_FAST_OPERATOR_PLUS -D QT_USE_FAST_CONCATENATION -D HAVE_PTHREAD_NP_H -D
BUILD_WEBKIT -D BUILDING_QT__ -D BUILDING_JavaScriptCore -D BUILDING_WTF -D
ENABLE_VIDEO=1 -D ENABLE_JAVASCRIPT_DEBUGGER=1 -D ENABLE_DATABASE=1 -D
ENABLE_EVENTSOURCE=1 -D ENABLE_OFFLINE_WEB_APPLICATIONS=1 -D
ENABLE_DOM_STORAGE=1 -D ENABLE_ICONDATABASE=1 -D ENABLE_CHANNEL_MESSAGING=1 -D
ENABLE_ORIENTATION_EVENTS=0 -D ENABLE_SQLITE=1 -D ENABLE_DASHBOARD_SUPPORT=0 -D
ENABLE_FILTERS=1 -D ENABLE_XPATH=1 -D ENABLE_WCSS=0 -D ENABLE_WML=0 -D
ENABLE_SHARED_WORKERS=1 -D ENABLE_WORKERS=1 -D ENABLE_XHTMLMP=0 -D
ENABLE_DATAGRID=0 -D ENABLE_RUBY=1 -D ENABLE_SANDBOX=1 -D ENABLE_PROGRESS_TAG=1
-D ENABLE_BLOB_SLICE=0 -D ENABLE_3D_RENDERING=1 -D ENABLE_SVG=1 -D
ENABLE_SVG_FONTS=1 -D ENABLE_SVG_FOREIGN_OBJECT=1 -D ENABLE_SVG_ANIMATION=1 -D
ENABLE_SVG_AS_IMAGE=1 -D ENABLE_SVG_USE=1 -D ENABLE_DATALIST=1 -D
ENABLE_TILED_BACKING_STORE=1 -D ENABLE_NETSCAPE_PLUGIN_API=1 -D
ENABLE_WEB_SOCKETS=1 -D ENABLE_XSLT=0 -D ENABLE_QT_BEARER=1 -D
ENABLE_TOUCH_EVENTS=1 -D XP_UNIX -D SQLITE_CORE -D SQLITE_OMIT_LOAD_EXTENSION
-D SQLITE_OMIT_COMPLETE -D QT_NO_DEBUG -D QT_GUI_LIB -D QT_NETWORK_LIB -D
QT_CORE_LIB -D QT_HAVE_AVX -D _LARGEFILE64_SOURCE -D _LARGEFILE_SOURCE -I
../../../../include/Qt -I ../../../../include -I /usr/local/include/freetype2
-I /usr/local/share/qt4/mkspecs/freebsd-clang -I . -I
../../../../include/QtCore -I ../../../../include/QtNetwork -I
../../../../include/QtGui -I ../../../../include -I bridge/qt -I page/qt -I
platform/graphics/qt -I platform/network/qt -I platform/qt -I ../WebKit/qt/Api
-I ../WebKit/qt/WebCoreSupport -I . -I accessibility -I bindings/js -I bridge
-I bridge/c -I bridge/jsc -I css -I dom -I dom/default -I editing -I history -I
html -I html/canvas -I inspector -I loader -I loader/appcache -I loader/archive
-I loader/icon -I notifications -I page -I page/animation -I platform -I
platform/animation -I platform/graphics -I platform/graphics/filters -I
platform/graphics/transforms -I platform/image-decoders -I platform/mock -I
platform/network -I platform/sql -I platform/text -I plugins -I rendering -I
rendering/style -I storage -I svg -I svg/animation -I svg/graphics -I
svg/graphics/filters -I websockets -I wml -I workers -I xml -I generated -I
../JavaScriptCore -I ../../webkit -I ../JavaScriptCore/assembler -I
../JavaScriptCore/bytecode -I ../JavaScriptCore/bytecompiler -I
../JavaScriptCore/debugger -I ../JavaScriptCore/interpreter -I
../JavaScriptCore/jit -I ../JavaScriptCore/parser -I ../JavaScriptCore/pcre -I
../JavaScriptCore/profiler -I ../JavaScriptCore/runtime -I
../JavaScriptCore/wtf -I ../JavaScriptCore/wtf/symbian -I
../JavaScriptCore/wtf/unicode -I ../JavaScriptCore/yarr -I
../JavaScriptCore/API -I ../JavaScriptCore/ForwardingHeaders -I
../JavaScriptCore/generated -I ../include/QtWebKit -I
../../../../include/QtWebKit -I .rcc/release-shared -I ../../sqlite -I
../../../../include/phonon -I /usr/local/include -I .moc/release-shared -I
/usr/local/include -O2 -Wall -W -fdeprecated-macro -ferror-limit 19
-fmessage-length 0 -fvisibility hidden -fvisibility-inlines-hidden
-fcxx-exceptions -fexceptions -fdiagnostics-show-option -o
.obj/release-shared/RenderSlider.o -x c++ rendering/RenderSlider.cpp
1. parser at end of file
2. rendering/RenderSlider.cpp:43:11: LLVM IR generation of declaration
'WebCore'
3. rendering/RenderSlider.cpp:81:26: Generating code for declaration
'WebCore::SliderThumbElement::defaultEventHandler'
4. rendering/RenderSlider.cpp:82:1: LLVM IR generation of compound
statement ('{}')
In
Re: [ANNOUNCE]: clang compiling ports, take 2
Roman Divacky writes: > 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/ qt4-webkit seems to trigger a clang bug, but the description for clang bug only says "See (TBA) for further information". Is there anything we (as in kde@) should do? ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
On Mon, Jul 25, 2011 at 6:59 PM, Roman Divacky wrote: > 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 > > Hello! I added some jquery for sorting / searching at the latest clang exp run. http://cybertron.gr/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/index.html I hope you 'll find it useful. Regards, George ___ 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"
Re: [ANNOUNCE]: clang compiling ports, take 2
On Mon, Jul 25, 2011 at 05:59:20PM +0200, Roman Divacky wrote: > 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/ > It would be good to also do an exp run on i386. I ran into one port that compiled fine with clang on amd64, but failed under i386. (inline asm error) - Diane -- - d...@freebsd.org d...@db.net http://www.db.net/~db Why leave money to our children if we don't leave them the Earth? ___ 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"
