Re: Building qt5-gui port?
On Sun, Feb 10, 2019 at 03:14:15PM -0800, Mark Millard wrote:
>
> /usr/ports/Mk/Uses/qt-dist.mk has:
>
> .if ${ARCH} == i386 && empty(MACHINE_CPU:Msse2)
> CONFIGURE_ARGS+=-no-sse2
> .endif
>
Hmmm. Oh well. I set CPUTYPE=core2 in /etc/make.conf.
During configure of qt5-gui, it does try to use sse2,
sse3, ssse3, and even the unsupported avx. The build
still dies.
--
Steve
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building qt5-gui port?
On Sun, Feb 10, 2019 at 10:32:50AM -0800, Steve Kargl wrote: > On Sun, Feb 10, 2019 at 10:24:43AM -0800, Mark Millard wrote: > > > > My reference to building for armv7 not having a problem in > > my builds is an example of a 32-bit-target context for > > qt5-gui. So i386 specific or some other aspect of how its > > build was attempted might be involved in your context. > > > > Do you use -march=native -mtune=native with clang in > freebsd-current on all those architectures? > > I can build qt5-gui with "-march=i486", "-march=i686" > "-march=i686 -mmmx", "-march=i686 -mmmx -msse". I'll > be adding each of -msse2, -msse3, -mssse3, -mcx16, > -mfxsr, and -msahf to CFLAGS to see which one is causing > the problem. > > If adding all of the -target-feature options turned on > by core2 work with i686, I'll then up i686 and repeat. > Well that was quick. Adding -msse2 to CFLAGS causes qt5-gui to die. -- Steve ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building qt5-gui port?
On Sun, Feb 10, 2019 at 10:24:43AM -0800, Mark Millard wrote: > > My reference to building for armv7 not having a problem in > my builds is an example of a 32-bit-target context for > qt5-gui. So i386 specific or some other aspect of how its > build was attempted might be involved in your context. > Do you use -march=native -mtune=native with clang in freebsd-current on all those architectures? I can build qt5-gui with "-march=i486", "-march=i686" "-march=i686 -mmmx", "-march=i686 -mmmx -msse". I'll be adding each of -msse2, -msse3, -mssse3, -mcx16, -mfxsr, and -msahf to CFLAGS to see which one is causing the problem. If adding all of the -target-feature options turned on by core2 work with i686, I'll then up i686 and repeat. In the end, this looks like a "wrong code" issue with llvm/clang/clang++. -- Steve ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building qt5-gui port?
On 2019-Feb-10, at 07:14, Steve Kargl wrote: > On Sun, Feb 10, 2019 at 11:34:28AM -0200, Lucas Nali de Magalhães wrote: >>> >>> My lumina builds indirectly build qt5-qui and have been having Dumb typo on my part: should have been a qt5-gui reference. >>> no problems (targeting amd64, aarch64, armv7, and powerpc64). >>> (My powerpc64 context is not normally gcc 4.2.1 based.) >>> >>> [...] >> >> So it looks like it's 32bit specific; maybe i386 only. >> > > Yes, likely. > > I'll note that valgrind hass been broken for a long time, > now that I think about it was built with -march=native. > My reference to building for armv7 not having a problem in my builds is an example of a 32-bit-target context for qt5-gui. So i386 specific or some other aspect of how its build was attempted might be involved in your context. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building qt5-gui port?
> On Feb 10, 2019, at 12:56 PM, Carmel NY wrote: > > On Sun, 10 Feb 2019 06:40:01 -0800, Steve Kargl stated: > >> On Sun, Feb 10, 2019 at 08:31:12AM +0100, Tobias C. Berner wrote: >>> Moin moin >>> >>> Make sure all your qt5-(qt5-gui dependency)-ports that are already >>> installed are at 5.12.0. >>> >> >> They are all up to date. >> >> % cd /usr/ports >> % svn update >> % pkg delete -f qt5-\* >> % portmaster -Byd x11-toolkits/qt5-gui >> >> will die if I have "CFLAGS+=-march=native" in /etc/make.conf. >> >> It seems to be a clang/clang++ issue on freebsd-current. One of >> the errors is >> >> .obj/qimage.o: In function `QImage::fill(unsigned int)': >> qimage.cpp:(.text+0x2442): undefined reference to >> `qt_memfill32(unsigned int*, unsigned int, int)' >> qimage.cpp:(.text+0x2477): undefined reference to >> `qt_memfill16(unsigned short*, unsigned short, int)' >> qimage.cpp:(.text+0x268f): undefined reference to >> `qt_memfill32(unsigned int*, unsigned int, int)' >> qimage.cpp:(.text+0x26cf): undefined reference to >> `qt_memfill16(unsigned short*, unsigned short, int)' >> >> % find work -name \*.cpp | xargs grep qt_memfill16 >> path_to/qdrawhelper_sse2.cpp:void qt_memfill16(quint16 *dest, quint16 >> value, int count) path_to/qdrawhelper.cpp:void qt_memfill16(quint16 >> *dest, quint16 color, int count) mobile:root[210] find work -name >> qdrawhelper.o path_to/qdrawhelper.o >> mobile:root[211] nm path_to/qdrawhelper.o | grep memfill >>U _Z12qt_memfill16Ptti >>U _Z12qt_memfill32Pjji >> 00017bb0 T _Z12qt_memfill64Pyyi >> > > Just for grins, what is the output of: >dmesg | grep -i "CPU" CPU: Intel(R) Celeron(R) M CPU430 @ 1.73GHz (1729.04-MHz 686-class CPU) cpu0: CPU: Intel(R) Celeron(R) M CPU430 @ 1.73GHz (1729.04-MHz 686-class CPU) microcode-update is in use here. Lc -- rollingbits — rollingb...@gmail.com rollingb...@terra.com.br rollingb...@yahoo.com rollingb...@globo.com rollingb...@icloud.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building qt5-gui port?
On Sun, Feb 10, 2019 at 02:56:17PM +, Carmel NY wrote: > On Sun, 10 Feb 2019 06:40:01 -0800, Steve Kargl stated: > > >On Sun, Feb 10, 2019 at 08:31:12AM +0100, Tobias C. Berner wrote: > >> Moin moin > >> > >> Make sure all your qt5-(qt5-gui dependency)-ports that are already > >> installed are at 5.12.0. > >> > > > >They are all up to date. > > > >% cd /usr/ports > >% svn update > >% pkg delete -f qt5-\* > >% portmaster -Byd x11-toolkits/qt5-gui > > > >will die if I have "CFLAGS+=-march=native" in /etc/make.conf. > > > >It seems to be a clang/clang++ issue on freebsd-current. One of > >the errors is > > > >.obj/qimage.o: In function `QImage::fill(unsigned int)': > >qimage.cpp:(.text+0x2442): undefined reference to > >`qt_memfill32(unsigned int*, unsigned int, int)' > >qimage.cpp:(.text+0x2477): undefined reference to > >`qt_memfill16(unsigned short*, unsigned short, int)' > >qimage.cpp:(.text+0x268f): undefined reference to > >`qt_memfill32(unsigned int*, unsigned int, int)' > >qimage.cpp:(.text+0x26cf): undefined reference to > >`qt_memfill16(unsigned short*, unsigned short, int)' > > > >% find work -name \*.cpp | xargs grep qt_memfill16 > >path_to/qdrawhelper_sse2.cpp:void qt_memfill16(quint16 *dest, quint16 > >value, int count) path_to/qdrawhelper.cpp:void qt_memfill16(quint16 > >*dest, quint16 color, int count) mobile:root[210] find work -name > >qdrawhelper.o path_to/qdrawhelper.o > >mobile:root[211] nm path_to/qdrawhelper.o | grep memfill > > U _Z12qt_memfill16Ptti > > U _Z12qt_memfill32Pjji > >00017bb0 T _Z12qt_memfill64Pyyi > > > > Just for grins, what is the output of: > dmesg | grep -i "CPU" > mobile:kargl[201] dmesg | grep -i CPU CPU: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz (1995.05-MHz 686-class CPU) -- Steve ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building qt5-gui port?
On Sun, Feb 10, 2019 at 08:31:12AM +0100, Tobias C. Berner wrote: > Moin moin > > Make sure all your qt5-(qt5-gui dependency)-ports that are already > installed are at 5.12.0. > The qt5 ports are up to date. % cd /usr/ports % svn update % pkg delete -f qt5-\* % cd x11-toolkits/qt5-gui % make (wait a long time) Build dies if CFLAGS+=-march=native is in /etc/make.conf. -- Steve ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building qt5-gui port?
On Sun, 10 Feb 2019 06:40:01 -0800, Steve Kargl stated: >On Sun, Feb 10, 2019 at 08:31:12AM +0100, Tobias C. Berner wrote: >> Moin moin >> >> Make sure all your qt5-(qt5-gui dependency)-ports that are already >> installed are at 5.12.0. >> > >They are all up to date. > >% cd /usr/ports >% svn update >% pkg delete -f qt5-\* >% portmaster -Byd x11-toolkits/qt5-gui > >will die if I have "CFLAGS+=-march=native" in /etc/make.conf. > >It seems to be a clang/clang++ issue on freebsd-current. One of >the errors is > >.obj/qimage.o: In function `QImage::fill(unsigned int)': >qimage.cpp:(.text+0x2442): undefined reference to >`qt_memfill32(unsigned int*, unsigned int, int)' >qimage.cpp:(.text+0x2477): undefined reference to >`qt_memfill16(unsigned short*, unsigned short, int)' >qimage.cpp:(.text+0x268f): undefined reference to >`qt_memfill32(unsigned int*, unsigned int, int)' >qimage.cpp:(.text+0x26cf): undefined reference to >`qt_memfill16(unsigned short*, unsigned short, int)' > >% find work -name \*.cpp | xargs grep qt_memfill16 >path_to/qdrawhelper_sse2.cpp:void qt_memfill16(quint16 *dest, quint16 >value, int count) path_to/qdrawhelper.cpp:void qt_memfill16(quint16 >*dest, quint16 color, int count) mobile:root[210] find work -name >qdrawhelper.o path_to/qdrawhelper.o >mobile:root[211] nm path_to/qdrawhelper.o | grep memfill > U _Z12qt_memfill16Ptti > U _Z12qt_memfill32Pjji >00017bb0 T _Z12qt_memfill64Pyyi > Just for grins, what is the output of: dmesg | grep -i "CPU" -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building qt5-gui port?
On Sun, Feb 10, 2019 at 08:31:12AM +0100, Tobias C. Berner wrote: > Moin moin > > Make sure all your qt5-(qt5-gui dependency)-ports that are already > installed are at 5.12.0. > They are all up to date. % cd /usr/ports % svn update % pkg delete -f qt5-\* % portmaster -Byd x11-toolkits/qt5-gui will die if I have "CFLAGS+=-march=native" in /etc/make.conf. It seems to be a clang/clang++ issue on freebsd-current. One of the errors is .obj/qimage.o: In function `QImage::fill(unsigned int)': qimage.cpp:(.text+0x2442): undefined reference to `qt_memfill32(unsigned int*, unsigned int, int)' qimage.cpp:(.text+0x2477): undefined reference to `qt_memfill16(unsigned short*, unsigned short, int)' qimage.cpp:(.text+0x268f): undefined reference to `qt_memfill32(unsigned int*, unsigned int, int)' qimage.cpp:(.text+0x26cf): undefined reference to `qt_memfill16(unsigned short*, unsigned short, int)' % find work -name \*.cpp | xargs grep qt_memfill16 path_to/qdrawhelper_sse2.cpp:void qt_memfill16(quint16 *dest, quint16 value, int count) path_to/qdrawhelper.cpp:void qt_memfill16(quint16 *dest, quint16 color, int count) mobile:root[210] find work -name qdrawhelper.o path_to/qdrawhelper.o mobile:root[211] nm path_to/qdrawhelper.o | grep memfill U _Z12qt_memfill16Ptti U _Z12qt_memfill32Pjji 00017bb0 T _Z12qt_memfill64Pyyi -- Steve ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building qt5-gui port?
> On Feb 10, 2019, at 6:58 AM, Mark Millard via freebsd-ports > wrote: > > Steve Kargl sgk at troutmask.apl.washington.edu wrote on > Sun Feb 10 03:32:37 UTC 2019 : > >> Anyone have any pointers on building x11-toolkits/qt5-gui on >> FreeBSD-current? My attempts end with >> >> . . . >> >> .obj/qimage.o: In function `QImage::fill(unsigned int)': >> qimage.cpp:(.text+0x2442): undefined reference to `qt_memfill32(unsigned >> int*, unsigned int, int)' >> qimage.cpp:(.text+0x2477): undefined reference to `qt_memfill16(unsigned >> short*, unsigned short, int)' >> >> . . . > > My lumina builds indirectly build qt5-qui and have been having > no problems (targeting amd64, aarch64, armv7, and powerpc64). > (My powerpc64 context is not normally gcc 4.2.1 based.) > > [...] So it looks like it's 32bit specific; maybe i386 only. Lc -- rollingbits — rollingb...@gmail.com rollingb...@terra.com.br rollingb...@yahoo.com rollingb...@globo.com rollingb...@icloud.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building qt5-gui port?
> On Feb 10, 2019, at 3:40 AM, Steve Kargl > wrote: > >> On Sat, Feb 09, 2019 at 07:32:27PM -0800, Steve Kargl wrote: >> Anyone have any pointers on building x11-toolkits/qt5-gui on >> FreeBSD-current? My attempts end with >> >> c++ -Wl,--as-needed > > (boat load of info removed). > >> qdrawhelper.cpp:(.text+0x2d0ba): undefined reference to >> `comp_func_Plus_sse2(unsigned int*, unsigned int const*, int, unsigned int)' >> c++: error: linker command failed with exit code 1 (use -v to see invocation) >> *** Error code 1 >> > > It seems that clang cannot use -march=native (at least on my > Intel(R) Core(TM)2 Duo CPU T7250). I was about to write about it too: same thing here but I'm still finishing my upgrade. Things I've tried: - remove all qt5- ports: no difference. No qt4- ports here. - remove CPUTYPE=native: no difference. - use CPUTYPE=pentium4: no difference. - use CPUTYPE=yonah: no difference. I tried a few other things, too, that didn't work in many ways of the word. Lc -- rollingbits — rollingb...@gmail.com rollingb...@terra.com.br rollingb...@yahoo.com rollingb...@globo.com rollingb...@icloud.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeCAD 0.17 - is anyone using it?
On 2/8/19 8:13 PM, Torfinn Ingolfsen wrote: Just checking: is anyone using FreeCAD 0.17 (cad/freecad) under FreeBSD at all? I installed it from ports, I'm running tingo@kg-core1$ uname -a FreeBSD kg-core1.kg4.no 11.2-STABLE FreeBSD 11.2-STABLE #0 r342545: Thu Dec 27 00:29:46 CET 2018 r...@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 but the windows in FreeCAD have graphics corruption all over them, making it very hard to use. See picture in this message at the FreeBSD forums: https://forums.freebsd.org/threads/freecad-0-17-graphics-corruption.69429/ Works fine here on 11.2/amd64 with an old Radeon card. bye av. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building qt5-gui port?
Steve Kargl sgk at troutmask.apl.washington.edu wrote on Sun Feb 10 03:32:37 UTC 2019 : > Anyone have any pointers on building x11-toolkits/qt5-gui on > FreeBSD-current? My attempts end with > > . . . > > .obj/qimage.o: In function `QImage::fill(unsigned int)': > qimage.cpp:(.text+0x2442): undefined reference to `qt_memfill32(unsigned > int*, unsigned int, int)' > qimage.cpp:(.text+0x2477): undefined reference to `qt_memfill16(unsigned > short*, unsigned short, int)' > > . . . My lumina builds indirectly build qt5-qui and have been having no problems (targeting amd64, aarch64, armv7, and powerpc64). (My powerpc64 context is not normally gcc 4.2.1 based.) Both targeting aarch64 and armv7 via amd64 based cross builds and native builds on all 4 have not had such errors. (Same /usr/src/ and /usr/ports/ by content across all but powerpc64, with powerpc64 having some extra debug material. Also: only amd64 being used to host cross builds.) Most recently this was on: # uname -apKU FreeBSD FBSDFSSD 13.0-CURRENT FreeBSD 13.0-CURRENT #9 r343884M: Thu Feb 7 19:22:33 PST 2019 markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/GENERIC-NODBG amd64 amd64 1300010 1300010 # svnlite info /usr/ports/ | grep "Re[plv]" Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 492409 Last Changed Rev: 492409 I build via ports-mgmt/poudriere-devel in all cases, even on the likes of a Pine64+ 2GB armv7 board. (You did not mention much about how you build ports generally or the specific port: what type of context are you hoping for helpful information for?) (I'll not get into apparently-unrelated oddities with qemu-user-static and host-native cross-tools used for cross builds. The self-hosted poudriere use has not had the oddities but takes longer to build.) === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ x11-servers/Xfstt | 1.9.3 | 1.10 +-+ x11-themes/greybird-theme | 3.22.9 | v3.22.10 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
