Please commit PR#203931 dns/knot2
has maintainer approval. thanks everyone https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203931 ___ 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"
dns/knot2 Would much appreciate committer
Maintainer seems to have overlooked this PR. Trying again seeking maintainer feedback/approval. Thanks to everyone. Viva la FreeBSD Changes should be pretty cut and dried if any committer would like to take a look. I copied the implementation more or less verbatim from openvpn's rc.d script. Any feedback/issues, I'd be happy to resolve. I'm well versed in Bourne sh. Bug 203931 - [PATCH] dns/knot2 enable multiple instances in rc.d script https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203931 ___ 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"
pkg-config fails after update to 1.6.0 of security/libssh2
one thing i noticed this break is the LIBSSH2 option on multimedia/vlc.
fix is attached. if attachment gets stripped off of email to list, it's
available at https://nuos.org/security_libssh2.diff . if this link is
broken it's because a fix has been committed to ports tree.
Index: Makefile
===
--- Makefile(revision 397608)
+++ Makefile(working copy)
@@ -3,7 +3,7 @@
PORTNAME= libssh2
PORTVERSION= 1.6.0
-PORTREVISION= 0
+PORTREVISION= 1
PORTEPOCH= 2
CATEGORIES=security devel
MASTER_SITES= http://www.libssh2.org/download/ \
@@ -48,4 +48,8 @@
${WRKSRC}/configure
.endif
+post-build:
+ @${REINPLACE_CMD} -E -e
'/Requires.private:/{s/[[:<:]]zlib[[:>:]]//;s/,,/,/;s/ ,/ /;s/,$$//;}' \
+ ${WRKSRC}/libssh2.pc
+
.include
___
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: ZFS 9.2/9.3 oh so broken...
> 9.x is really quite old I'd strongly advise you move to 10.2 as it includes a > lot of fixes and enhancements to many areas including ZFS. 9.3 isn't that old and as far as I'm concerned 10.x is still today unfortunately causing more problems than it's fixed. That's just my opinion though. I'm an old coot with a fear of the cutting edge. I'll be bringing up the rear clutching onto my legacy OS, thank you very much. Don't push me. "Get off my lawn." I'm not totally alone in this sentiment, am I? I haven't had a single issue to report with online replacement and resilvering of drives on 9.0-9.3 and I've probably swapped about 20 failed drives using ZFS across 9.x versions. Yes, I've had a second drive fail while resilvering a disk in a raidz2. I haven't used any hardware RAID controllers in conjunction with FreeBSD for about 5 years now and at first glance it looked to me like the OP might have been. (Sorry I didn't look at it in detail, I'm on my phone and pastedumps hurt my eyes.) Sorry to spam the list, I realize this is not the place for either topic. ___ 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: [HEADS-UP] switching default Perl to 5.22
On Aug 28, 2015, at 12:11 PM, Konstantin Belousov kostik...@gmail.com wrote: On Fri, Aug 28, 2015 at 05:49:30PM +0200, Mathieu Arnold wrote: +--On 28 ao??t 2015 17:44:55 +0200 Mathieu Arnold m...@freebsd.org wrote: | +--On 28 ao??t 2015 17:34:49 +0200 Mark Martinec | mark.martinec+free...@ijs.si wrote: || 2015-08-28 17:16, Mathieu Arnold wrote: || +--On 28 ao??t 2015 17:13:34 +0200 Kurt Jaeger li...@opsec.eu wrote: || | | In one or two weeks, I'll be switching the default Perl version || to || | | 5.22, and from now on, the new Perl will be added at the end of || May || | | when released, and switched to at the beginning of September. || | | || | | mod_perl is still broken with 5.22. Which is very sad. So maybe || | | it's premature to switch the default ? || | || | But, it was building when I added Perl 5.22 in May, when did it || break ? || | || | ohauer marked it broken on the 9th of June. || || Oh, maybe it did not work and I told myself never mind, mod_perl never || works anyway || || The lang/perl5.20 will still be in ports, for anyone that needs it. || || Being heavy Perl users we have switched to 5.22 when it hit the ports, || and I have no complaints about it. | | Oh, yes, Perl 5.20 will still be until 2018-12-31, as will 5.18 until | 2017-12-31 and 5.16 until 2016-12-31 :-) Scratch that, remove one year for all those 0:-) There is definitely some acrimony in the 5.22 release. I only mention Canary::Stability/stableperl bitter taste. The TeXlive tlmgr tripped over the cosmetic but annoying regression in 5.22, there were no fix some time ago, despite the fact that the bug was known for porters for long time, see http://www.perlmonks.org/?node_id=1132751 (the article claims that the issue was fixed, I am not sure). Previous policy, even if informal, was to wait for 5.xx.1 before bringing the port to the tree. May be, we should wait for xx.1 before switching the default port, at least ? I second this. I'm using 5.22 happily, however I think bumping the default is premature. I for one appreciate the conservative nature of FreeBSD and don't think we should feel compelled to keep up with the Joneses. ___ 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: Would a committer please commit my update to net-p2p/namecoin?
Thanks for the assistance! Bitcoin core currently also is stuck on db 4.8, and not only on FreeBSD. I'll continue researching it further as I too was aware db48 is long in the tooth and has its days numbered. As soon as I can I'll make db ver 4, 5 and 6 work via options but for now can I just stick to db48 if that's alright? This update to 0.3.80 in ports is long overdue. On Jun 4, 2015, at 4:32 PM, Kurt Jaeger li...@opsec.eu wrote: Hi! Any idea whether 6 would be OK ? A test build with db6 on 10.1pX amd64 builds namecoin. I have not tested it. A testbuild with db6 using poudriere failed 8-( See https://people.freebsd.org/~pi/logs/ net-p2p__namecoin-10x-1433419365.txt net-p2p__namecoin-84i-1433419365.txt net-p2p__namecoin-93a-1433419365.txt -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ 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
Would a committer please commit my update to net-p2p/namecoin?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193534 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193534 has a txz attachment of my latest version (now at 0.3.80) which contains directories namecoin and namecoin-daemon (please add namecoin-daemon port while updating namecoin port.) Be sure the files which no longer exist in the port get deleted from the ports tree (patches which were upstreamed). Thank you ___ 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] multiple instance support in rc.d script
On 10/22/14 17:02, Jim Riggs wrote: On 16 Oct 2014, at 20:22, Hiroki Sato h...@freebsd.org wrote: I would like your feedback and testers of the attached patch. This implements multiple instance support in rc.d scripts. You can try it by replacing /etc/rc.subr with the attached one. I really like the idea, as I have written at least 2 or 3 ports in which I have needed support for multiple profiles (as I have seen them called in several ports). So, I had to duplicate the multiple-instance logic in the rc script for each. This would save all of that aggravation. The only concern I have with generalizing the approach in rc.subr, though, is that not every app/daemon/script can or should support it. I worry that some things if run multiple times may stomp on each other or corrupt data or break something. It seems that there should be a way for each rc script to either opt in or opt out of multiple instance support. I don't know which is better. Opt-in is probably safer, but then core devs and port maintainers have to make specific changes to support it. :-\ Thoughts? Opt-in please ___ 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: Switching from building ports to packages
On 09/14/14 16:34, Matt Reimer wrote:
I'd like to switch from building everything from source using ports to
using packages as much as possible. This requires identifying which ports
I'm currently building use the same port knobs as the binary packages that
FreeBSD builds. Is there an easy way of showing how my port configs differ
from the defaults that are used to build binary packages?
Thanks in advance.
Matt
this script below will do exactly that from the port building machine if
you built them all in one place. (it gathers from
/var/db/ports/*/options but does not mine the data from
/var/db/pkg/local.sqlite.) if you'd like to extract options out of your
installed binary pkg ng's or pkg_og's or dir of .txz's or .tbz's laying
around somewhere and compare those to the current ports tree, let me
know. it's slightly more difficult but not terrible.
in case of mail munging and for your convenience this script is posted
to https://cargobay.net/LpYDhX3U with SHA256 (LpYDhX3U) =
4ef3dae564d861fd32efad267bb3e360a498d4688bb86fca7e2a0a195e58a34f
#!/bin/sh
_=/dev/null
cd /usr/ports
_a=PORT_DBDIR=/var/empty
for p in /var/db/ports/*; do
p=${p#/*/*/*/}
c=${p%%_*}
d=${p#*_}
if cd $c/$d; then
for z in a b; do
eval make \$_$z showconfig 2$_ /tmp/$$.$z
done
if ! diff /tmp/$$.[ab] $_; then
echo $c/$d
diff /tmp/$$.[ab] | grep ^ | cut -c 2-
fi
cd ../..
fi
done
rm /tmp/$$.[ab]
___
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: Switching from building ports to packages
On 09/14/14 16:34, Matt Reimer wrote: I'd like to switch from building everything from source using ports to using packages as much as possible. This requires identifying which ports I'm currently building use the same port knobs as the binary packages that FreeBSD builds. Is there an easy way of showing how my port configs differ from the defaults that are used to build binary packages? Thanks in advance. Matt IMPORTANT not to forget that things you may have put in your /etc/make.conf such as DEFAULT_VERSIONS etc may affect far more ports than you realize even when those ports have default OPTIONS. ___ 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
perl related error in mail/cyrus-imapd24
I'm gonna look into this further today but maybe one of you can make quicker sense of this. I just got this error while building cyrus-imapd24-2.4.17_8. Port options are default but my make.conf sets perl to 5.20. My make.conf is included below the error. Many thanks to anyone that even glances at this error to help. :) ### Making all in /usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl ### Making all in /usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl/imap Checking if your kit is complete... Looks good Generating a Unix-style Makefile Writing Makefile for Cyrus::IMAP Writing MYMETA.yml and MYMETA.json Smartmatch is experimental at /usr/local/lib/perl5/5.20/BSDPAN/ExtUtils/Packlist.pm line 218. cp IMAP.pm blib/lib/Cyrus/IMAP.pm cp IMAP/Shell.pm blib/lib/Cyrus/IMAP/Shell.pm cp IMAP/IMSP.pm blib/lib/Cyrus/IMAP/IMSP.pm cp IMAP/Admin.pm blib/lib/Cyrus/IMAP/Admin.pm Running Mkbootstrap for Cyrus::IMAP () chmod 644 IMAP.bs /usr/local/bin/perl5.20.0 /usr/local/lib/perl5/5.20/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.20/ExtUtils/typemap -typemap typemap IMAP.xs IMAP.xsc mv IMAP.xsc IMAP.c cc -c -I../../lib -I../.. -I../../com_err/et -I/usr/local/include -I/usr/include -DAPPLLIB_EXP=/usr/local/lib/perl5/5.20/BSDPAN -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -DDEBUGGING -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -g-DVERSION=\1.00\ -DXS_VERSION=\1.00\ -DPIC -fPIC -I/usr/local/lib/perl5/5.20/mach/CORE -DPERL_POLLUTE IMAP.c In file included from /usr/local/lib/perl5/5.20/mach/CORE/perl.h:5152, from IMAP.xs:51: /usr/local/lib/perl5/5.20/mach/CORE/inline.h: In function 'S_append_utf8_from_native_byte': /usr/local/lib/perl5/5.20/mach/CORE/inline.h:264: error: expected ')' before ',' token /usr/local/lib/perl5/5.20/mach/CORE/inline.h:264: error: void value not ignored as it ought to be /usr/local/lib/perl5/5.20/mach/CORE/inline.h:265: error: expected ')' before ',' token /usr/local/lib/perl5/5.20/mach/CORE/inline.h:265: error: void value not ignored as it ought to be IMAP.xs: At top level: IMAP.xs:218: warning: initialization from incompatible pointer type IMAP.xs:219: warning: initialization from incompatible pointer type IMAP.xs:220: warning: initialization from incompatible pointer type *** [IMAP.o] Error code 1 Stop in /usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl/imap. *** [all] Error code 1 Stop in /usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl. *** [all] Error code 1 Stop in /usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17. *** [do-build] Error code 1 Stop in /usr/ports/mail/cyrus-imapd24. *** [stage] Error code 1 Stop in /usr/ports/mail/cyrus-imapd24. root@nuos-lab:/usr/ports/mail/cyrus-imapd24 # uname -a FreeBSD nuos-lab.naruto.ccsys.com 9.3-RELEASE FreeBSD 9.3-RELEASE #0 r269946: Wed Aug 13 12:53:13 EDT 2014 r...@naruto.ccsys.com:/usr/obj/usr/src/sys/NUOS amd64 root@nuos-lab:/usr/ports/mail/cyrus-imapd24 # cat /etc/make.conf CPUTYPE?=core2 DEFAULT_VERSIONS= perl5=5.20 php=55 WITH_PGSQL_VER=93 WITH_MYSQL_VER=56 WITH_NEW_XORG=yes QT4_OPTIONS=CUPS ___ 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: perl related error in mail/cyrus-imapd24
On 09/11/14 16:29, Hajimu UMEMOTO wrote:
Hi,
On Thu, 11 Sep 2014 16:10:49 +
Chad J. Milios mil...@ccsys.com said:
milios I'm gonna look into this further today but maybe one of you can make
milios quicker sense of this. I just got this error while building
milios cyrus-imapd24-2.4.17_8. Port options are default but my make.conf sets
milios perl to 5.20. My make.conf is included below the error. Many thanks to
milios anyone that even glances at this error to help. :)
milios
milios ### Making all in
/usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl
milios ### Making all in
milios /usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl/imap
milios Checking if your kit is complete...
milios Looks good
milios Generating a Unix-style Makefile
milios Writing Makefile for Cyrus::IMAP
milios Writing MYMETA.yml and MYMETA.json
milios Smartmatch is experimental at
milios /usr/local/lib/perl5/5.20/BSDPAN/ExtUtils/Packlist.pm line 218.
milios cp IMAP.pm blib/lib/Cyrus/IMAP.pm
milios cp IMAP/Shell.pm blib/lib/Cyrus/IMAP/Shell.pm
milios cp IMAP/IMSP.pm blib/lib/Cyrus/IMAP/IMSP.pm
milios cp IMAP/Admin.pm blib/lib/Cyrus/IMAP/Admin.pm
milios Running Mkbootstrap for Cyrus::IMAP ()
milios chmod 644 IMAP.bs
milios /usr/local/bin/perl5.20.0 /usr/local/lib/perl5/5.20/ExtUtils/xsubpp
milios -typemap /usr/local/lib/perl5/5.20/ExtUtils/typemap -typemap typemap
milios IMAP.xs IMAP.xsc mv IMAP.xsc IMAP.c
milios cc -c -I../../lib -I../.. -I../../com_err/et -I/usr/local/include
milios -I/usr/include -DAPPLLIB_EXP=/usr/local/lib/perl5/5.20/BSDPAN
milios -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -DDEBUGGING -fno-strict-aliasing
milios -pipe -fstack-protector -I/usr/local/include -g-DVERSION=\1.00\
milios -DXS_VERSION=\1.00\ -DPIC -fPIC
milios -I/usr/local/lib/perl5/5.20/mach/CORE -DPERL_POLLUTE IMAP.c
milios In file included from /usr/local/lib/perl5/5.20/mach/CORE/perl.h:5152,
milios from IMAP.xs:51:
milios /usr/local/lib/perl5/5.20/mach/CORE/inline.h: In function
milios 'S_append_utf8_from_native_byte':
milios /usr/local/lib/perl5/5.20/mach/CORE/inline.h:264: error: expected ')'
milios before ',' token
milios /usr/local/lib/perl5/5.20/mach/CORE/inline.h:264: error: void value
milios not ignored as it ought to be
milios /usr/local/lib/perl5/5.20/mach/CORE/inline.h:265: error: expected ')'
milios before ',' token
milios /usr/local/lib/perl5/5.20/mach/CORE/inline.h:265: error: void value
milios not ignored as it ought to be
milios IMAP.xs: At top level:
milios IMAP.xs:218: warning: initialization from incompatible pointer type
milios IMAP.xs:219: warning: initialization from incompatible pointer type
milios IMAP.xs:220: warning: initialization from incompatible pointer type
milios *** [IMAP.o] Error code 1
milios Stop in /usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl/imap.
milios *** [all] Error code 1
milios Stop in /usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl.
milios *** [all] Error code 1
milios Stop in /usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17.
milios *** [do-build] Error code 1
milios Stop in /usr/ports/mail/cyrus-imapd24.
milios *** [stage] Error code 1
milios Stop in /usr/ports/mail/cyrus-imapd24.
milios root@nuos-lab:/usr/ports/mail/cyrus-imapd24 # uname -a
milios FreeBSD nuos-lab.naruto.ccsys.com 9.3-RELEASE FreeBSD 9.3-RELEASE #0
milios r269946: Wed Aug 13 12:53:13 EDT 2014
milios r...@naruto.ccsys.com:/usr/obj/usr/src/sys/NUOS amd64
milios root@nuos-lab:/usr/ports/mail/cyrus-imapd24 # cat /etc/make.conf
milios CPUTYPE?=core2
milios DEFAULT_VERSIONS= perl5=5.20 php=55
milios WITH_PGSQL_VER=93
milios WITH_MYSQL_VER=56
milios WITH_NEW_XORG=yes
milios QT4_OPTIONS=CUPS
I've just tried to reproduce the problem on my 9.3-STABLE with
perl5-5.20.0_3. But, I cannot reproduce it, here.
Sincerely,
--
Hajimu UMEMOTO
u...@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.mahoroba.org/~ume/
Thanks for the quick feedback! The fact it's not happening for you is
valuable information in and of itself. I'm building this in a jail. I'm
going to try eliminating each of the differences between us one by one.
I have non-default perl options as well. It just dawned on me I should
have included those. I marked the non-defaults with ** Here they are:
root@nuos-lab:/usr/ports/lang/perl5.20 # make showconfig
=== The following configuration options are available for perl5-5.20.0_3:
**DEBUG=on: Build with debugging support
**GDBM=on: GDBM_File extension
**MULTIPLICITY=on: Use multiplicity
PERL_64BITINT=on: Use 64 bit integers (on i386)
PTHREAD=on: Build with -pthread
**SITECUSTOMIZE=on: Run-time customization of @INC
Exclusive OPTIONS: you can only select none or one of them
THREADS=on: Build threaded perl
PERL_MALLOC=off: Use Perl malloc
=== Use 'make config' to modify these settings
root@nuos-lab:/usr/ports # svn info
Path: .
Working Copy Root Path: /usr/ports
URL: https://svn0.us-east.freebsd.org
perl5.20 problem FOUND but not fixed. Was: perl related error in mail/cyrus-imapd24
On 09/11/14 16:51, Chad J. Milios wrote:
On 09/11/14 16:29, Hajimu UMEMOTO wrote:
Hi,
On Thu, 11 Sep 2014 16:10:49 +
Chad J. Milios mil...@ccsys.com said:
milios I'm gonna look into this further today but maybe one of you
can make
milios quicker sense of this. I just got this error while building
milios cyrus-imapd24-2.4.17_8. Port options are default but my
make.conf sets
milios perl to 5.20. My make.conf is included below the error. Many
thanks to
milios anyone that even glances at this error to help. :)
milios
milios ### Making all in
/usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl
milios ### Making all in
milios /usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl/imap
milios Checking if your kit is complete...
milios Looks good
milios Generating a Unix-style Makefile
milios Writing Makefile for Cyrus::IMAP
milios Writing MYMETA.yml and MYMETA.json
milios Smartmatch is experimental at
milios /usr/local/lib/perl5/5.20/BSDPAN/ExtUtils/Packlist.pm line 218.
milios cp IMAP.pm blib/lib/Cyrus/IMAP.pm
milios cp IMAP/Shell.pm blib/lib/Cyrus/IMAP/Shell.pm
milios cp IMAP/IMSP.pm blib/lib/Cyrus/IMAP/IMSP.pm
milios cp IMAP/Admin.pm blib/lib/Cyrus/IMAP/Admin.pm
milios Running Mkbootstrap for Cyrus::IMAP ()
milios chmod 644 IMAP.bs
milios /usr/local/bin/perl5.20.0
/usr/local/lib/perl5/5.20/ExtUtils/xsubpp
milios -typemap /usr/local/lib/perl5/5.20/ExtUtils/typemap -typemap
typemap
milios IMAP.xs IMAP.xsc mv IMAP.xsc IMAP.c
milios cc -c -I../../lib -I../.. -I../../com_err/et
-I/usr/local/include
milios -I/usr/include -DAPPLLIB_EXP=/usr/local/lib/perl5/5.20/BSDPAN
milios -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -DDEBUGGING
-fno-strict-aliasing
milios -pipe -fstack-protector -I/usr/local/include -g
-DVERSION=\1.00\
milios -DXS_VERSION=\1.00\ -DPIC -fPIC
milios -I/usr/local/lib/perl5/5.20/mach/CORE -DPERL_POLLUTE IMAP.c
milios In file included from
/usr/local/lib/perl5/5.20/mach/CORE/perl.h:5152,
milios from IMAP.xs:51:
milios /usr/local/lib/perl5/5.20/mach/CORE/inline.h: In function
milios 'S_append_utf8_from_native_byte':
milios /usr/local/lib/perl5/5.20/mach/CORE/inline.h:264: error:
expected ')'
milios before ',' token
milios /usr/local/lib/perl5/5.20/mach/CORE/inline.h:264: error: void
value
milios not ignored as it ought to be
milios /usr/local/lib/perl5/5.20/mach/CORE/inline.h:265: error:
expected ')'
milios before ',' token
milios /usr/local/lib/perl5/5.20/mach/CORE/inline.h:265: error: void
value
milios not ignored as it ought to be
milios IMAP.xs: At top level:
milios IMAP.xs:218: warning: initialization from incompatible
pointer type
milios IMAP.xs:219: warning: initialization from incompatible
pointer type
milios IMAP.xs:220: warning: initialization from incompatible
pointer type
milios *** [IMAP.o] Error code 1
milios Stop in
/usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl/imap.
milios *** [all] Error code 1
milios Stop in
/usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17/perl.
milios *** [all] Error code 1
milios Stop in /usr/ports/mail/cyrus-imapd24/work/cyrus-imapd-2.4.17.
milios *** [do-build] Error code 1
milios Stop in /usr/ports/mail/cyrus-imapd24.
milios *** [stage] Error code 1
milios Stop in /usr/ports/mail/cyrus-imapd24.
milios root@nuos-lab:/usr/ports/mail/cyrus-imapd24 # uname -a
milios FreeBSD nuos-lab.naruto.ccsys.com 9.3-RELEASE FreeBSD
9.3-RELEASE #0
milios r269946: Wed Aug 13 12:53:13 EDT 2014
milios r...@naruto.ccsys.com:/usr/obj/usr/src/sys/NUOS amd64
milios root@nuos-lab:/usr/ports/mail/cyrus-imapd24 # cat /etc/make.conf
milios CPUTYPE?=core2
milios DEFAULT_VERSIONS= perl5=5.20 php=55
milios WITH_PGSQL_VER=93
milios WITH_MYSQL_VER=56
milios WITH_NEW_XORG=yes
milios QT4_OPTIONS=CUPS
I've just tried to reproduce the problem on my 9.3-STABLE with
perl5-5.20.0_3. But, I cannot reproduce it, here.
Sincerely,
--
Hajimu UMEMOTO
u...@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.mahoroba.org/~ume/
Thanks for the quick feedback! The fact it's not happening for you is
valuable information in and of itself. I'm building this in a jail.
I'm going to try eliminating each of the differences between us one
by one. I have non-default perl options as well. It just dawned on me
I should have included those. I marked the non-defaults with ** Here
they are:
root@nuos-lab:/usr/ports/lang/perl5.20 # make showconfig
=== The following configuration options are available for
perl5-5.20.0_3:
**DEBUG=on: Build with debugging support
**GDBM=on: GDBM_File extension
**MULTIPLICITY=on: Use multiplicity
PERL_64BITINT=on: Use 64 bit integers (on i386)
PTHREAD=on: Build with -pthread
**SITECUSTOMIZE=on: Run-time customization of @INC
Exclusive OPTIONS: you can only select none or one of them
THREADS=on: Build threaded perl
PERL_MALLOC=off: Use Perl malloc
=== Use 'make config' to modify these settings
root@nuos-lab:/usr/ports # svn info
Path
net-mgmt/net-snmp build error on 9.2
I have pkg-1.2.7_3 installed and unused (FYI, I need pkg_tools support on these systems and am not prepared to make the transition to pkgng until sometime between now and the pkg_tools EOL). pkg-1.2.7_3 was pulled in as a dependency for net-mgmt/net-snmp and pkg has no other dependents on my system. Is there something special I need to do to get this to work? There is a comment in the makefile that pkg-1.2 cannot handle this dependency well. So then why is the dependency placed on pkg and not pkg-devel? Thank you for any help you have to offer. ... building 'netsnmp.client_intf' extension creating build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7 creating build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp cc -DNDEBUG -O2 -pipe -march=core2 -I/usr/local/include -fno-strict-aliasing -fPIC -I/usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2/include -I/usr/local/include/python2.7 -c netsnmp/client_intf.c -o build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp/client_intf.o cc -shared -pthread -Wl,-rpath,/usr/lib:/usr/local/lib -O2 -pipe -march=core2 -I/usr/local/include -fno-strict-aliasing build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp/client_intf.o -L/usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2/agent/.libs -L/usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2/snmplib/.libs -lm -lkvm -ldevstat -lpkg -lnetsnmp -lcrypto -lelf -lssp_nonshared -o build/lib.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp/client_intf.so /usr/bin/ld: cannot find -lpkg error: command 'cc' failed with exit status 1 *** [pythonmodules] Error code 1 Stop in /usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2. *** [do-build] Error code 1 Stop in /usr/ports/net-mgmt/net-snmp. ___ 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: net-mgmt/net-snmp build error on 9.2
root@nuos-lab:/usr/ports/net-mgmt/net-snmp # more /etc/make.conf CPUTYPE?=core2 NO_WARNING_PKG_INSTALL_EOL=yes DEFAULT_VERSIONS= perl5=5.18 php=55 APACHE_PORT=www/apache24 WITH_BDB_VER=48 WITH_PGSQL_VER=93 WITH_MYSQL_VER=56 WITH_NEW_XORG=yes root@nuos-lab:/usr/ports/net-mgmt/net-snmp # grep PORTREV Makefile PORTREVISION= 9 On 6/13/2014 10:12 AM, Ryan Steinmetz wrote: What's the PORTREVISION of your net-snmp port? Do you have anything in /etc/make.conf? -r On (06/13/14 08:50), Chad J. Milios wrote: I have pkg-1.2.7_3 installed and unused (FYI, I need pkg_tools support on these systems and am not prepared to make the transition to pkgng until sometime between now and the pkg_tools EOL). pkg-1.2.7_3 was pulled in as a dependency for net-mgmt/net-snmp and pkg has no other dependents on my system. Is there something special I need to do to get this to work? There is a comment in the makefile that pkg-1.2 cannot handle this dependency well. So then why is the dependency placed on pkg and not pkg-devel? Thank you for any help you have to offer. ... building 'netsnmp.client_intf' extension creating build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7 creating build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp cc -DNDEBUG -O2 -pipe -march=core2 -I/usr/local/include -fno-strict-aliasing -fPIC -I/usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2/include -I/usr/local/include/python2.7 -c netsnmp/client_intf.c -o build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp/client_intf.o cc -shared -pthread -Wl,-rpath,/usr/lib:/usr/local/lib -O2 -pipe -march=core2 -I/usr/local/include -fno-strict-aliasing build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp/client_intf.o -L/usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2/agent/.libs -L/usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2/snmplib/.libs -lm -lkvm -ldevstat -lpkg -lnetsnmp -lcrypto -lelf -lssp_nonshared -o build/lib.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp/client_intf.so /usr/bin/ld: cannot find -lpkg error: command 'cc' failed with exit status 1 *** [pythonmodules] Error code 1 Stop in /usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2. *** [do-build] Error code 1 Stop in /usr/ports/net-mgmt/net-snmp. ___ 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: net-mgmt/net-snmp build error on 9.2
root@nuos-lab:/usr/ports/net-mgmt/net-snmp # ll /usr/local/lib/libpkg* -r--r--r-- 1 root wheel 2010402 Jun 13 03:47 /usr/local/lib/libpkg.a lrwxr-xr-x 1 root wheel 11 Jun 13 03:47 /usr/local/lib/libpkg.so@ - libpkg.so.1 -r--r--r-- 1 root wheel 1281472 Jun 13 03:47 /usr/local/lib/libpkg.so.1 On 6/13/2014 11:29 AM, Ryan Steinmetz wrote: Do you have a /usr/local/lib/libpkg*? -r On (06/13/14 11:24), Chad J. Milios wrote: root@nuos-lab:/usr/ports/net-mgmt/net-snmp # more /etc/make.conf CPUTYPE?=core2 NO_WARNING_PKG_INSTALL_EOL=yes DEFAULT_VERSIONS= perl5=5.18 php=55 APACHE_PORT=www/apache24 WITH_BDB_VER=48 WITH_PGSQL_VER=93 WITH_MYSQL_VER=56 WITH_NEW_XORG=yes root@nuos-lab:/usr/ports/net-mgmt/net-snmp # grep PORTREV Makefile PORTREVISION= 9 On 6/13/2014 10:12 AM, Ryan Steinmetz wrote: What's the PORTREVISION of your net-snmp port? Do you have anything in /etc/make.conf? -r On (06/13/14 08:50), Chad J. Milios wrote: I have pkg-1.2.7_3 installed and unused (FYI, I need pkg_tools support on these systems and am not prepared to make the transition to pkgng until sometime between now and the pkg_tools EOL). pkg-1.2.7_3 was pulled in as a dependency for net-mgmt/net-snmp and pkg has no other dependents on my system. Is there something special I need to do to get this to work? There is a comment in the makefile that pkg-1.2 cannot handle this dependency well. So then why is the dependency placed on pkg and not pkg-devel? Thank you for any help you have to offer. ... building 'netsnmp.client_intf' extension creating build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7 creating build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp cc -DNDEBUG -O2 -pipe -march=core2 -I/usr/local/include -fno-strict-aliasing -fPIC -I/usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2/include -I/usr/local/include/python2.7 -c netsnmp/client_intf.c -o build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp/client_intf.o cc -shared -pthread -Wl,-rpath,/usr/lib:/usr/local/lib -O2 -pipe -march=core2 -I/usr/local/include -fno-strict-aliasing build/temp.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp/client_intf.o -L/usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2/agent/.libs -L/usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2/snmplib/.libs -lm -lkvm -ldevstat -lpkg -lnetsnmp -lcrypto -lelf -lssp_nonshared -o build/lib.freebsd-9.2-RELEASE-p3-amd64-2.7/netsnmp/client_intf.so /usr/bin/ld: cannot find -lpkg error: command 'cc' failed with exit status 1 *** [pythonmodules] Error code 1 Stop in /usr/ports/net-mgmt/net-snmp/work/net-snmp-5.7.2. *** [do-build] Error code 1 Stop in /usr/ports/net-mgmt/net-snmp. ___ 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: reason 23 why we've moved to linux
On Mar 22, 2014, at 2:44 PM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 03/22/14 14:00, CyberLeo Kitsana wrote: On 03/22/2014 01:57 PM, Fernando Apesteguía wrote: On Sat, Mar 22, 2014 at 7:50 PM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 03/22/14 11:12, Randy Bush wrote: snip At least testing branches would be appreciated. Something like ivoras@ suggested two years ago? http://lists.freebsd.org/pipermail/freebsd-ports/2010-March/060296.html Something like this? http://svnweb.freebsd.org/ports/branches/2014Q1/ No, not like that. A continuously updated moving branch one step down in experimentation. -Nathan I believe it is indeed what you are looking for [in spirit and in theory at least], hence the branch description: This is a stable branch which will be maintained for 3 months... and various commit descriptions marked MFH i.e. merged from head ranging from 3 months to 3 days ago. Now, whether or not this branch lives up to it's intent is another story all together. That part, I couldn't say because... I, for one, admit to just now learning of this branch's existence. Then again, I never went looking for such a thing since, despite maintaining the deployment of 1300 ports on 130 servers [from a seat on a golf cart during the trips between the front and back nine], I so very seldom stumble upon a failure in ports HEAD that isn't fixed within mere moments or that I can't conveniently back-burner and have solved for me over the course of a day by a quick holler to the helpful and friendly folk on freebsd-ports@, but I guess that's just me. FWIW, I only use 9.2 in production and I do share your underlying sentiment that 9.2 should still be the release marked Production and 10.0 should have been marked New Technology at least until 10.1. I think I recall the issue that triggered this long and windy thread was clang related. At least FreeBSD has notoriously thorough and long-lived legacy support. FWIW, in my job I still use the old pkg_ tools, don't need portmaster, poudriere or any of that young punk noise, just the base tools with an occasional dash of svn. I've never felt an uncomfortable stampede of masses forcing my grumpy old self onto newer and better tech before I was good and ready for it, like happens to me while involved with many of the various types of Linix deployments I maintain, though the fear of such a thing happening to FreeBSD has always been real, what with the rapid pace of its development happening these days along with some people's ever-present nagging to keep up with the Linuxes regarding this or that latest shiny red button. FWIW, and I believe it's worth a lot, on the two VM's I fiddle with 10.x on, I've found all of the new tools to be relatively easy to learn, well engineered, well maintained and [for better or worse] rapidly evolving, only not quite as well tested as I might like, and on that last point I can concede that I understand the OP's pain. I, for one, would like to thank all of the devs at FreeBSD for creating and maintaining the smoothest, most flexible and overall best operating system I've ever had the pleasure of working with. I am very much looking forward to deploying 10.1 on almost every one of the production systems I maintain and I'm confident that when 10.x is granted that .1 badge by release engineering that I will confidently and smoothly be able to. I can't imagine where I'd be in a rigid world of only the fractured Linux fiefdoms, oligarchies and hipster drum-circles. Probably dead under a bridge with a needle in my arm, a gun in my mouth, a noose around my neck and an empty bottle of pills laying beside me. ___ 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: reason 23 why we've moved to linux
On Mar 22, 2014, at 5:40 PM, Randy Bush ra...@psg.com wrote: strange. Whenever I come in touch with Linux, I have the feeling that the people better would have kept Windows on their machine. +1, liked, upvoted, favorited, pinned, retweeted the first time i logged on to a linux system, i said `ls`, it came out in color, and i walked away. Wait, what? Are you saying that like it's a good or a bad thing? i have been a freebsd lover for a couple of decades, and 4.3 before that. but in the last couple of years it has become really painful. and .bashrc has helped me not have broken fingers on linux, and the bottom line is a *lot* less pain. Bash makes me want to do its namesake to my own skull against a concrete wall. at least once a month, i have to do port security updates on over a dozen freebsd systems. it takes most of a day if i am lucky. It's your job right? I presume you get paid for it and there was a reason you or somebody chose FreeBSD on those systems. the linux systems update automagically and send me email telling me what they did. Oh, so you've never been burned by hippy magic? In that case I have some beans I'd like to sell you that will fix all of your problems and some powder that goes up your nose that will fulfill your every desire. i value my time. So much so that you seem to feel that bitching is a better way to spend it than helping would be. Lawlz. if i did not value freebsd, i would just walk away saying nothing. but the community seems to be in some sort of fantasy that things are OK and nirvana is just around the corner. linux has matured, believe it or not. freebsd, ports in particular, has rotted. and folk are voting with their feet. Good riddance. I hope you'll let us know how that works out for you. randy Oh randy, I'm only picking on you because of your delivery, in my pursuit of a balanced discussion. I admit to understanding your pain and appreciating your valid, practical opinion and observant perspective. I, the folk at FreeBSD and their supporters all appreciate your input, I'm certain. However I, for one, am not in a fantasy and I know the nirvana we all seek is not just a leisurely stroll around the nearest corner. It will take the hard work and perseverance of you, I and many of these far greater minds around us. Perhaps I'm just drunk off the koolaid and you're right to be headed for the lifeboats but I feel right at home and in good hands with the team and community here at FreeBSD. -Chad ___ 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: Listing of all available options in ports tree for use in make.conf /ports.conf (WITHOUT_ , WITH_ as well as OPTIONS_SET /UNSET)
On 3/4/2014 9:40 AM, Thierry Thomas wrote: Le mar 4 mar 14 à 15:05:51 +0100, Jakub Lach jakub_l...@mailplus.pl écrivait : Thanks for reply! IMHO, port knobs really should be centrally tracked/standardized. When one would like to set some options globally, it gets really ugly really fast e.g. It used to be in /usr/ports/KNOBS but it was removed some days ago. Anyway, it's still available in svn, and most of the knobs are described in /usr/ports/Mk/bsd.options.desc.mk . from within a port's directory, make showconfig will show you the current options set and make __MAKE_CONF=/dev/null PORT_DBDIR=/var/empty showconfig will show you the defaults. Hope this is helpful to you ___ 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: dns/djbdns [do-package] Error code 1
On Mar 3, 2014, at 2:16 AM, Baptiste Daroussin b...@freebsd.org wrote: On Sun, Mar 02, 2014 at 07:53:31PM -0800, David Thiel wrote: On 02/27, Chad J. Milios wrote: root@kakashi:~ # dnscache-conf dnscache dnslog /var/service/dnscache dnscache-conf: fatal: unable to switch to /usr/ports/dns/djbdns/work/stage/usr/local: file does not exist root@kakashi:~ # strings `which dnscache-conf` | grep stage /usr/ports/dns/djbdns/work/stage/usr/local HOWEVER the software works properly ONCE it manages to get installed by the normal `make clean install` method (where i have to try about 15 times with my fingers crossed and by the grace of God it works one of the times) and strings reports no 'stage' anywhere in dnscache-conf Bapt figured it out. The it target included the install target, making prog the more appropriate build target. I'm still rather confused as to why this made the issues timing-sensitive (and apparently only in some environments), but it should work now. Similar issues may be affecting other djb ports; I'll investigate that this week. I have been able to reproduce this issue everywhere, sorry it was totally my fault as with DEVELOPER=yes in my make.conf it was showing the problem during the qa phase which somehow I haven't seen the first time when I staged it. My bad, I deserve my pointyhat for that one. I have had a look at sysutils/daemontools and it is safe in that area, in fact given how most of djb's Makefile are written 'it' should be the right target, djbdns seems a bit special here. Sorry about the initial breakage regards, Bapt t'sall good homie. Thank you for all your work on FreeBSD ___ 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: dns/djbdns [do-package] Error code 1
setting MAKE_JOBS_UNSAFE didn't do it for me. furthermore, i have more peculiarities to report: my testing earlier, (where i got the build/package/install to succeed by doing `make clean make sleep 1 make package`) resulted in quietly installing a borked program. dnscache-conf then yells as follows: root@kakashi:~ # dnscache-conf dnscache dnslog /var/service/dnscache dnscache-conf: fatal: unable to switch to /usr/ports/dns/djbdns/work/stage/usr/local: file does not exist root@kakashi:~ # strings `which dnscache-conf` | grep stage /usr/ports/dns/djbdns/work/stage/usr/local HOWEVER the software works properly ONCE it manages to get installed by the normal `make clean install` method (where i have to try about 15 times with my fingers crossed and by the grace of God it works one of the times) and strings reports no 'stage' anywhere in dnscache-conf Let me know if you have anything else you'd like me to try for you. 9.2-RELEASE-p3/amd64 on ZFS here. -Chad p.s. i tried `make -DNO_STAGE install` about 20 times also and none of them worked, tar always complained about missing man pages On 2/19/2014 2:04 PM, Chad J. Milios wrote: Oh yeah, I probably should have mentioned I'm on 9.2-RELEASE/amd64 with all ZFS file systems (except tmpfs /tmp). I'll give that a shot and report back, usually woulda been my first stab at it but i too had a feeling that just didnt seem to be applicable in this case. I'll have to try it out tonight, that box is close to pegged most of the day, I was doing the experimenting at 3:30 am this morning. On 2/19/2014 1:50 PM, David Thiel wrote: Interesting, I can't seem to replicate it here. It doesn't seem like MAKE_JOBS_UNSAFE would apply, but perhaps try that? On 02/19, Chad J. Milios wrote: there seems to be a timing issue. can anyone else please confirm this problem is happening? I haven't gone ahead and tried any non-default values of vfs.timestamp_precision. make package fails 26/30 times make sleep 1 make package succeeds 50/50 times Thanks in advance. ___ 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Stop in ports/lang/gcc47: Shared object libfl.so.2 not found, required by ar
On 2/25/2014 2:18 PM, Tijl Coosemans wrote: On Mon, 24 Feb 2014 23:41:22 -0500 Chad J. Milios wrote: I've been getting this same error for a couple days now in ports. 9.2-RELEASE-p3/amd64. Any insight into what I'm doing wrong? My gut is telling me this is my fault though I'm at a loss for how. Try to rebuild devel/binutils. There was a short window in which textproc/flex installed libfl.so.2 and it looks like you rebuilt devel/binutils in that window. That is exactly what fixed the problem. Thank you ___ 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
Stop in ports/lang/gcc47: Shared object libfl.so.2 not found, required by ar
I've been getting this same error for a couple days now in ports. 9.2-RELEASE-p3/amd64. Any insight into what I'm doing wrong? My gut is telling me this is my fault though I'm at a loss for how. if [ x-fpic != x ]; then \ cc -c -DHAVE_CONFIG_H -g -fkeep-inline-functions -I. -I.././../gcc-4.7-20140215/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic -fpic .././../gcc-4.7-20140215/libiberty/strverscmp.c -o pic/strverscmp.o; \ else true; fi cc -c -DHAVE_CONFIG_H -g -fkeep-inline-functions -I. -I.././../gcc-4.7-20140215/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic .././../gcc-4.7-20140215/libiberty/strverscmp.c -o strverscmp.o rm -f ./libiberty.a pic/./libiberty.a /usr/local/bin/ar rc ./libiberty.a \ ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o ./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o ./dyn-string.o ./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatformat.o ./fnmatch.o ./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o ./obstack.o ./partition.o ./pexecute.o ./physmem.o ./pex-common.o ./pex-one.o ./pex-unix.o ./safe-ctype.o ./simple-object.o ./simple-object-coff.o ./simple-object-elf.o ./simple-object-mach-o.o ./sort.o ./spaces.o ./splay-tree.o ./stack-limit.o ./strerror.o ./strsignal.o ./timeval-utils.o ./unlink-if-ordinary.o ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o ./xstrdup.o ./xstrerror.o ./xstrndup.o ./mempcpy.o ./strverscmp.o Shared object libfl.so.2 not found, required by ar gmake[3]: *** [libiberty.a] Error 1 gmake[3]: Leaving directory `/usr/ports/lang/gcc47/work/build/libiberty' gmake[2]: *** [all-stage1-libiberty] Error 2 gmake[2]: Leaving directory `/usr/ports/lang/gcc47/work/build' gmake[1]: *** [stage1-bubble] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc47/work/build' gmake: *** [bootstrap-lean] Error 2 *** [do-build] Error code 1 Stop in /usr/ports/lang/gcc47. *** [build] Error code 1 Stop in /usr/ports/lang/gcc47. ___ 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: misc/186883: last update of docbook broke building kdelibs
On 2/19/2014 8:37 AM, Sergio de Almeida Lenzi wrote:
Em Qua, 2014-02-19 às 13:58 +0100, Antoine Brodin escreveu:
Please try patch below
Kdelibs expects to find docbookx.dtd in
share/xml/docbook/${DOCBOOKXML_CURRENTDTD_VERSION} , not in a subdir
Index: textproc/docbook-xml/Makefile
===
--- textproc/docbook-xml/Makefile (revision 345083)
+++ textproc/docbook-xml/Makefile (working copy)
@@ -3,7 +3,7 @@
PORTNAME= docbook-xml
PORTVERSION= 4.2
-PORTREVISION= 3
+PORTREVISION= 4
MASTER_SITES= http://www.docbook.org/xml/${PORTVERSION}/ \
http://www.oasis-open.org/committees/docbook/xml/${PORTVERSION}/
@@ -13,6 +13,7 @@
NO_ISOCAT= yes
XML_DTD= yes
HAS_MANUAL_CATALOG_FILE= yes
+NO_DTD_SUBDIR= yes
DTD_NAME?= ${PORTNAME:S/-xml//}
YES!!!
it fix for me here...
I think we can close the PR
Waiting for more tests (9.X, 8.X)
For me it is done...
Thanks
That worked perfectly for me on 9.2-RELEASE as well. I was going to say,
Can we get kdelibs4 to find it in the dtd directory instead? but I see
the way docbook-xml is now installing files after the above patch
matches the way it was doing it a few days ago so this seems acceptable
to me.
___
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
dns/djbdns [do-package] Error code 1
there seems to be a timing issue. can anyone else please confirm this
problem is happening? I haven't gone ahead and tried any non-default
values of vfs.timestamp_precision.
make package
fails 26/30 times
make sleep 1 make package
succeeds 50/50 times
Thanks in advance.
here is the full output of a failed run:
=== Found saved configuration for djbdns-1.05_14
=== Fetching all distfiles required by djbdns-1.05_17,1 for building
=== Extracting for djbdns-1.05_17,1
= SHA256 Checksum OK for djbdns-1.05.tar.gz.
= SHA256 Checksum OK for djbdns-1.05-man-20031023.tar.gz.
=== Patching for djbdns-1.05_17,1
=== Applying FreeBSD patches for djbdns-1.05_17,1
=== Configuring for djbdns-1.05_17,1
=== Building for djbdns-1.05_17,1
cat warn-auto.sh dnstracesort.sh | sed s}HOME}`head -1 conf-home`}g
dnstracesort
cat warn-auto.sh rts.sh | sed s}HOME}`head -1 conf-home`}g rts
( cat warn-auto.sh; echo 'main=$1; shift'; echo exec `head -1
conf-ld` '-o $main $main.o ${1+$@}' ) load
( cat warn-auto.sh; echo exec `head -1 conf-cc` '-c ${1+$@}' )
compile
chmod 755 dnstracesort
chmod 755 compile
chmod 755 load
chmod 755 rts
( cat warn-auto.sh; echo CC=\'`head -1 conf-cc`\'; echo LD=\'`head -1
conf-ld`\'; cat find-systype.sh; ) | sh systype
cat warn-auto.sh choose.sh | sed s}HOME}`head -1 conf-home`}g choose
./compile alloc.c
./compile alloc_re.c
chmod 755 choose
./compile auto-str.c
auto-str.c:8: warning: conflicting types for built-in function 'puts'
./compile axfrdns-conf.c
./compile buffer.c
./compile buffer_1.c
./compile buffer_2.c
./compile buffer_copy.c
./compile buffer_get.c
./compile buffer_put.c
./compile buffer_read.c
./compile buffer_write.c
./compile byte_chr.c
./compile byte_copy.c
./compile byte_cr.c
./compile byte_diff.c
./compile byte_zero.c
./compile case_diffb.c
./compile case_diffs.c
./compile case_lowerb.c
./compile chkshsgr.c
./compile droproot.c
./compile env.c
./compile error.c
./compile error_str.c
./compile fmt_ulong.c
./compile generic-conf.c
./compile getln.c
./compile getln2.c
./compile hier.c
./compile install.c
./compile instcheck.c
./compile ip4_fmt.c
./compile ip4_scan.c
./compile ndelay_off.c
./compile ndelay_on.c
./compile okclient.c
./compile open_read.c
./compile open_trunc.c
./compile openreadclose.c
./compile pickdns-conf.c
./compile qlog.c
./compile rbldns-conf.c
./compile readclose.c
./compile scan_ulong.c
./compile seek_set.c
./compile sgetopt.c
./compile socket_accept.c
./compile socket_bind.c
./compile socket_conn.c
./compile socket_listen.c
./compile socket_recv.c
./compile socket_send.c
./compile socket_tcp.c
./compile socket_udp.c
./compile str_chr.c
./compile str_diff.c
./compile str_len.c
./compile str_rchr.c
./compile str_start.c
./compile stralloc_cat.c
./compile stralloc_catb.c
./compile stralloc_cats.c
./compile stralloc_copy.c
./compile stralloc_eady.c
./compile stralloc_num.c
./compile stralloc_opyb.c
./compile stralloc_opys.c
./compile stralloc_pend.c
./compile strerr_die.c
./compile strerr_sys.c
./compile subgetopt.c
./compile tinydns-conf.c
./compile uint16_pack.c
./compile uint16_unpack.c
./compile utime.c
./compile walldns-conf.c
( ( ./compile trylsock.c ./load trylsock -lsocket -lnsl ) /dev/null
21 echo -lsocket -lnsl || exit 0 ) socket.lib
( ( ./compile tryulong32.c ./load tryulong32 ./tryulong32 )
/dev/null 21 cat uint32.h2 || cat uint32.h1 ) uint32.h
./choose c trydrent direntry.h1 direntry.h2 direntry.h
rm -f trylsock.o trylsock
./choose clr trypoll iopause.h1 iopause.h2 iopause.h
./choose c trysysel select.h1 select.h2 select.h
./choose clr tryulong64 uint64.h1 uint64.h2 uint64.h
rm -f tryulong32.o tryulong32
( case `cat systype` in sunos-5.*) cat hasdevtcp.h2 ;; *) cat
hasdevtcp.h1 ;; esac ) hasdevtcp.h
( cat warn-auto.sh; echo 'main=$1; shift'; echo 'rm -f $main';
echo 'ar cr $main ${1+$@}'; case `cat systype` in sunos-5.*) ;;
unix_sv*) ;; irix64-*) ;; irix-*) ;; dgux-*) ;; hp-ux-*) ;; sco*)
;; *) echo 'ranlib $main' ;; esac ) makelib
./load chkshsgr
chmod 755 makelib
./compile cdb.c
./compile cdb_hash.c
./compile cdb_make.c
./compile rbldns-data.c
./compile uint32_pack.c
./compile uint32_unpack.c
./makelib alloc.a alloc.o alloc_re.o getln.o getln2.o stralloc_cat.o
stralloc_catb.o stralloc_cats.o stralloc_copy.o stralloc_eady.o
stralloc_num.o stralloc_opyb.o stralloc_opys.o stralloc_pend.o
./makelib buffer.a buffer.o buffer_1.o buffer_2.o buffer_copy.o
buffer_get.o buffer_put.o strerr_die.o strerr_sys.o
./makelib env.a env.o
./makelib getopt.a sgetopt.o subgetopt.o
./makelib unix.a buffer_read.o buffer_write.o error.o error_str.o
ndelay_off.o ndelay_on.o open_read.o open_trunc.o openreadclose.o
readclose.o seek_set.o socket_accept.o socket_bind.o socket_conn.o
socket_listen.o socket_recv.o socket_send.o socket_tcp.o socket_udp.o
./chkshsgr || ( cat warn-shsgr; exit 1 )
./choose clr tryshsgr hasshsgr.h1 hasshsgr.h2 hasshsgr.h
./compile axfr-get.c
./compile axfrdns.c
Re: dns/djbdns [do-package] Error code 1
Oh yeah, I probably should have mentioned I'm on 9.2-RELEASE/amd64 with all ZFS file systems (except tmpfs /tmp). I'll give that a shot and report back, usually woulda been my first stab at it but i too had a feeling that just didnt seem to be applicable in this case. I'll have to try it out tonight, that box is close to pegged most of the day, I was doing the experimenting at 3:30 am this morning. On 2/19/2014 1:50 PM, David Thiel wrote: Interesting, I can't seem to replicate it here. It doesn't seem like MAKE_JOBS_UNSAFE would apply, but perhaps try that? On 02/19, Chad J. Milios wrote: there seems to be a timing issue. can anyone else please confirm this problem is happening? I haven't gone ahead and tried any non-default values of vfs.timestamp_precision. make package fails 26/30 times make sleep 1 make package succeeds 50/50 times Thanks in advance. ___ 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
Is it September already? (package tools out of date?)
I am having a problem packaging docbook-xml450-4.5_3 and I imagine there
will be others. I ran through my entire build system two days ago and
know docbook-xml450-4.5 did not have this problem. Is there a workaround
I should be doing or a way we can maintain compatibility with
9.2-RELEASE-p3 systems?
Sorry to be a pest. Yes, I like pkgng in concept, theory, not yet in
practice. I've followed all the controversy regarding pkgng, staging,
clang, et al and I am generally a big advocate for positive change. That
being said, FreeBSD has ALWAYS had a solid backward compatibility track
record. That's what I like about it. I have a toy box running 10.0 but
it's just my toy system. I'm still wrapping my head around all the major
changes and meanwhile I have a fleet of 9.2 servers in production to
maintain. The more trouble I have in maintenance of those the less time
I have to learn about and contribute to the new way of doing things.
Frankly I would have thought we would have marked 10.0 new technology
and maintained the production label on 9.x until 10.1. Running legacy
on my newest production servers just makes me feel old. :(
Kudos to everyone and their hard work at making FreeBSD 10, pkgng and
the ports system great.
=== Cleaning for docbook-xml450-4.5_3
=== Fetching all distfiles required by docbook-xml450-4.5_3 for building
=== Extracting for docbook-xml450-4.5_3
= SHA256 Checksum OK for docbook-xml-4.5.zip.
=== Patching for docbook-xml450-4.5_3
=== Configuring for docbook-xml450-4.5_3
=== Staging for docbook-xml450-4.5_3
=== docbook-xml450-4.5_3 depends on file: /usr/local/bin/xmlcatmgr -
found
=== Generating temporary packing list
cd /usr/ports/textproc/docbook-xml-450/work/docbook-xml-4.5 /bin/sh
-c '(/usr/bin/find -d $0 $2 | /usr/bin/cpio -dumpl $1 /dev/null 21)
/usr/sbin/chown -Rh root:wheel $1 /usr/bin/find -d $0 $2 -type d
-exec chmod 755 $1/{} \; /usr/bin/find -d $0 $2 -type f -exec chmod
444 $1/{} \;' -- .
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/xml/docbook/4.5/dtd
/bin/mv
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/xml/docbook/4.5/dtd/ChangeLog
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/doc/docbook-xml/4.5/ChangeLog
/bin/mv
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/xml/docbook/4.5/dtd/README
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/doc/docbook-xml/4.5/README
/bin/mv
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/xml/docbook/4.5/dtd/ent/README
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/doc/docbook-xml/4.5/ent/README
Compressing man pages (compress-man)
=== Building package for docbook-xml450-4.5_3
Creating package
/usr/ports/textproc/docbook-xml-450/work/docbook-xml450-4.5_3.tbz
Registering depends: xmlcatmgr-2.2.
pkg_create: read_plist: unknown command '@dirrmtry share/xml/docbook'
(package tools out of date?)
pkg_create: read_plist: unknown command '@dirrmtry
share/doc/docbook-xml' (package tools out of date?)
pkg_create: write_plist: unknown command type -1 (share/xml/docbook)
*** [do-package] Error code 1
Stop in /usr/ports/textproc/docbook-xml-450.
___
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: Is it September already? (package tools out of date?)
On 2/18/2014 6:18 PM, Matthias Andree wrote: Am 18.02.2014 21:15, schrieb Chad J. Milios: I am having a problem packaging docbook-xml450-4.5_3 and I imagine there will be others. I ran through my entire build system two days ago and know docbook-xml450-4.5 did not have this problem. Is there a workaround I should be doing or a way we can maintain compatibility with 9.2-RELEASE-p3 systems? Chad, sorry for the trouble. Mathieu Arnold has fixed this a few minutes before I've sent this message, so if you upgrade the ports tree, the docbook packages should build for you again. Thanks for taking the time to report this. Cheers Matthias Ahh, many many thanks to you both! So it was just a glitch? Thank goodness I saw that message and felt like an old man already being put out to pasture! And I can report... GREAT SUCCESS after the ports tree update everything previously mentioned worked flawlessly for me. Much gratitude goes out to everyone working on all the great modernizations being integrated, tested and coming down the pipeline. FreeBSD has always been and still is AMAZINGLY stable and solid in light of its rapid pace of innovation. -Chad ___ 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: last update of docbook broke KDE4
On 2/18/2014 2:13 PM, Sergio de Almeida Lenzi wrote: FreeBSD freebsd10.toontown 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r261076M: Thu Jan 23 21:21:09 BRST 2014 -- The following REQUIRED packages have not been found: * DocBookXML , DocBook XML , http://www.oasis-open.org/docbook/xml/4.2 Required by the KDE help system to process DocBook XML CMake Error at /usr/local/share/cmake/Modules/FeatureSummary.cmake:430 (message): feature_summary() Error: REQUIRED package(s) are missing, aborting CMake run. Call Stack (most recent call first): CMakeLists.txt:397 (feature_summary) -- Configuring incomplete, errors occurred! I have the exact same error on 9.2-RELEASE-p3 as well. Furthermore, root@nuos-lab:~/nuos/bin # pkg_info|grep -i docbook docbook-1.4_2 Meta-port for the different versions of the DocBook DTD docbook-sk-4.1.2_5 XML version of the DocBook DTD version controlled for Scrol docbook-xml-4.2_3 XML version of the DocBook DTD docbook-xml430-4.3_2 DocBook/XML DTD V4.3, designed for technical documentation docbook-xml440-4.4_4 DocBook/XML DTD V4.4, designed for technical documentation docbook-xml450-4.5_3 DocBook/XML DTD V4.5, designed for technical documentation docbook-xsl-1.76.1_2 XSL DocBook stylesheets docbook410-4.1_5V4.1 of the DocBook DTD, designed for technical documentati docbook420-4.2_1V4.2 of the DocBook DTD, designed for technical documentati docbook430-4.3_1DocBook/SGML DTD V4.3, designed for technical documentation docbook440-4.4_3DocBook/SGML DTD V4.4, designed for technical documentation docbook450-4.5_3DocBook/SGML DTD V4.5, designed for technical documentation docbook500-5.0_4DocBook 5.0, designed for technical documentation Should I file a PR or is there a quick fix being worked on? ___ 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
New port: net-p2p/namecoin
I submitted a working port for namecoin-qt and namecoind. Please try it and share any feedback/improvements you have. Let me know how you use it and with what options, please. More info is in the PR and the .shar attached there contains namecoin and namecoin-daemon. http://www.freebsd.org/cgi/query-pr.cgi?pr=185459 Thanks everyone. By the way: namecoin is going to the moon this year. :) If anyone feels like sending a tip I'll use it to keep making FreeBSD even better! (code and/or coin) :) More work needs to be done yet to hook namecoin into resolv.conf and/or your local caching resolver. I'm also planning to make nice rc.d scripts for all the [foo]coin-daemon ports soon so they might behave like actual services should! Any discussion welcomed. NMC: NCtH4BZLWTutaYX5rdKua1WtK1LfZUJ6La BTC: 1HKQbm7nnYjQ61u1XtFV28bPLCgjiGgGvU -- Chad J. Milios Crop Circle Systems, Inc. We do consulting around ZFS, DTrace and BSD along with app development on the MEAN stack (Mongo Express Angular Node) ___ 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
Please commit this fix to a race in the audio/liba52 port
Sorry to be a pest. At the bottom of closed PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183791
There is a working fix that hasn't been committed yet. A target needs to be
added to audio/liba52/Makefile I recommend changing it a little bit though from
the one in the PR, to this:
pre-install:
${FIND} ${WRKSRC} -name Makefile | ${XARGS} ${TOUCH}
___
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: [FIXED] ports/183791: audio/liba52 (liba52-0.7.4_2) is not jobs safe
On Dec 25, 2013, at 8:02 AM, Peter p...@citylink.dinoex.sub.org wrote: This seems to be a race condition with the timestamps of the Makefiles. make install thinks that the Makefiles are outdated, and recreates them before doing the install - but now with the target pointing directly to /usr/local and not to the staging area. In the log we can see this happening: Making install in liba52 gmake[1]: Entering directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' cd .. \ CONFIG_FILES=liba52/Makefile CONFIG_HEADERS= /bin/sh ./config.status config.status: creating liba52/Makefile config.status: executing default-1 commands gmake[1]: Leaving directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' gmake[1]: Entering directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' gmake[2]: Entering directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' /bin/sh ../autotools/mkinstalldirs /usr/local/lib while on successful runs these lines do not appear: Making install in liba52 gmake[1]: Entering directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' gmake[2]: Entering directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' /bin/sh ../autotools/mkinstalldirs /usr/ports/audio/liba52/work/stage/usr/local/lib I could not figure out why or how this happens - but for now a suitable workaround seems to be the following addition to the (main) makefile: pre-install: touch work/a52dec-*/*/Makefile I can confirm that addition to the Makefile worked perfectly for me on all of 200 runs on both test servers. Thanks Peter! Can someone close the PR after making a commit with the addition of the aforementioned pre-install target to /usr/ports/audio/liba52/Makefile please? (No revision bump necessary.) -Chad ___ 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
Please commit ports/184655 (net-p2p/bitcoin) and a slave port too
Hate to be a pest, but the update to 0.8.6 is deemed critical. PR ports/184655
has the update. Is there an issue necessitating further testing? Working well
for me.
Also, while yer at it, might someone pretty-please commit for me something
along the following lines into a slave port at net-p2p/bitcoin-nox11/Makefile
so one might easily decide to have both bitcoind and bitcoin-qt installed on
the same system? Would be much appreciated:
PKGNAMESUFFIX= -nox11
COMMENT= Virtual Peer-to-Peer Currency Client
MASTERDIR= ${.CURDIR}/../bitcoin
DESCR= ${MASTERDIR}/pkg-descr
SLAVE_PORT= yes
OPTIONS_EXCLUDE= GUI QRCODES
.include ${MASTERDIR}/Makefile
___
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: Is it or isn't it installed? (It is, but ports tries to again, doomed to fail.)
On 11/5/2013 11:13 AM, William Grzybowski wrote:
On Tue, Nov 5, 2013 at 2:09 PM, Dominic Fandrey kamik...@bsdforen.de wrote:
On 05/11/2013 14:55, Chad J. Milios wrote:
snip...
Just happen to already have the dependency devel/py-boto (py27-boto-2.14.0) or
devel/py-pyzmq (py27-pyzmq-2.2.0) installed (and their port dirs since cleaned
up) when you try to install net/py-kombu (py27-kombu-3.0.1) from ports with
BOTO and/or ZMQ options. (In my case I have all its options on.)
...snip...
Stop in /usr/ports/net/py-kombu.
root@shikamaru:/usr/ports/net/py-kombu #
That looks like the dependencies in net/py-kombu are broken. I.e. they
refer to files that are not/no longer installed by the dependencies.
Actually, Dominic, the dependencies were referred to using the
package_name/version_spec functionality rather than checking the
existence of a target file. There was an error with the way the version
requirement was specified which William has since fixed.
Did you get my email asking to try again after the last port update
fixing the dependencies?
YUP! Sure did fix it, William. THANK YOU for the super-quick response
and fix. Sorry it took me this long to get around to a re-test for you.
It looks like your fix did the trick:
28c28
BOTO_RUN_DEPENDS=
${PYTHON_PKGNAMEPREFIX}boto=2.6.0:${PORTSDIR}/devel/py-boto
---
BOTO_RUN_DEPENDS=
${PYTHON_PKGNAMEPREFIX}boto=2.6.0:${PORTSDIR}/devel/py-boto
32c32
ZMQ_RUN_DEPENDS=
${PYTHON_PKGNAMEPREFIX}pyzmq=2.2.0:${PORTSDIR}/devel/py-pyzmq
---
ZMQ_RUN_DEPENDS=
${PYTHON_PKGNAMEPREFIX}pyzmq=2.2.0:${PORTSDIR}/devel/py-pyzmq
Anyone spot the subtle difference? Darn. That went right under my nose.
Seems like a mistake anyone could make, with all the syntaxen floating
around in one's head. I for one think it would be nice if make failed
more spectacularly at the point it hits the =. Is there any legal use
of = in make? It seems that every occurrence of = in the ports tree is
now either just part of some inlined perl code, part of human-readable
text output or in a comment. Food for thought: I wonder what make is
thinking at that point of parsing and executing. Can the make makers
make make see that as an immediate syntax error without a drastic change
that breaks Makefiles potentially in the wild? A question for far
greater minds than I. Prolly already wudda if they cudda. Oh well, just
another make gotcha for everyone to remember to watch out for.
Thanks again WG@ for fixing my issue within half an hour of my mail to
freebsd-ports@ !!!
___
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
Is it or isn't it installed? (It is, but ports tries to again, doomed to fail.)
TLDR; check lines prefixed with ? in the transcript below. Ran into this over a couple weeks ago. Checked again with last night's portsnap, same problem, same ports. Figured I ought to pipe up about it. Seems like a good ol' classic mystery. I don't know if it's just one instance of a general problem in the way dependencies get detected and dispatched to be installed, maybe just in the python infrastructure, a bug in the net/py-kombu port (which my eyes couldn't find a problem with), or what. I looked into it for an hour before punting with a trivial workaround and moving on, didn't think much of it at the time, figuring it was just one of those temporary problems smarter minds are already hard at work fixing. Apparently they weren't or didn't. This time I'm using a squeaky clean new amd64 9.2-RELEASE-p1 system (empty /usr/local then installing all ports from the same snapshot of /usr/ports). ***How to reproduce: Just happen to already have the dependency devel/py-boto (py27-boto-2.14.0) or devel/py-pyzmq (py27-pyzmq-2.2.0) installed (and their port dirs since cleaned up) when you try to install net/py-kombu (py27-kombu-3.0.1) from ports with BOTO and/or ZMQ options. (In my case I have all its options on.) ***Transcripts: (attention to lines prefixed with ? and !) === Installing for py27-kombu-3.0.1 === py27-kombu-3.0.1 depends on package: py27-amqp=1.3.1 - found === py27-kombu-3.0.1 depends on package: py27-anyjson=0.3.3 - found === py27-kombu-3.0.1 depends on package: py27-beanstalkc0 - found ?=== py27-kombu-3.0.1 depends on package: py27-boto=2.6.0 - not found ===Verifying install for py27-boto=2.6.0 in /usr/ports/devel/py-boto === Installing for py27-boto-2.14.0 === py27-boto-2.14.0 depends on file: /usr/local/bin/easy_install-2.7 - found === py27-boto-2.14.0 depends on file: /usr/local/bin/python2.7 - found === py27-boto-2.14.0 depends on executable: python - found === py27-boto-2.14.0 depends on executable: python2 - found === Generating temporary packing list === Checking if devel/py-boto already installed ?=== py27-boto-2.14.0 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/py-boto without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/devel/py-boto. *** [run-depends] Error code 1 Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # === Installing for py27-kombu-3.0.1 === py27-kombu-3.0.1 depends on package: py27-amqp=1.3.1 - found === py27-kombu-3.0.1 depends on package: py27-anyjson=0.3.3 - found === py27-kombu-3.0.1 depends on package: py27-beanstalkc0 - found !=== py27-kombu-3.0.1 depends on package: py27-boto=2.6.0 - not found !===Verifying install for py27-boto=2.6.0 in /usr/ports/devel/py-boto !=== Returning to build of py27-kombu-3.0.1 === py27-kombu-3.0.1 depends on package: pymongo0 - found === py27-kombu-3.0.1 depends on package: py27-sqlalchemy0 - found ?=== py27-kombu-3.0.1 depends on package: py27-pyzmq=2.2.0 - not found ===Verifying install for py27-pyzmq=2.2.0 in /usr/ports/devel/py-pyzmq === Installing for py27-pyzmq-2.2.0 === py27-pyzmq-2.2.0 depends on file: /usr/local/bin/python2.7 - found === py27-pyzmq-2.2.0 depends on executable: python - found === py27-pyzmq-2.2.0 depends on shared library: zmq.1 - found === Generating temporary packing list === Checking if devel/py-pyzmq already installed ?=== py27-pyzmq-2.2.0 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/py-pyzmq without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/devel/py-pyzmq. *** [run-depends] Error code 1 Stop in /usr/ports/net/py-kombu. *** [install] Error code 1 Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # ___ 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
[PATCH] www/w3m fails to build under stable/10 r256624 i386
found this at:
http://sourceforge.net/p/w3m/patches/59/
confirmed compiles, confirmed works on:
FreeBSD naruto.ccsys.com 9.2-RELEASE FreeBSD 9.2-RELEASE #1 r256078: Sun
Oct 6 07:24:48 UTC 2013
r...@shikamaru.ccsys.com:/usr/obj/usr/src/sys/VIMAGE amd64
--- main.c.orig 2011-01-04 09:42:19.0 +
+++ main.c 2013-10-18 20:38:37.342820541 +
@@ -833,7 +833,12 @@
mySignal(SIGPIPE, SigPipe);
#endif
+#if GC_VERSION_MAJOR = 7 GC_VERSION_MINOR = 2
+orig_GC_warn_proc = GC_get_warn_proc();
+GC_set_warn_proc(wrap_GC_warn_proc);
+#else
orig_GC_warn_proc = GC_set_warn_proc(wrap_GC_warn_proc);
+#endif
err_msg = Strnew();
if (load_argc == 0) {
/* no URL specified */
___
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
