Passing cmpile flags to portmaster
let's say there is a port I want to install, but I want to pass the compile -WITH-FOO-BAR, how do I tell postmaster I want to do that? -- You are forgetting something: the Nazgul are immune to non-magical weapons. Any sufficiently advanced technology is indistinguishable from magic. ___ 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: Passing cmpile flags to portmaster
2013/8/26 LuKreme krem...@kreme.com: let's say there is a port I want to install, but I want to pass the compile -WITH-FOO-BAR, how do I tell postmaster I want to do that? -- You are forgetting something: the Nazgul are immune to non-magical weapons. Any sufficiently advanced technology is indistinguishable from magic. ___ 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 It's usually done within /etc/make.conf, portmaster just wraps make(1) in its script. Also, if you want more fine grained settings, you may take a look at ports-mgmt/portconf, but it will be deprecated with the new option framework. Cheers, -- Demelier David ___ 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
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 +-+ devel/paexec| 0.18.0 | 0.19.0 +-+ graphics/wxsvg | 1.1.15 | 1.1.16 +-+ lang/gcl| 2.6.7 | 2.6.9 +-+ 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...@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
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/181543Typo in subversion port Makefile o ports/181539[MAINTAINER] textproc/apache-solr: Update to 4.4.0 f ports/181530Upgrade lang/abcl to 1.2.1 o ports/181529sysutils/devcpu-data: Panic after CPU microcode update o ports/181527New port: multimedia/mjpg-streamer HTTP video streamin f ports/181520mplayer/mencoder failed to build with net/liveMedia 20 o ports/181518[patch] update net/scamper to 20130824 o ports/181517[maintainer update] for graphics/openimageio f ports/181511[PATCH] dns/dnscrypt-proxy: added rc.conf vars f ports/181507[PATCH] security/pks: fix autostart o ports/181506[maintainer-update] devel/eclipse-eclemma 2.2.1 f ports/181499[PATCH] emulators/dosbox: add icon o ports/181494[PATCH] update devel/cil to 1.7.3 o ports/181492[maintainer-update] multimedia/libbluray 0.3.0 multime o ports/181491[PATCH] update devel/clanlib to 2.3.7 f ports/181488[PATCH] Change security/prelude-pflogger to use getpro f ports/181483[PATCH] science/py27-h5py: update to 2.1.1_3 f ports/181481[PATCH] irc/ircd-ratbox fix default options broken by o ports/181480textproc/xerces-c2 and textproc/xerces-c2-devel missin o ports/181455New port: sysutils/sysvbanner o ports/181451[NEW PORT] misc/auto-multiple-choice: Multiple Choice o ports/181450[new port] www/linux-f10-flashplugin10 request, becase f ports/181449[update] lang/php52 to 5.2.17_15 (20130717) f ports/181443[patch] net-mgmt/collectd5: Update to 5.4.0 o ports/181431maintainer-update of mail/mutt f ports/181423[patch] databases/freetds-devel -- update to 0.92.79 f ports/181422[PATCH] graphics/geos: update to 3.4.1 f ports/181413[patch] emulators/visualboyadvance-m: unbreak build f ports/181399Update converters/pdf2djvu port to 0.7.17 and unbreak f ports/181391lang/itcl: fix REINPLACE usage o ports/181385[patch] x11-drivers/xf86-video-vmware: a fix from a VM f ports/181345net/tigervnc o ports/181334[New Port] lang/yap-devel o ports/181332Update databases/jasperreports to version 5.1.2 f ports/181324[patch] fix net/istgt with options VBOXVD (VirtualBox f ports/181308Update textproc/jakarta-poi to version 3.9 o ports/181301New port: net/kamailio - A very fast and configurable f ports/181294Missing dependency for www/glpi f ports/181291[PATCH] mail/postgrey: make postgrey work with perl 5. o ports/181288[maintainer update] dns/rbldnsd - update to 0.997a o ports/181286Update security/libscrypt libscrypt-1.13 and fixed i38 f ports/181251net-mgmt/mrtg: rateup constantly segfaulted because of f ports/181248[PATCH] print/cups-base Disable INSTALLS_ICONS for non o ports/181244New port: devel/ocl-icd OpenCL Installable Client Dri o ports/181243New port: devel/opencl-icd Khronos OpenCL Installable f ports/181230security/dirmngr fails to build after ld(1) update o ports/181160Port sysutils/bacula-client - All bacula-fd processes o ports/181137x11-clocks/wmfuzzy updates far too frequently, chewing o ports/181133[patch] x11-drivers/input-wacom: enabled support of wa f ports/181106sysutils/logrotate bus error (core dumped) f ports/181104audio/mumble: dubious patch to allow OSS device select f ports/181102[PATCH] audio/mumble cannot find bundled libcelt f ports/181089graphics/ufraw needs to follow glib/gettext changes o ports/181077[patch] ports-mgmt/pkg_replace support pkgng f ports/181040[patch] sysutils/conky diskio memory leak fix o ports/181038print/acrobatviewer dies with null pointer exception w f ports/181021x11-toolkits/open-motif fails to build because YY_MAIN o ports/180987[NEW PORTs] audio/ardour3 and multimedia/harvid f ports/180984math/openblas: Patch patch-exports+gensymbol failed t o ports/180967Update port games/opensonic to 0.1.4 f ports/180959[PATCH] x11/x3270: update to 3.3.12 o ports/180954sysutils/pciutils (lspci) uses its own database and no o ports/180925Can't compile
xpi-* broken since firefox-22
I don't know whether that's a general problem or just affects me, but since Firefox 22 the xpi-* ports don't work for me any more. I.e. they install just fine, but firefox doesn't pick them up. I'm a huge fan of everything goes into the package system and I am convinced plugin systems and automatic updates are just hacks that wouldn't even exist if Windows had a package system. But there simply are too many firefox addons and I think before anything gets fixed it's time to put down some hard rule for plugin/addon kind of stuff. My suggestion is the following: Any plugin/addon may be added to the ports collection if one or more of the following conditions are met: - The plugin/addon builds/contains native code - The plugin/addon is a dependency of another port - The plugin/addon improves the integration with the base system, .e.g. it adds support for common environment variables like LANG, HTTP_PROXY or TZ -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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
print/cups: 10.0-CURRENT renders cups unusable / recompilation fails due to missing libiconv
Today I update a box to 10.0-CURRENT #0 r254896: Mon Aug 26 09:42:48 CEST 2013 amd64. Bevor the update this morning, I ran a box with the sources from around last Friday and port print/cups was working fine so far. After building/installation of world/kernel today as of r254896 the cups daemon didn't respond when accessd locally via port 631, printing is rejected with messages like reset by peer and furthermore, when I thought the cups binary might be out of sync with the environment, I tried to recompile the whole preint/cups installation, but this fails now in a close to EPICAL way not finding libiconv [...] cc -L../cgi-bin -L../cups -L../filter -L../ppdc -L../scheduler -L/usr/local/lib -Wl,-rpath=/usr/lib:/usr/local/lib -Wl,-R/usr/local/lib -Wall -Wno-format-y2k -Wunused -fPIC -Os -g -fstack-protector -Wno-tautological-compare -o bannertops bannertops.o pstext.o common.o -lcupsimage \ -lcups -lssl -lcrypto -lz -pthread -lcrypt -lm -lssp_nonshared ../cups/libcups.so: undefined reference to `libiconv' ../cups/libcups.so: undefined reference to `libiconv_close' ../cups/libcups.so: undefined reference to `libiconv_open' Well, freeBSD 10.0-CUR seems now out of cups as far as I can see. The old installation is not working since it now rejects connections, a recompilation isn't possible due to the libiconv issue. What happens here, how can this problem be solved? Regards, Oliver P.S. Sorry for cross posting, but I think this is for both CURRENT and PORT list of interest. signature.asc Description: PGP signature
Re: print/cups: 10.0-CURRENT renders cups unusable / recompilation fails due to missing libiconv
On Aug 26, 2013, at 15:54, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
Today I update a box to 10.0-CURRENT #0 r254896: Mon Aug 26 09:42:48
CEST 2013 amd64. Bevor the update this morning, I ran a box with the
sources from around last Friday and port print/cups was working fine
so far.
After building/installation of world/kernel today as of r254896 the
cups daemon didn't respond when accessd locally via port 631, printing
is rejected with messages like reset by peer
I can't help you with this...
and furthermore, when I
thought the cups binary might be out of sync with the environment, I
tried to recompile the whole preint/cups installation, but this fails
now in a close to EPICAL way not finding libiconv
[...]
cc -L../cgi-bin -L../cups -L../filter -L../ppdc -L../scheduler
-L/usr/local/lib -Wl,-rpath=/usr/lib:/usr/local/lib
-Wl,-R/usr/local/lib -Wall -Wno-format-y2k -Wunused -fPIC -Os -g
-fstack-protector -Wno-tautological-compare -o bannertops bannertops.o
pstext.o common.o -lcupsimage \ -lcups -lssl -lcrypto -lz -pthread
-lcrypt -lm -lssp_nonshared ../cups/libcups.so: undefined reference to
`libiconv' ../cups/libcups.so: undefined reference to
`libiconv_close' ../cups/libcups.so: undefined reference to
`libiconv_open'
... but maybe I can help here. This is due to iconv being enabled in
the base system, as I pointed out here:
http://lists.freebsd.org/pipermail/freebsd-ports/2013-August/085459.html
The easiest workaround for now is to force LDFLAGS to contain -liconv
in the port's Makefile, e.g.:
Index: print/cups-base/Makefile
===
--- print/cups-base/Makefile(revision 324846)
+++ print/cups-base/Makefile(working copy)
@@ -23,7 +23,7 @@
GNU_CONFIGURE= yes
CFLAGS+= ${PTHREAD_CFLAGS}
CPPFLAGS+= -I${LOCALBASE}/include
-LDFLAGS+= -L${LOCALBASE}/lib
+LDFLAGS+= -L${LOCALBASE}/lib -liconv
DSOFLAGS= -Wl,-rpath,${PREFIX}/lib -L${PREFIX}/lib ${LDFLAGS}
CONFIGURE_ENV= DSOFLAGS=${DSOFLAGS}
CONFIGURE_ARGS+= --localstatedir=/var\
-Dimitry
___
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
portmaster dependency problems
Hello. I've been using portmaster successfully (and exclusively) for many years. Previously I built a 9.2-PRERELEASE machine and ports using portmaster-3.17.1 without PKG_NG: portmaster -bwDH --delete-build-only --no-confirm ... Recently I decided to rebuild everything from packages after first removing all the preset options (i.e. removing /var/db/ports/* ) and then (still using portmaster-3.17.1 without PKG_NG): env BATCH=y portmaster -abfwDHP --packages-build \\ --delete-build-only --packages-newer --no-confirm Because the options changed mast of the dependencies are now messed up. For example: # portmaster --check-depends ... === Checking alacarte-0.13.2_2 === print/ghostscript9 is listed as a dependency === but there is no installed version ... # pkg_info -Ix ghostscript ghostscript9-nox11-9.06_4 Ghostscript 9.x PostScript interpreter To fix this specific problem, I have separately tried using: portmaster -o print/ghostscript9 ghostscript and: portmaster -o print/ghostscript9-nox11 ghostscript In both cases, portmaster leaves an empty @pkgdep line in /var/db/pkg/alacarte-0.13.2_2+CONTENTS just before: @comment DEPORIGIN:print/ghostscript9 and never updates the origin to print/ghostscript9-nox11. What am I doing wrong? Or how can I fix these broken dependencies? This used to work fine with older versions of portmsater when the origins shifted around. But now I have a few hundred ports which depend upon (for example) ghostscript so I'd rather not have to manually fix everything. Also, I don't think that running portmaster --check-depends -y would be a good option since that would remove all those broken dependencies and would require me to reinstall those hundreds of ports. Any ideas? Thanks in advance, -- Rick C. Petty KIWI Computer ___ 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: print/cups: 10.0-CURRENT renders cups unusable / recompilation fails due to missing libiconv
On Mon, 26 Aug 2013 16:24:26 +0200
Dimitry Andric d...@freebsd.org wrote:
[...]
and furthermore, when I
thought the cups binary might be out of sync with the environment, I
tried to recompile the whole preint/cups installation, but this
fails now in a close to EPICAL way not finding libiconv
[...]
cc -L../cgi-bin -L../cups -L../filter -L../ppdc -L../scheduler
-L/usr/local/lib -Wl,-rpath=/usr/lib:/usr/local/lib
-Wl,-R/usr/local/lib -Wall -Wno-format-y2k -Wunused -fPIC -Os -g
-fstack-protector -Wno-tautological-compare -o bannertops
bannertops.o pstext.o common.o -lcupsimage \ -lcups -lssl
-lcrypto -lz -pthread -lcrypt -lm
-lssp_nonshared ../cups/libcups.so: undefined reference to
`libiconv' ../cups/libcups.so: undefined reference to
`libiconv_close' ../cups/libcups.so: undefined reference to
`libiconv_open'
... but maybe I can help here. This is due to iconv being enabled in
the base system, as I pointed out here:
http://lists.freebsd.org/pipermail/freebsd-ports/2013-August/085459.html
The easiest workaround for now is to force LDFLAGS to contain -liconv
in the port's Makefile, e.g.:
Index: print/cups-base/Makefile
===
--- print/cups-base/Makefile (revision 324846)
+++ print/cups-base/Makefile (working copy)
@@ -23,7 +23,7 @@
GNU_CONFIGURE= yes
CFLAGS+= ${PTHREAD_CFLAGS}
CPPFLAGS+= -I${LOCALBASE}/include
-LDFLAGS+=-L${LOCALBASE}/lib
+LDFLAGS+=-L${LOCALBASE}/lib -liconv
DSOFLAGS=-Wl,-rpath,${PREFIX}/lib -L${PREFIX}/lib ${LDFLAGS}
CONFIGURE_ENV= DSOFLAGS=${DSOFLAGS}
CONFIGURE_ARGS+= --localstatedir=/var\
-Dimitry
___
freebsd-curr...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
freebsd-current-unsubscr...@freebsd.org
Sorry, I missed the detailed explanation and how-to.
Applying the add on th LDCONFIG solves the problem.
Thank you very much
Oliver
signature.asc
Description: PGP signature
Re: xpi-* broken since firefox-22
On 26.08.13 14:07, Dominic Fandrey wrote: I don't know whether that's a general problem or just affects me, but since Firefox 22 the xpi-* ports don't work for me any more. This was broken for a brief period, it should be fixed though. You might need to reinstall the xpis so that the correct links are created. Any plugin/addon may be added to the ports collection if one or more of the following conditions are met: - The plugin/addon builds/contains native code - The plugin/addon is a dependency of another port - The plugin/addon improves the integration with the base system, .e.g. it adds support for common environment variables like LANG, HTTP_PROXY or TZ That's the plan anyway. I'm working on it. Enigmail and lightning will stay, perhaps the MOZILLA-xpi ports, but I'm leaning to removing those too, as they can be installed from addons.mozilla.org just fine. I'm just busy and haven't put this up for approval/discussion, yet. Florian signature.asc Description: OpenPGP digital signature
Re: xpi-* broken since firefox-22
On 26/08/2013 18:59, Florian Smeets wrote: On 26.08.13 14:07, Dominic Fandrey wrote: I don't know whether that's a general problem or just affects me, but since Firefox 22 the xpi-* ports don't work for me any more. This was broken for a brief period, it should be fixed though. You might need to reinstall the xpis so that the correct links are created. Thanks, when it happened I installed everything locally and that probably masks that the ports xpis work again. Any plugin/addon may be added to the ports collection if one or more of the following conditions are met: - The plugin/addon builds/contains native code - The plugin/addon is a dependency of another port - The plugin/addon improves the integration with the base system, .e.g. it adds support for common environment variables like LANG, HTTP_PROXY or TZ That's the plan anyway. I'm working on it. Enigmail and lightning will stay, perhaps the MOZILLA-xpi ports, but I'm leaning to removing those too, as they can be installed from addons.mozilla.org just fine. I'm just busy and haven't put this up for approval/discussion, yet. I'm maintainer of 2 xpi- ports. I'm willing to continue maintaining them if this is the verdict. But my vote is on getting rid of them. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: How to start wine?
What are LD_LIBRARY_PATH and LD_32_LIBRARY_PATH supposed to be? I see neither of these environment variables defined. And what about PATH? I am trying #!/bin/sh set PATH=/compat/i386/usr/local/bin:/compat/i386/usr/local/sbin:/compat/i386/usr/bin:/compat/i386/usr/sbin:/compat/i386/bin:/compat/i386/sbin:$PATH export LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/lib:/compat/i386/lib:$LD_32_LIBRARY_PATH export LD_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/lib:/compat/i386/lib:$LD_LIBRARY_PATH but I feel like I'm just thrashing here, will run into trouble trying to execute 32-bit binaries when not appropriate. I see /lib /libexec /usr/lib /usr/lib32 /usr/libdata /usr/libexec /usr/local/lib /usr/local/libdata /usr/local/libexec and then there are some subdirectories of these directories with the FreeBSD i386 installation not mounted. I have seen LD_LIBRARY_PATH before from building packages from source. I thought maybe wineboot would set up the environment, but it looks like I have to set up the environment beforehand. What is the difference between the various wine ports in $PORTSDIR/emulators? I used wine-devel, newer but less tested than wine. Upstream latest release is 1.6 as far as I can see. Building X for FreeBSD i386 before wine would be necessary for running from i386 boot even if not runnable from amd64. My i386 version was/is somewhat behind amd64 version. Tom ___ 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: How to start wine?
On Monday, 26 August 2013 11:58:12 Thomas Mueller wrote: What are LD_LIBRARY_PATH and LD_32_LIBRARY_PATH supposed to be? I see neither of these environment variables defined. The LD_(32_)LIBRARY_PATH variables are used by ld-elf(32).so.1 in resolving the libraries. And what about PATH? PATH will not fix the problem, in this case, unless wine needs to find support binaries (such as wineserver). I am trying #!/bin/sh set PATH=/compat/i386/usr/local/bin:/compat/i386/usr/local/sbin:/compat/i386/us r/bin:/compat/i386/usr/sbin:/compat/i386/bin:/compat/i386/sbin:$PATH export LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/lib:/compat/ i386/lib:$LD_32_LIBRARY_PATH export LD_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/lib:/compat/i38 6/lib:$LD_LIBRARY_PATH The bootstrap code from i386-wine does the following: if [ -z $__BINBOUNCE_BOOTSTRAP ] then export LIBGL_DRIVERS_PATH=$LOCALBASE/lib32/dri if [ `uname -p` = i386 ] then export LD_LIBRARY_PATH=$LOCALBASE/lib32:$LOCALBASE/lib32/wine:$LD_LIBRARY_PATH else export LD_32_LIBRARY_PATH=$LOCALBASE/lib32:$LOCALBASE/lib32/wine:$LD_32_LIBRARY_PATH:/usr/lib32 fi export PATH=$LOCALBASE/bin32:$PATH fi What is the difference between the various wine ports in $PORTSDIR/emulators? I used wine-devel, newer but less tested than wine. emulators/wine - Stable version of wine, currently 1.4.1 (we are waiting for 1.6.1). Currently only i386 is supported. emulators/wine-devel - Development version (works for most people), currently 1.7.0. Currently only i386 is supported. emulators/i386-wine - amd64 version of wine tracking emulators/wine emulators/i386-wine-devel - amd64 version of wine tracking emulators/wine- devel I suggest you try i386-wine(-devel) and see if that works for you. If it does and you want to build from source have a look at the Makefile for some of the changes required. Regards signature.asc Description: This is a digitally signed message part.
devel/jenkins port not starting. Kernel panic in IPv6 multicast code
Hi,
Sorry for the cross-posting, but I'm not 100% sure where the problem
is, either with the Jenkins port, Java, or FreeBSD networking code..
I recently tried to install the devel/jenkins port
on two separate boxes:
(1) box 1 running FreeBSD-9-STABLE.
(2) box 2 running running FreeBSD-CURRENT r254815
On box 1 when I tried to run jenkins with service jenkins start,
I got a Java error with backtrace:
WARNING: Failed to advertise the service to DNS multi-cast
(see attached jenkins.log.txt)
On box 2, since I this is a debug kernel with WITNESS and INVARIANTS
enabled, I get a kernel panic. (see attached core.txt.gz)
The panic occurs here on line 1779:
1768 static struct ifnet *
1769 in6p_lookup_mcast_ifp(const struct inpcb *in6p,
1770 const struct sockaddr_in6 *gsin6)
1771 {
1772 struct route_in6 ro6;
1773 struct ifnet*ifp;
1774
1775 KASSERT(in6p-inp_vflag INP_IPV6,
1776 (%s: not INP_IPV6 inpcb, __func__));
1777 KASSERT(gsin6-sin6_family == AF_INET6,
1778 (%s: not AF_INET6 group, __func__));
1779 KASSERT(IN6_IS_ADDR_MULTICAST(gsin6-sin6_addr),
1780 (%s: not multicast, __func__));
If I look at gsin6-sin6_addr inside kgdb,
I see:
(kgdb) p gsin6-sin6_addr
$1 = {__u6_addr = {__u6_addr8 =
\000\000\000\000\000\000\000\000\000\000���M|�, __u6_addr16 = {0, 0, 0,
0, 0, 65535, 19951, 54652}, __u6_addr32 = {0, 0,
4294901760, 3581693423}}}
I am not so familiar with this part of the networking code.
Can someone recommend where is the best place to fix
this would be?
Thanks.
--
Craig
Running from: /usr/local/share/jenkins/jenkins.war
Aug 26, 2013 9:58:27 AM winstone.Logger logInternal
INFO: Beginning extraction from war file
Jenkins home directory: /usr/local/jenkins found at:
System.getProperty(JENKINS_HOME)
Aug 26, 2013 9:58:30 AM winstone.Logger logInternal
INFO: HTTP Listener started: port=8180
Aug 26, 2013 9:58:30 AM winstone.Logger logInternal
INFO: AJP13 Listener started: port=8009
Aug 26, 2013 9:58:30 AM winstone.Logger logInternal
INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled
Aug 26, 2013 9:58:30 AM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Aug 26, 2013 9:58:38 AM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Aug 26, 2013 9:58:38 AM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Aug 26, 2013 9:58:39 AM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Aug 26, 2013 9:58:39 AM jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
Aug 26, 2013 9:58:39 AM jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
Aug 26, 2013 9:58:48 AM org.jenkinsci.main.modules.sshd.SSHD start
INFO: Started SSHD at port 19672
Aug 26, 2013 9:58:48 AM jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
Aug 26, 2013 9:58:48 AM hudson.TcpSlaveAgentListener init
INFO: JNLP slave agent listener started on TCP port 54687
Aug 26, 2013 9:58:48 AM hudson.UDPBroadcastThread run
WARNING: UDP handling problem
java.net.SocketException: Invalid argument
at java.net.PlainDatagramSocketImpl.join(Native Method)
at
java.net.AbstractPlainDatagramSocketImpl.join(AbstractPlainDatagramSocketImpl.java:168)
at java.net.MulticastSocket.joinGroup(MulticastSocket.java:300)
at hudson.UDPBroadcastThread.run(UDPBroadcastThread.java:76)
Aug 26, 2013 9:58:48 AM hudson.WebAppMain$3 run
INFO: Jenkins is fully up and running
Aug 26, 2013 9:58:48 AM hudson.DNSMultiCast$1 call
WARNING: Failed to advertise the service to DNS multi-cast
java.net.SocketException: Invalid argument
at java.net.PlainDatagramSocketImpl.join(Native Method)
at
java.net.AbstractPlainDatagramSocketImpl.join(AbstractPlainDatagramSocketImpl.java:168)
at java.net.MulticastSocket.joinGroup(MulticastSocket.java:300)
at javax.jmdns.impl.JmDNSImpl.openMulticastSocket(JmDNSImpl.java:459)
at javax.jmdns.impl.JmDNSImpl.init(JmDNSImpl.java:420)
at javax.jmdns.JmDNS.create(JmDNS.java:60)
at hudson.DNSMultiCast$1.call(DNSMultiCast.java:32)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
___
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: How to start wine?
The bootstrap code from i386-wine does the following: if [ -z $__BINBOUNCE_BOOTSTRAP ] then export LIBGL_DRIVERS_PATH=$LOCALBASE/lib32/dri if [ `uname -p` = i386 ] then export LD_LIBRARY_PATH=$LOCALBASE/lib32:$LOCALBASE/lib32/wine:$LD_LIBRARY_PATH else export LD_32_LIBRARY_PATH=$LOCALBASE/lib32:$LOCALBASE/lib32/wine:$LD_32_LIBRARY_PATH:/usr/lib32 fi export PATH=$LOCALBASE/bin32:$PATH fi I see no /usr/local/lib32 directories; just /usr/lib32, and much bigger for amd64 than for i386. I see /compat/i386/usr/local/lib/wine so I guess that needs to be included in LD_32_LIBRARY_PATH? The only lib directory dri was in /usr/local/lib/dri and only for amd64 because I didn't build X for i386 (not yet). So now my winepath.sh is (to be run before any wine binaries, and avoiding nonexistent directories) #!/bin/sh export LIBGL_DRIVERS_PATH=/usr/local/lib/dri export PATH=/compat/i386/usr/local/bin:$PATH export LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/local/lib/wine:/compat/i386/usr/lib32:$LD_32_LIBRARY_PATH:/usr/lib32 # export LD_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/lib:/compat/i386/lib:$LD_LIBRARY_PATH Is it necessary to set environment variables like this when running wine on i386? I'd like to try from both amd64 and i386. Tom ___ 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
Part of bsd.port.mk broken with pkgng
Hi, in bsd.port.mk there is a variable ACTUAL-PACKAGE-DEPENDS. To my understanding it is broken with pkgng. The target where this is used is still used if FORCE_PACKAGE is set. Can someone confirm (I've only read the code)? Previously this target was used to only record the explicit dependencies of a port and not all the recursive dependencies. To my understanding (again, I've only read the code) the EXPLICIT_PACKAGE_DEPENDS feature is broken now at least on systems which don't use pkgng (it seems that one of the changes to support pkgng in bsd.port.mk introduced this regression). I don't know how pkgng handles this part of the package creation. If it has no internal knowledge similar to EXPLICIT_PACKAGE_DEPENDS, this feature is broken with pkgng too. Can someone confirm? If my analysis is correct, does someone know if this is on the TODO list of pkgng? This is specially interesting as the release process of FreeBSD 10 is starting and it seems that the ld of FreeBSD 10 doesn't record recursive lib-dependencies anymore and as such it may be interesting to switch to EXPLICIT_PACKAGE_DEPENDS for 10-onwards. Bye, Alexander. -- http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ 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
