[FreeBSD-Ports-Announce] [HEADS UP] Ports Slush is now in effect
Just to make it official, the ports slush is over. Ports committers are now able to perform regular updates, business as usual, no need for portmgr@ approvals. Keep in mind that -exp runs are always a good idea if you think there is a significant change to the ports tree. It is anticipated that a FreeBSD 9.2 release schedule could be upon us quickly so we have elected to lift the slush period a little sooner than planned. We would like committers and maintainers alike to work on keeping the ports tree in shape for the next cycle. Additionally, we also have a FreeBSD 10.0 release coming up in the unspecified future, and many ports have work-arounds applied for them to work with autotools and for Clang. We would like all porters to use this extra time to ensure their ports build on 10.X, and work with upstream support to integrate FreeBSD related patches. As always, this is not a reason to break the INDEX, please exercise due diligence before performing all commits. Thomas on behalf of portmgr@ ___ freebsd-ports-announce@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports-announce To unsubscribe, send any mail to freebsd-ports-announce-unsubscr...@freebsd.org
[FreeBSD-Ports-Announce] [CORRECTION] Ports Slush is now in over
Just to make it official, the ports slush is over. Ports committers are now able to perform regular updates, business as usual, no need for portmgr@ approvals. Keep in mind that -exp runs are always a good idea if you think there is a significant change to the ports tree. It is anticipated that a FreeBSD 9.2 release schedule could be upon us quickly so we have elected to lift the slush period a little sooner than planned. We would like committers and maintainers alike to work on keeping the ports tree in shape for the next cycle. Additionally, we also have a FreeBSD 10.0 release coming up in the unspecified future, and many ports have work-arounds applied for them to work with autotools and for Clang. We would like all porters to use this extra time to ensure their ports build on 10.X, and work with upstream support to integrate FreeBSD related patches. As always, this is not a reason to break the INDEX, please exercise due diligence before performing all commits. Thomas on behalf of portmgr@ ___ freebsd-ports-announce@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports-announce To unsubscribe, send any mail to freebsd-ports-announce-unsubscr...@freebsd.org
Re: non-destructive ports/packages update
Chris Rees utis...@gmail.com wrote: On 21 Apr 2013 02:13, Perry Hutchison per...@pluto.rain.com wrote: ... The question is, what (if anything) else -- besides /usr/ports, /usr/local, /var/db/ports, and /var/db/pkg -- needs to be checkpointed? Are you installing any drivers? You may need to back up /boot too. No drivers from ports here (nor any ports which overwrite base), but good to note this for the archives :) ___ 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: non-destructive ports/packages update
Peter Pentchev r...@ringlet.net wrote: Some ports might store run state in /var/db/portname or a similarly named directory. The thing is, the decision whether to save this and restore it or to keep it across runs actually depends on the port: for database management systems such as MySQL, PostgreSQL, etc, you'll probably want to keep the databases even if the ports themselves are reinstalled, rolled back, restored, whatever. For some other systems, you might want to remove the current state information of the version that you are about to replace. Good catch. No DBMS on this system, so no problem there, but there are two non-empty X11-related directories under /var/db: dbus and fontconfig. (The machine does have some X client apps, but not the X server.) ___ 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
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o ports/178048Milter installations failwhen sendmail is installed fr o ports/178047[maintainer update] sysutils/backuppc: update to 3.3.0 o ports/178045[MAINTAINER UPDATE] sysutils/sec: update to 2.7.2 f ports/178042sysutils/ezjail: zsh completion does not work o ports/178025[NEW PORT] net/grive: An open source client for Google f ports/178024mail/archmbox -- uses fuser(1) with incompatible flags o ports/178022[MAINTAINER] japanese/ja-ruby20-ming: Fix to work with o ports/178021print/latex2slides: [PATCH] tries to create directory f ports/178019[patch] editors/textroom: trim header, lib depends, an o ports/178013new port: www/rest - accessing RESTful web services o ports/178010[MAINTAINER UPDATE] sysutils/htop: Update to 1.0.2 o ports/178007[MAINTAINER UPDATE] www/libmicrohttpd: Update 0.9.26 f ports/178004games/minecraft-server: [PATCH] bad checksum, bad sche o ports/178003[MAINTAINER UPDATE] net/babeld: Update to 1.3.5 f ports/178002sysutils/password-store: checksum mismatch f ports/178001games/capitalism: unfetchable, subsite gone o ports/177998net/netembryo: unfetchable (bad master_site) f ports/177997databases/innobackup: unfetchable (www.innodb.com gone f ports/177994games/knights-kde4: unfetchable o ports/177993editors/xxe: unfetchable o ports/177992new port: astro/garmindev Garmin device drivers for QL f ports/177991astro/qlandkartegt : upgrade to 1.7.0 f ports/177987games/megaglest: fix build f ports/177967redrawing text bolts and occasionally blinks from unde f ports/177961Update port science/veusz to 1.17.1 f ports/177959mail/mailfront: patch for default options o ports/177958[MAINTAINER] net-mgmt/netdisco-mibs: update to 1.3 o ports/177956[MAINTAINER] net-mgmt/netdisco: update to 1.2 o ports/177954devel/bglibs: patch: perl is only needed runtime o ports/177951Update ports/samba4 to 4.0.5 o ports/177945[PATCH] dns/powerdns-recursor: update to 3.5 o ports/177906[new port] x11-fonts/fpf Free Persian font o ports/177900New port: net/owncloud-csync, a backend app for Ownclo f ports/177857[patch] Update x11/slim to 1.3.5 f ports/177839New version of news/nzbget (10.1) f ports/177797[PATCH] mail/postfix-policyd-spf-python: update to 1.1 o ports/177790[new port] security/axTLS f ports/15multimedia/gtk-youtube-viewer: properly support depend o ports/14[patch] net/nbd-server update to 3.3 f ports/177758security/amavisd-milter does not build on FreeBSD 9.1 f ports/177757[PATCH] www/awstats: update to 7.1.1,1 f ports/177755[patch] devel/rbenv: fix rbenv-init completions o ports/177753New port: sysutils/slurm-devel o ports/177745New port: science/lammps o ports/177744New port: science/lammps-openmpi f ports/177741net-mgmt/sipcalc cannot handle ipv6 zone index o ports/177733[maintainer update] graphics/nomacs update to version o ports/177726cad/p5-Verilog-Perl: update of p5-Verilog-Perl o ports/177724New port: math/matlab-R2012a-installer o ports/177723New port: devel/linux-f10-ncurses-base f ports/177721multimedia/mplayer: Missing dependency o ports/177719maintainer update: devel/swig20 o ports/177717update finance/opentaxsolver for TY 2012 o ports/177715Port: sysutils/procenv Utility to show process environ o ports/177692New port: science/openkim o ports/177684[maintainer update] www/xpi-pentadactyl o ports/177676[PATCH] net-mgmt/net-mgmt/argus3: Fix MANPAGES=no o ports/177675[PATCH] net-mgmt/argus3-clients: Fix MANPAGES=no f ports/177669news/nzbget - PostProcess script terminated with unkno o ports/177665[MAINTAINER] lang/rust: update to 0.6 o ports/177651New port: security/openiked OpenBSD's IKEv2 daemon o ports/177649[NEW PORT] net/hanstunnel: Hans makes it possible to t o ports/177643Update port graphics/fotoxx to latest version o ports/177641[new port] devel/kyua-cli Kyua (automated testing fram o ports/177640
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 +-+ archivers/zipper| 1.4 | 1.5 +-+ databases/geoserver-mysql-plugin| 2.1.1 | 2.3.1 +-+ games/lwjgl | 2.8.5 | 2.9.0 +-+ net-mgmt/xymon-client | 4.3.10 | 4.3.11 +-+ 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 If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. ___ 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
databases/pgbouncer devel/otrs maintainership
I'd like to maintain following unmaintained (former @skv) ports: databases/pgbouncer www/otrs -- Mikhail ___ 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
[HEADS UP] Ports Slush is now in effect
Just to make it official, the ports slush is over. Ports committers are now able to perform regular updates, business as usual, no need for portmgr@ approvals. Keep in mind that -exp runs are always a good idea if you think there is a significant change to the ports tree. It is anticipated that a FreeBSD 9.2 release schedule could be upon us quickly so we have elected to lift the slush period a little sooner than planned. We would like committers and maintainers alike to work on keeping the ports tree in shape for the next cycle. Additionally, we also have a FreeBSD 10.0 release coming up in the unspecified future, and many ports have work-arounds applied for them to work with autotools and for Clang. We would like all porters to use this extra time to ensure their ports build on 10.X, and work with upstream support to integrate FreeBSD related patches. As always, this is not a reason to break the INDEX, please exercise due diligence before performing all commits. Thomas on behalf of portmgr@ ___ 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
[CORRECTION] Ports Slush is now in over
Just to make it official, the ports slush is over. Ports committers are now able to perform regular updates, business as usual, no need for portmgr@ approvals. Keep in mind that -exp runs are always a good idea if you think there is a significant change to the ports tree. It is anticipated that a FreeBSD 9.2 release schedule could be upon us quickly so we have elected to lift the slush period a little sooner than planned. We would like committers and maintainers alike to work on keeping the ports tree in shape for the next cycle. Additionally, we also have a FreeBSD 10.0 release coming up in the unspecified future, and many ports have work-arounds applied for them to work with autotools and for Clang. We would like all porters to use this extra time to ensure their ports build on 10.X, and work with upstream support to integrate FreeBSD related patches. As always, this is not a reason to break the INDEX, please exercise due diligence before performing all commits. Thomas on behalf of portmgr@ ___ 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: CFT: google-earth crash fix (ports/160422 [1])
On Sun, 21 Apr 2013, Juergen Lock wrote: On Sun, Apr 21, 2013 at 12:25:37PM +0200, Kurt Jaeger wrote: Hi! http://people.freebsd.org/~nox/tmp/google-earth-6.0.3.2197-crashfixp-001.patch Works on 9.1-amd64. Ok as it seems to work for everyone that tested it I just committed the update. If it still crashes for some people it's at least much better than it was... Thanx! :) Juergen I ran across this thread and decided to install google-earth-6.0.3.2197,3. Svn ports/ revision is 316221. I got the following crashlog: Major Version 6 Minor Version 0 Build Number 0003 Build Date May 17 2011 Build Time 00:40:40 OS Type 3 OS Major Version 2 OS Minor Version 6 OS Build Version 16 OS Patch Version 0 Crash Signal 11 Crash Time 1366648366 Up Time 4.44642 Stacktrace from glibc: ./libgoogleearth_free.so[0x2813a953] ./libgoogleearth_free.so[0x2813aad3] [0xbfbff007] ./libQtWebKit.so.4[0x29492da2] ./libQtWebKit.so.4[0x29492e15] ./libQtWebKit.so.4[0x29493c66] ./libQtWebKit.so.4[0x29535f44] ./libQtWebKit.so.4[0x29535cf1] ./libQtWebKit.so.4[0x298c1e01] ./libQtWebKit.so.4[0x298c1e62] ./libQtWebKit.so.4[0x299d7536] ./libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x1a7)[0x282e79c7] ./libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0x285a469c] ./libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x426)[0x285af666] ./libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x78)[0x282d5ba8] ./libQtCore.so.4[0x28305af6] ./libQtCore.so.4(_ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0xc7)[0x28305cb7] ./libQtGui.so.4[0x2865] ./libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x49)[0x282d4b39] ./libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x102)[0x282d4d12] ./libQtCore.so.4(_ZN16QCoreApplication4execEv+0xaf)[0x282d71bf] ./libQtGui.so.4(_ZN12QApplication4execEv+0x27)[0x285a4177] ./libgoogleearth_free.so(_ZN5earth6client11Application3runEv+0x605)[0x28144ba5] ./libgoogleearth_free.so[0x2813940b] ./libgoogleearth_free.so(earthmain+0x247)[0x2813a587] ./googleearth-bin[0x804872b] /lib/libc.so.6(__libc_start_main+0xe5)[0x2a42b6e5] ./googleearth-bin[0x8048671] Thanks, Frank ___ 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: CFT: google-earth crash fix (ports/160422 [1])
On Sun, 21 Apr 2013, Juergen Lock wrote: On Sun, Apr 21, 2013 at 12:25:37PM +0200, Kurt Jaeger wrote: Hi! http://people.freebsd.org/~nox/tmp/google-earth-6.0.3.2197-crashfixp-001.patch Works on 9.1-amd64. Ok as it seems to work for everyone that tested it I just committed the update. If it still crashes for some people it's at least much better than it was... Thanx! :) Juergen ___ 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 Forgot to mention: 9.1-STABLE FreeBSD 9.1-STABLE #1 r249061 ___ 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: CFT: google-earth crash fix (ports/160422 [1])
On Mon, Apr 22, 2013 at 12:46:35PM -0400, Frank Seltzer wrote: On Sun, 21 Apr 2013, Juergen Lock wrote: On Sun, Apr 21, 2013 at 12:25:37PM +0200, Kurt Jaeger wrote: Hi! http://people.freebsd.org/~nox/tmp/google-earth-6.0.3.2197-crashfixp-001.patch Works on 9.1-amd64. Ok as it seems to work for everyone that tested it I just committed the update. If it still crashes for some people it's at least much better than it was... Thanx! :) Juergen ___ 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 Forgot to mention: 9.1-STABLE FreeBSD 9.1-STABLE #1 r249061 Hmm before we start worrying again... Did you have linprocfs mounted on /compat/linux/proc ? Juergen ___ 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: databases/pgbouncer devel/otrs maintainership
On 2013-04-22 15:34, Mikhail Tsatsenko wrote: I'd like to maintain following unmaintained (former @skv) ports: databases/pgbouncer www/otrs Hi Mikhail, I just assigned you as maintainer for the requested ports. Would you please review the following PR's PR 176640 : databases/pgbouncer: update 1.5.2 - 1.5.4 PR 175701 : [patch] devel/otrs update to 3.2.1 version Let us know if you are fine with the requests (PR follow-up) with a hint you are the new maintainer. Thanks for picking up the ports! -- olli ___ 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: databases/pgbouncer devel/otrs maintainership
22.04.2013, 22:33, Olli Hauer oha...@freebsd.org: On 2013-04-22 15:34, Mikhail Tsatsenko wrote: I'd like to maintain following unmaintained (former @skv) ports: databases/pgbouncer www/otrs Hi Mikhail, I just assigned you as maintainer for the requested ports. Would you please review the following PR's PR 176640 : databases/pgbouncer: update 1.5.2 - 1.5.4 PR 175701 : [patch] devel/otrs update to 3.2.1 version Let us know if you are fine with the requests (PR follow-up) with a hint you are the new maintainer. Thanks for picking up the ports! -- olli ___ 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 Hi Mikhail, Then please review/commit the patch for otrs-3.2.5(was attached). -- With Best Regards, Ilya A. Arkhipov___ 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
10.0-CURRENT #0 r249720: graphics/jasper: eval: @CC@: not found
Trying to update port graphics/jasper on our FreeBSD 10.0-CURRENT boxes (all r249720 or higher) fails on all(!) Core2Duo based systems (Intel E8400 or Q6600) (CLANG 3.3) with the below shown error. Interestingly, the port does compile on all boxes running the very same FreeBSD 10.0-CURRENT with either Sandy-Bridge-E (i7-3939K) or Ivy Bridge (i3-3220) CPUs. All systems have in common that I compile world and kernel with option -O3 (CLANG 3.3), -march=native. I also use the very same /etc/src.conf on all boxes: WITH_CLANG_EXTRAS= YES WITH_LLVM= YES WITH_LLVM_EXTRAS= YES # WITH_BIND_LIBS= YES WITH_BIND_SIGCHASE= YES WITH_BIND_LARGE_FILE= YES # WITH_IDEA= YES # #WITH_ICONV=YES #WITH_BSD_GREP= YES WITH_BSD_SORT= YES WITH_BSDCONFIG= YES WITH_BSD_PATCH= YES # #WITH_OFED= YES WITH_NAND= YES WITH_NMTREE=YES #WITH_BMAKE=YES #WITH_CTF= YES # MALLOC_PRODUCTION= YES I guess I hit a miscompilation with either option -O3 -march=native on Penryn architectures with the new CLANG 3.3 compiler? (By the way, I also see this obscure @CC@: not found error in compiling games/qstat and it hits also the Core2Duo boxes, but not any CPU type beyond the C2D). Error compiling port graphics/jasper: === Building for jasper-1.900.1_12 Making all in src Making all in libjasper Making all in include Making all in jasper /usr/bin/make all-am Making all in base if /bin/sh /usr/local/bin/libtool --tag=CC --mode=compile @CC@ -DHAVE_CONFIG_H -I. -I. -I../../../src/libjasper/include/jasper -I../../../src/libjasper/include -I/usr/local/include -O2 -pipe -O3 -march=native -fno-strict-aliasing -MT jas_cm.lo -MD -MP -MF .deps/jas_cm.Tpo -c -o jas_cm.lo jas_cm.c; then mv -f .deps/jas_cm.Tpo .deps/jas_cm.Plo; else rm -f .deps/jas_cm.Tpo; exit 1; fi libtool: compile: @CC@ -DHAVE_CONFIG_H -I. -I. -I../../../src/libjasper/include/jasper -I../../../src/libjasper/include -I/usr/local/include -O2 -pipe -O3 -march=native -fno-strict-aliasing -MT jas_cm.lo -MD -MP -MF .deps/jas_cm.Tpo -c jas_cm.c -fPIC -DPIC -o .libs/jas_cm.o eval: @CC@: not found *** [jas_cm.lo] Error code 1 Stop in /usr/ports/graphics/jasper/work/jasper-1.900.1/src/libjasper/base. *** [all-recursive] Error code 1 Stop in /usr/ports/graphics/jasper/work/jasper-1.900.1/src/libjasper. *** [all-recursive] Error code 1 Stop in /usr/ports/graphics/jasper/work/jasper-1.900.1/src. *** [all-recursive] Error code 1 Stop in /usr/ports/graphics/jasper/work/jasper-1.900.1. *** [do-build] Error code 1 Stop in /usr/ports/graphics/jasper. *** [build] Error code 1 Stop in /usr/ports/graphics/jasper. === make failed for graphics/jasper === Aborting update === Killing background jobs signature.asc Description: This is a digitally signed message part
Re: 10.0-CURRENT #0 r249720: graphics/jasper: eval: @CC@: not found
On Apr 22, 2013, at 20:47, O. Hartmann ohart...@zedat.fu-berlin.de wrote: Trying to update port graphics/jasper on our FreeBSD 10.0-CURRENT boxes (all r249720 or higher) fails on all(!) Core2Duo based systems (Intel E8400 or Q6600) (CLANG 3.3) with the below shown error. ... Interestingly, the port does compile on all boxes running the very same FreeBSD 10.0-CURRENT with either Sandy-Bridge-E (i7-3939K) or Ivy Bridge (i3-3220) CPUs. All systems have in common that I compile world and kernel with option -O3 (CLANG 3.3), -march=native. ... I guess I hit a miscompilation with either option -O3 -march=native on Penryn architectures with the new CLANG 3.3 compiler? (By the way, I also see this obscure @CC@: not found error in compiling games/qstat and it hits also the Core2Duo boxes, but not any CPU type beyond the C2D). This is most likely the same issue you reported in another thread, here: http://docs.freebsd.org/cgi/mid.cgi?1365877246.2093.20.camel The configure script tries to use sed to replace @CC@ with a build-time setting, but the sed replacement fails, because of a problem in the regex functions in libc, when libc is compiled with -O3 or higher. The exact cause of the problem is still unknown (likely a bug in the vectorizer, or less likely a bug in libc). Please recompile and reinstall at least your libc with -O2 instead of -O3, and retry the ports build afterwards. In general, if you use non-standard optimization settings, always remove the customizations first, before reporting problems. ___ 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: 10.0-CURRENT #0 r249720: graphics/jasper: eval: @CC@: not found
On Mon, 2013-04-22 at 21:40 +0200, Dimitry Andric wrote: On Apr 22, 2013, at 20:47, O. Hartmann ohart...@zedat.fu-berlin.de wrote: Trying to update port graphics/jasper on our FreeBSD 10.0-CURRENT boxes (all r249720 or higher) fails on all(!) Core2Duo based systems (Intel E8400 or Q6600) (CLANG 3.3) with the below shown error. ... Interestingly, the port does compile on all boxes running the very same FreeBSD 10.0-CURRENT with either Sandy-Bridge-E (i7-3939K) or Ivy Bridge (i3-3220) CPUs. All systems have in common that I compile world and kernel with option -O3 (CLANG 3.3), -march=native. ... I guess I hit a miscompilation with either option -O3 -march=native on Penryn architectures with the new CLANG 3.3 compiler? (By the way, I also see this obscure @CC@: not found error in compiling games/qstat and it hits also the Core2Duo boxes, but not any CPU type beyond the C2D). This is most likely the same issue you reported in another thread, here: http://docs.freebsd.org/cgi/mid.cgi?1365877246.2093.20.camel The configure script tries to use sed to replace @CC@ with a build-time setting, but the sed replacement fails, because of a problem in the regex functions in libc, when libc is compiled with -O3 or higher. The exact cause of the problem is still unknown (likely a bug in the vectorizer, or less likely a bug in libc). Please recompile and reinstall at least your libc with -O2 instead of -O3, and retry the ports build afterwards. You're right. After decreasing from -O3 to -O2 the problem on C2D machines went away. In general, if you use non-standard optimization settings, always remove the customizations first, before reporting problems. I should do, indeed, but isn't it interesting of the knowledge, that this happens only on Core2Duo architecure CPUs, but not on more modern designs? Regards, Oliver signature.asc Description: This is a digitally signed message part
ports repository exporting to github?
official mirrors for ports repository on github hasn't been updated for a few days. Does FreeBSD project quit to provide mirrors on github? or suspended temporarily? -- `whois vmeta.jp | nkf -w` meta m...@vmeta.jp ___ 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: FreeBSD Port: postfix-2.9.5,1 - LDAP_SASL option ignored
On Fri, 2013-03-22 at 11:54:14 +0200, Pavel Bychykhin wrote:
In config dialog i check OPENLDAP, LDAP_SASL and SASL2.
The make process ignores an option LDAP_SASL.
As a result i see unsupported parameter value: bind = SASL in output of
postmap command.
As a solution, i added -DUSE_LDAP_SASL directly into Makefile in
do-configure section:
do-configure:
(cd ${WRKSRC} ${MAKE} -f Makefile.init makefiles ${MAKEFILEFLAGS} \
CCARGS=${POSTFIX_CCARGS} -DUSE_LDAP_SASL
AUXLIBS=${POSTFIX_AUXLIBS} \
${ECHO} all: default Makefile)
After that changes, all works fine with LDAP SASL binding.
A different fix has been committed. Please let me know if the problem
persists.
--
Sahil Tandon
___
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: ports repository exporting to github?
On Tue, 23 Apr 2013 10:49:00 +0900 Koichiro IWAO m...@vmeta.jp wrote: official mirrors for ports repository on github hasn't been updated for a few days. Does FreeBSD project quit to provide mirrors on github? or suspended temporarily? possible I missed something, but.. Is a mirror on github was _official_ ? -- wbr, tiger ___ 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
