Re: Building subversion-1.8.10 under poudriere
Hi! On Wed, Aug 27, 2014 at 05:30:22PM -0500, Lawrence K. Chen, P.Eng. wrote: Wonder if there's still time to now see what ports I have installed that haven't been staged yet? This doesn't quite answer your question, but there's a portsmon page listing all nonstaged ports: http://portsmon.freebsd.org/portsconcordancefornostage.py?sortby=portname bapt has this list, I don't know the update frequency etc. http://people.freebsd.org/~bapt/notstaged.txt -- p...@opsec.eu+49 171 3101372 6 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
Re: Building subversion-1.8.10 under poudriere
Hi! On Wed, Aug 27, 2014 at 05:30:22PM -0500, Lawrence K. Chen, P.Eng. wrote: Wonder if there's still time to now see what ports I have installed that haven't been staged yet? This doesn't quite answer your question, but there's a portsmon page listing all nonstaged ports: http://portsmon.freebsd.org/portsconcordancefornostage.py?sortby=portname bapt has this list, I don't know the update frequency etc. http://people.freebsd.org/~bapt/notstaged.txt To have it updated whenever you want #!/bin/sh echo == Checking ports not staged. === /usr/local/bin/curl -s 'http://portsmon.freebsd.org/portsconcordancefornostage.py?sortby=portname' | /usr/bin/grep 'portname' | /usr/bin/cut -d'' -f3 | /usr/bin/cut -d'' -f1 | /usr/bin/sed '1,2d;$d' notstaged.txt || exit 1 /usr/bin/wc -l notstaged.txt || exit 1 echo == Portnotstaged done. === Cheers, -- Carlos Jacobo Puga Medina c...@fbsd.es ___ 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
Building subversion-1.8.10 under poudriere
Hi, Starting to use poudriere, and I'm pleasantly surprised. And even more after the first install steps. Don't have to go to all the different servers copy my ports-configs, and build... So I'm trying to get subversion build in poudriere for 9.3 amd and I keep running into: cd subversion/svn /bin/sh /wrkdirs/usr/ports/devel/subversion/work/subversion-1.8.10/libtool --tag=CC --silent --mode=link clang -all-static -Werror=unknown-warning-option -O2 -pipe -fpic -DPIC -fno-strict-aliasing-L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib -rpath /usr/local/lib -o svn add-cmd.lo blame-cmd.lo cat-cmd.lo changelist-cmd.lo checkout-cmd.lo cl-conflicts.lo cleanup-cmd.lo commit-cmd.lo conflict-callbacks.lo copy-cmd.lo delete-cmd.lo deprecated.lo diff-cmd.lo export-cmd.lo file-merge.lo help-cmd.lo import-cmd.lo info-cmd.lo list-cmd.lo lock-cmd.lo log-cmd.lo merge-cmd.lo mergeinfo-cmd.lo mkdir-cmd.lo move-cmd.lo notify.lo patch-cmd.lo propdel-cmd.lo propedit-cmd.lo propget-cmd.lo proplist-cmd.lo props.lo propset-cmd.lo relocate-cmd.lo resolve-cmd.lo resolved-cmd.lo revert-cmd.lo status-cmd.lo status.lo svn.lo switch-cmd.lo unlock-cmd.lo update-cmd.lo upgrade-cmd.lo util.lo ../../subversion/libsvn_client/libsvn_client-1.la ../../subversion/libsvn_wc/libsvn_wc-1.la ../../subversion/libsvn_ra/libsvn_ra-1.la ../../subversion/libsvn_delta/libsvn_delta-1.la ../../subversion/libsvn_diff/libsvn_diff-1.la ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib -laprutil-1 -ldb-5.3 -lgdbm -lexpat -liconv -L/usr/local/lib -lapr-1 -lcrypt -pthread -lintl /usr/local/lib/libapr-1.a(apr_snprintf.o): In function `apr_vformatter': strings/apr_snprintf.c:(.text+0x61c): undefined reference to `isnan' clang: error: linker command failed with exit code 1 (use -v to see invocation) *** [subversion/svn/svn] Error code 1 Stop in /wrkdirs/usr/ports/devel/subversion/work/subversion-1.8.10. *** [do-build] Error code 1 Stop in /usr/ports/devel/subversion. === Cleaning for subversion-1.8.10_1 If I build just by hand in /usr/ports it all just works fine. Trashing the whole config and restarting does not help. So one way or another the compiling/building oversees the fact that in math.h isnan() is a macro, and expects to link against a function to be supplied by a library. Any suggestions as to how to fix this? Normally I'd just try to whack the source into a working version, and go make make install. But how to do something like this under poudriere Thanx, --WjW ___ 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: Building subversion-1.8.10 under poudriere
On 27 Aug 2014, at 14:15, Willem Jan Withagen w...@digiware.nl wrote: Starting to use poudriere, and I'm pleasantly surprised. And even more after the first install steps. Don't have to go to all the different servers copy my ports-configs, and build... So I'm trying to get subversion build in poudriere for 9.3 amd and I keep running into: cd subversion/svn /bin/sh /wrkdirs/usr/ports/devel/subversion/work/subversion-1.8.10/libtool --tag=CC --silent --mode=link clang -all-static -Werror=unknown-warning-option -O2 -pipe -fpic -DPIC -fno-strict-aliasing-L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib -rpath /usr/local/lib -o svn add-cmd.lo blame-cmd.lo cat-cmd.lo changelist-cmd.lo checkout-cmd.lo cl-conflicts.lo cleanup-cmd.lo commit-cmd.lo conflict-callbacks.lo copy-cmd.lo delete-cmd.lo deprecated.lo diff-cmd.lo export-cmd.lo file-merge.lo help-cmd.lo import-cmd.lo info-cmd.lo list-cmd.lo lock-cmd.lo log-cmd.lo merge-cmd.lo mergeinfo-cmd.lo mkdir-cmd.lo move-cmd.lo notify.lo patch-cmd.lo propdel-cmd.lo propedit-cmd.lo propget-cmd.lo proplist-cmd.lo props.lo propset-cmd.lo relocate-cmd.lo resolve-cmd.lo resolved-cmd.lo revert-cmd.lo status-cmd.lo status.lo svn.lo switch-cmd.lo unlock-cmd.lo update-cmd.lo upgrade-cmd.lo util.lo ../../subversion/libsvn_client/libsvn_client-1.la ../../subversion/libsvn_wc/libsvn_wc-1.la ../../subversion/libsvn_ra/libsvn_ra-1.la ../../subversion/libsvn_delta/libsvn_delta-1.la ../../subversion/libsvn_diff/libsvn_diff-1.la ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib -laprutil-1 -ldb-5.3 -lgdbm -lexpat -liconv -L/usr/local/lib -lapr-1 -lcrypt -pthread -lintl /usr/local/lib/libapr-1.a(apr_snprintf.o): In function `apr_vformatter': strings/apr_snprintf.c:(.text+0x61c): undefined reference to `isnan' clang: error: linker command failed with exit code 1 (use -v to see invocation) This is a problem in the devel/apr1 port. It checks for modf(), finds it in libc, then assumes isnan() also comes from libc. However, that does not work for static linking. Please apply the attached patch for apr1, which I have been using for some time now. -Dimitry devel__apr1-3.diff Description: Binary data signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Building subversion-1.8.10 under poudriere
On 2014-08-27 14:41, Dimitry Andric wrote: On 27 Aug 2014, at 14:15, Willem Jan Withagen w...@digiware.nl wrote: Starting to use poudriere, and I'm pleasantly surprised. And even more after the first install steps. Don't have to go to all the different servers copy my ports-configs, and build... So I'm trying to get subversion build in poudriere for 9.3 amd and I keep running into: cd subversion/svn /bin/sh /wrkdirs/usr/ports/devel/subversion/work/subversion-1.8.10/libtool --tag=CC --silent --mode=link clang -all-static -Werror=unknown-warning-option -O2 -pipe -fpic -DPIC -fno-strict-aliasing-L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib -rpath /usr/local/lib -o svn add-cmd.lo blame-cmd.lo cat-cmd.lo changelist-cmd.lo checkout-cmd.lo cl-conflicts.lo cleanup-cmd.lo commit-cmd.lo conflict-callbacks.lo copy-cmd.lo delete-cmd.lo deprecated.lo diff-cmd.lo export-cmd.lo file-merge.lo help-cmd.lo import-cmd.lo info-cmd.lo list-cmd.lo lock-cmd.lo log-cmd.lo merge-cmd.lo mergeinfo-cmd.lo mkdir-cmd.lo move-cmd.lo notify.lo patch-cmd.lo propdel-cmd.lo propedit-cmd.lo propget-cmd.lo proplist-cmd.lo props.lo propset-cmd.lo relocate-cmd.lo resolve-cmd.lo resolved-cmd.lo revert-cmd.lo status-cmd.lo status.lo svn.lo switch-cmd.lo unlock-cmd.lo update-cmd.lo upgrade-cmd.lo util.lo ../../subversion/libsvn_client/libsvn_client-1.la ../../subversion/libsvn_wc /libsvn_wc-1.la ../../subversion/libsvn_ra/libsvn_ra-1.la ../../subversion/libsvn_delta/libsvn_delta-1.la ../../subversion/libsvn_diff/libsvn_diff-1.la ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib -laprutil-1 -ldb-5.3 -lgdbm -lexpat -liconv -L/usr/local/lib -lapr-1 -lcrypt -pthread -lintl /usr/local/lib/libapr-1.a(apr_snprintf.o): In function `apr_vformatter': strings/apr_snprintf.c:(.text+0x61c): undefined reference to `isnan' clang: error: linker command failed with exit code 1 (use -v to see invocation) This is a problem in the devel/apr1 port. It checks for modf(), finds it in libc, then assumes isnan() also comes from libc. However, that does not work for static linking. Please apply the attached patch for apr1, which I have been using for some time now. Hi Dimitry, So this is due to me wanting to link things static? Then I'll reconfig subversion to dynamic linking. Because I don't have a clue (yet) as to how to get (and keep) custom patches in a poudriere environment. Thanx for the reply, --WjW ___ 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: Building subversion-1.8.10 under poudriere
On 2014-08-27 15:09, Willem Jan Withagen wrote: On 2014-08-27 14:41, Dimitry Andric wrote: On 27 Aug 2014, at 14:15, Willem Jan Withagen w...@digiware.nl wrote: Starting to use poudriere, and I'm pleasantly surprised. And even more after the first install steps. Don't have to go to all the different servers copy my ports-configs, and build... So I'm trying to get subversion build in poudriere for 9.3 amd and I keep running into: cd subversion/svn /bin/sh /wrkdirs/usr/ports/devel/subversion/work/subversion-1.8.10/libtool --tag=CC --silent --mode=link clang -all-static -Werror=unknown-warning-option -O2 -pipe -fpic -DPIC -fno-strict-aliasing-L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib -rpath /usr/local/lib -o svn add-cmd.lo blame-cmd.lo cat-cmd.lo changelist-cmd.lo checkout-cmd.lo cl-conflicts.lo cleanup-cmd.lo commit-cmd.lo conflict-callbacks.lo copy-cmd.lo delete-cmd.lo deprecated.lo diff-cmd.lo export-cmd.lo file-merge.lo help-cmd.lo import-cmd.lo info-cmd.lo list-cmd.lo lock-cmd.lo log-cmd.lo merge-cmd.lo mergeinfo-cmd.lo mkdir-cmd.lo move-cmd.lo notify.lo patch-cmd.lo propdel-cmd.lo propedit-cmd.lo propget-cmd.lo proplist-cmd.lo props.lo propset-cmd.lo relocate-cmd.lo resolve-cmd.lo resolved-cmd.lo revert-cmd.lo status-cmd.lo status.lo svn.lo switch-cmd.lo unlock-cmd.lo update-cmd.lo upgrade-cmd.lo util.lo ../../subversion/libsvn_client/libsvn_client-1.la ../../subversion/libsvn_wc /libsvn_wc-1.la ../../subversion/libsvn_ra/libsvn_ra-1.la ../../subversion/libsvn_delta/libsvn_delta-1.la ../../subversion/libsvn_diff/libsvn_diff-1.la ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib -laprutil-1 -ldb-5.3 -lgdbm -lexpat -liconv -L/usr/local/lib -lapr-1 -lcrypt -pthread -lintl /usr/local/lib/libapr-1.a(apr_snprintf.o): In function `apr_vformatter': strings/apr_snprintf.c:(.text+0x61c): undefined reference to `isnan' clang: error: linker command failed with exit code 1 (use -v to see invocation) This is a problem in the devel/apr1 port. It checks for modf(), finds it in libc, then assumes isnan() also comes from libc. However, that does not work for static linking. Please apply the attached patch for apr1, which I have been using for some time now. Hi Dimitry, So this is due to me wanting to link things static? Then I'll reconfig subversion to dynamic linking. Because I don't have a clue (yet) as to how to get (and keep) custom patches in a poudriere environment. Right, At least that was also the different between building via poudriere or just natively on the host: Static linking. Atleast I now have a set of packesg that I can distribute. Thanx for fixing my problem, --WjW ___ 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: Building subversion-1.8.10 under poudriere
On 08/27/2014 09:09, Willem Jan Withagen wrote:
On 2014-08-27 14:41, Dimitry Andric wrote:
This is a problem in the devel/apr1 port. It checks for modf(), finds
it in libc, then assumes isnan() also comes from libc. However, that
does not work for static linking.
Please apply the attached patch for apr1, which I have been using for
some time now.
Hi Dimitry,
So this is due to me wanting to link things static?
Then I'll reconfig subversion to dynamic linking.
Because I don't have a clue (yet) as to how to get (and keep) custom
patches in a poudriere environment.
Thanx for the reply,
--WjW
I keep custom patches this way:
/usr/local/etc/poudriere.d/my-appropriate-make.conf:
.if ${.CURDIR:M*/mail/mutt}
EXTRA_PATCHES+= /distfiles/mypatches/patch-mail-mutt-fix-imap-append
.endif
You may also be interested in things like:
.if ${.CURDIR:M*/security/krb5}
CONFIGURE_ARGS+=--localstatedir=/var/db
WITH_OPENSSL_PORT=yes
.endif
I suggest using this method in poudriere's make.conf for port building
options:
DEFAULT_VERSIONS= perl5=5.16 php=5.4 mysql=5.5 apache=2.2 pgsql=8.4
# Global port options
OPTIONS_UNSET+=AVAHI BONJOUR CUPS MDNS PULSEAUDIO
# specific port options:
mail_dovecot_SET=GSSAPI
mail_dovecot_UNSET=MANAGESIEVE
That way you only change the options you desire and aren't hardcoding
any of the other port options in case the default changes in the future,
possibly in a critical way (threading for example).
The path to the patch must be a proper path within port building jails
and I believe poudriere mounts it's distfiles directory on /distfiles.
It has to be a path that is available within port building jails. I
picked distfiles because it is available. One thing I like about
EXTRA_PATCHES is it will cause a port build to fail if the file is not
found, so if that happens I will know to correct the problem rather than
produce unpatched packages. I add my mypatches directory to my
standard server backups so it is easy to restore if needed. Beware
running poudriere distclean since it will wipe out unreferenced files in
distfiles.
___
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: Building subversion-1.8.10 under poudriere
On 08/27/14 08:41, Adam McDougall wrote:
On 08/27/2014 09:09, Willem Jan Withagen wrote:
On 2014-08-27 14:41, Dimitry Andric wrote:
This is a problem in the devel/apr1 port. It checks for modf(), finds
it in libc, then assumes isnan() also comes from libc. However, that
does not work for static linking.
Please apply the attached patch for apr1, which I have been using for
some time now.
Hi Dimitry,
So this is due to me wanting to link things static?
Then I'll reconfig subversion to dynamic linking.
Because I don't have a clue (yet) as to how to get (and keep) custom
patches in a poudriere environment.
Thanx for the reply,
--WjW
I keep custom patches this way:
/usr/local/etc/poudriere.d/my-appropriate-make.conf:
.if ${.CURDIR:M*/mail/mutt}
EXTRA_PATCHES+= /distfiles/mypatches/patch-mail-mutt-fix-imap-append
.endif
You may also be interested in things like:
.if ${.CURDIR:M*/security/krb5}
CONFIGURE_ARGS+=--localstatedir=/var/db
WITH_OPENSSL_PORT=yes
.endif
I suggest using this method in poudriere's make.conf for port building
options:
DEFAULT_VERSIONS= perl5=5.16 php=5.4 mysql=5.5 apache=2.2 pgsql=8.4
# Global port options
OPTIONS_UNSET+=AVAHI BONJOUR CUPS MDNS PULSEAUDIO
# specific port options:
mail_dovecot_SET=GSSAPI
mail_dovecot_UNSET=MANAGESIEVE
That way you only change the options you desire and aren't hardcoding
any of the other port options in case the default changes in the future,
possibly in a critical way (threading for example).
The path to the patch must be a proper path within port building jails
and I believe poudriere mounts it's distfiles directory on /distfiles.
It has to be a path that is available within port building jails. I
picked distfiles because it is available. One thing I like about
EXTRA_PATCHES is it will cause a port build to fail if the file is not
found, so if that happens I will know to correct the problem rather than
produce unpatched packages. I add my mypatches directory to my
standard server backups so it is easy to restore if needed. Beware
running poudriere distclean since it will wipe out unreferenced files in
distfiles.
Hmmm, wonder why I didn't think of that?
I've been trying to get poudriere workingI did go through the ugly
exercise of going through all my servers to attempt to unify port options.
Currently trying to go with two setsone for my headless servers and one
for servers with heads :) Though there's still enough difference that it
might not be possible. Though I've also thought of additional sets to
generate packages for updates I haven't done yet (which is one of reasons
driving trying to get things working, I haven't upgraded from apache 2.2 to
2.4 yet)
What I settled on instead of to create a tree with my extra patches, and use
portshaker to merge
Other delays in getting this going, is that I've been trying to use CFEngine
to handle the consolidation of options and pkglists and driving portshaker and
poudriere
I did a bulk run of everything from my headless servers this morningof
622, only one failed, one skipped, and one ignored.
The failed port was 'x11-toolkits/ocaml-lablgtk2', could probably get around
it by changing port option for no-X11 for unison on these servers. The
skipped port was unison, where the failed port is a dependency. Probably
don't need X11 graphics support in unison on these servers (even though
one of the servers starts Xvfb during bootbecause it runs an application
that needs X during startup, but never again once its runningLinux version
probably has the same weird issue, except none of my Linux servers were
headless...so it was never noticed. Killed off the last Linux server on
August 10th...) Which is why I didn't do OPTIONS_UNSET= X11 in make.conf
for this setbut I almost did.
The ignored port was because I had missed setting a required setting in
make.conf (its missing on all my servers...but haven't had to update that port
since it got installed, so didn't notice the settings had disappeared.)
Now I'm having trouble because I have ports installed (namely gnome related)
that had long ago disappeared
Wonder if there's still time to now see what ports I have installed that
haven't been staged yet?
--
Who: Lawrence K. Chen, P.Eng. - W0LKC - Sr. Unix Systems Administrator
For: Enterprise Server Technologies (EST) -- SafeZone Ally
___
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: Building subversion-1.8.10 under poudriere
On 08/27/14 17:30, Lawrence K. Chen, P.Eng. wrote:
On 08/27/14 08:41, Adam McDougall wrote:
On 08/27/2014 09:09, Willem Jan Withagen wrote:
On 2014-08-27 14:41, Dimitry Andric wrote:
This is a problem in the devel/apr1 port. It checks for modf(), finds
it in libc, then assumes isnan() also comes from libc. However, that
does not work for static linking.
Please apply the attached patch for apr1, which I have been using for
some time now.
Hi Dimitry,
So this is due to me wanting to link things static?
Then I'll reconfig subversion to dynamic linking.
Because I don't have a clue (yet) as to how to get (and keep) custom
patches in a poudriere environment.
Thanx for the reply,
--WjW
I keep custom patches this way:
/usr/local/etc/poudriere.d/my-appropriate-make.conf:
.if ${.CURDIR:M*/mail/mutt}
EXTRA_PATCHES+= /distfiles/mypatches/patch-mail-mutt-fix-imap-append
.endif
You may also be interested in things like:
.if ${.CURDIR:M*/security/krb5}
CONFIGURE_ARGS+=--localstatedir=/var/db
WITH_OPENSSL_PORT=yes
.endif
I suggest using this method in poudriere's make.conf for port building
options:
DEFAULT_VERSIONS= perl5=5.16 php=5.4 mysql=5.5 apache=2.2 pgsql=8.4
# Global port options
OPTIONS_UNSET+=AVAHI BONJOUR CUPS MDNS PULSEAUDIO
# specific port options:
mail_dovecot_SET=GSSAPI
mail_dovecot_UNSET=MANAGESIEVE
That way you only change the options you desire and aren't hardcoding
any of the other port options in case the default changes in the future,
possibly in a critical way (threading for example).
The path to the patch must be a proper path within port building jails
and I believe poudriere mounts it's distfiles directory on /distfiles.
It has to be a path that is available within port building jails. I
picked distfiles because it is available. One thing I like about
EXTRA_PATCHES is it will cause a port build to fail if the file is not
found, so if that happens I will know to correct the problem rather than
produce unpatched packages. I add my mypatches directory to my
standard server backups so it is easy to restore if needed. Beware
running poudriere distclean since it will wipe out unreferenced files in
distfiles.
Hmmm, wonder why I didn't think of that?
I've been trying to get poudriere workingI did go through the ugly
exercise of going through all my servers to attempt to unify port options.
Currently trying to go with two setsone for my headless servers and one
for servers with heads :) Though there's still enough difference that it
might not be possible. Though I've also thought of additional sets to
generate packages for updates I haven't done yet (which is one of reasons
driving trying to get things working, I haven't upgraded from apache 2.2 to
2.4 yet)
What I settled on instead of to create a tree with my extra patches, and use
portshaker to merge
Other delays in getting this going, is that I've been trying to use CFEngine
to handle the consolidation of options and pkglists and driving portshaker and
poudriere
I did a bulk run of everything from my headless servers this morningof
622, only one failed, one skipped, and one ignored.
The failed port was 'x11-toolkits/ocaml-lablgtk2', could probably get around
it by changing port option for no-X11 for unison on these servers. The
skipped port was unison, where the failed port is a dependency. Probably
don't need X11 graphics support in unison on these servers (even though
one of the servers starts Xvfb during bootbecause it runs an application
that needs X during startup, but never again once its runningLinux version
probably has the same weird issue, except none of my Linux servers were
headless...so it was never noticed. Killed off the last Linux server on
August 10th...) Which is why I didn't do OPTIONS_UNSET= X11 in make.conf
for this setbut I almost did.
The ignored port was because I had missed setting a required setting in
make.conf (its missing on all my servers...but haven't had to update that port
since it got installed, so didn't notice the settings had disappeared.)
Now I'm having trouble because I have ports installed (namely gnome related)
that had long ago disappeared
Wonder if there's still time to now see what ports I have installed that
haven't been staged yet?
And, now another poudriere bulk run is in progressthe final obstacle was
that I some how had a dependency loop...
pulseaudio-0.9.23_2 - jackit-0.121.3_5 - doxygen-1.8.7_1,1 -
tex-web2c-20140525 - zziplib-0.13.62_1 - sdl-1.2.15_4,2 - pulseaudio-0.9.23_2
Wonder how that came to beforget why I had turned on JACK in pulseaudio on
one system, its not set on the othersso changing that broke the loop ;)
--
Who: Lawrence K. Chen, P.Eng. - W0LKC - Sr. Unix Systems Administrator
For: Enterprise Server Technologies (EST) -- SafeZone Ally
___
Re: Building subversion-1.8.10 under poudriere
On Wed, Aug 27, 2014 at 05:30:22PM -0500, Lawrence K. Chen, P.Eng. wrote: Wonder if there's still time to now see what ports I have installed that haven't been staged yet? This doesn't quite answer your question, but there's a portsmon page listing all nonstaged ports: http://portsmon.freebsd.org/portsconcordancefornostage.py?sortby=portname The current count shown is 637. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
