Re: Out of memory building lang/ghc-8.8.3
On 2020-05-05 14:19:50, Gleb Popov (arr...@freebsd.org) wrote: > On Tue, May 5, 2020 at 1:37 PM andrew clarke wrote: > > > Beware anyone building lang/ghc-8.8.3 from the ports tree. Building it > > here on FreeBSD 12.1-REL AMD64 with Poudriere, the build ran out of swap, > > despite the PC having 8 GB RAM, 8 GB swap and not much else running. > > > > My /usr/local/etc/poudriere.conf: > > > > BASEFS=/poudriere > > ZPOOL=zroot > > FREEBSD_HOST=http://mirror.internode.net/ > > POUDRIERE_DATA=/poudriere/data > > RESOLV_CONF=/etc/resolv.conf > > DISTFILES_CACHE=/usr/ports/distfiles > > USE_TMPFS=yes > > ALLOW_MAKE_JOBS=yes > > KEEP_OLD_PACKAGES=yes > > PARALLEL_JOBS=8 > > > > Maybe I can retune the last three parameters to use less memory. I've not > > tried yet. > > > > This isn't really a whinge, I'm just surprised it failed. I'd have thought > > 8 GB was enough. > > > > (ghc is a build dependency of textproc/hs-pandoc) > > > > Did you have something else building at the same time? > > On my laptop with 16 Gb of RAM I also see OOM failures when building > multiple "heavy" packages (llvmXX, gccX, ghc, rust, libreoffice) > simultaneously. In this case I use -J poudriere option to limit number of > jobs. Nothing else building. This is a headless server, so I've no need to build something the size of libreoffice or chromium. I've noticed llvm10 takes a long time to build, but 8 GB seems plenty of memory for it. The -J option sounds like the way to go, provided I remember to use it next time. Or I could instead set PARALLEL_JOBS=1 in poudriere.conf but then build performance will suffer for every port, which isn't ideal. But perhaps there's an option to limit make jobs just for a single port, set in /usr/local/etc/poudriere.d/make.conf ? That would be nice. ___ 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"
Out of memory building lang/ghc-8.8.3
Beware anyone building lang/ghc-8.8.3 from the ports tree. Building it here on FreeBSD 12.1-REL AMD64 with Poudriere, the build ran out of swap, despite the PC having 8 GB RAM, 8 GB swap and not much else running. My /usr/local/etc/poudriere.conf: BASEFS=/poudriere ZPOOL=zroot FREEBSD_HOST=http://mirror.internode.net/ POUDRIERE_DATA=/poudriere/data RESOLV_CONF=/etc/resolv.conf DISTFILES_CACHE=/usr/ports/distfiles USE_TMPFS=yes ALLOW_MAKE_JOBS=yes KEEP_OLD_PACKAGES=yes PARALLEL_JOBS=8 Maybe I can retune the last three parameters to use less memory. I've not tried yet. This isn't really a whinge, I'm just surprised it failed. I'd have thought 8 GB was enough. (ghc is a build dependency of textproc/hs-pandoc) Cheers. ___ 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: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available
On 2020-04-18 09:34:39, Matthew Seaman (matt...@freebsd.org) wrote: > On 18/04/2020 03:19, Robert Huff wrote: > > a) according to the Makefile, is it possible to build this with > > python-37? (Or even -36?) > > If the Makefile for the port says: > > USES= python:27 > > then the port is for python-2.7.x only. All other python ports will > support python-3.x (which practically speaking means python-3.7). Note > that ports that are python-2.7.x only are now as rare as hen's teeth as > there has been an active program of deleting such. Out of interest I ran "pkg del python27" on my FreeBSD machine just to see what would break. Conspicuous was devel/mercurial: PORTVERSION=5.1.2 USES= cpe python:2.7 Evidently Mercurial versions 5.2 and later support Python 3. The current stable version is 5.3.2, so the FreeBSD port is a few versions behind for some reason. Evidently textproc/asciidoc also still requires Python 2.7. Though it looks like it's possible to install both Mercurial and Asciidoc using Python 3's "pip" instead of using FreeBSD ports. ___ 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: devel/dee Python27
On Thu 2019-08-15 13:10:05 UTC+1000, Andrew Johnson (dae...@optushome.com.au) wrote: > Is there any plan to drop the Python2.7 dependency of devel/dee? It's probably out of scope of FreeBSD Ports to supply patches to the Python part of the libdee code that rewrites it to use Python 3.x instead of Python 2.7. Looking at upstream[1][2], that code hasn't been updated since 2013. The online documentation[3] is also missing. Based on the bitrot, my guess is it has been superceded by something else? Disclaimer: I don't use libdee. [1] https://launchpadlibrarian.net/151383425/ "No Such Resource" [2] https://launchpad.net/dee/ still lists the most recent version as 1.2.7 [3] http://developer.ubuntu.com/api/ubuntu-12.04/c/dee/ 404: Page not found ___ 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: category qt?
On Mon 2018-12-24 11:06:56 UTC+0100, Walter Schwarzenfeld (w.schwarzenf...@utanet.at) wrote: > The qt* ports spreads around in the whole portstree. > > It is reasonable to concentrate all these ports in a qt category? I think it > is easier to find (and also easier to maintain). Why? You'd end up with, for eg. VirtualBox at emulators/virtualbox-ose being moved to qt/virtualbox-ose, and QEMU remain as emulators/qemu, which is a system that makes no sense to me. I suspect many other people would object to something like that. ___ 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: Updating poudriere jail
On Fri 2018-12-14 11:13:16 UTC+, Carmel NY (carmel...@outlook.com) wrote: > ># build Postfix with Cyrus SASL support > >mail_postfix_SET=SASL > > > >Of course, be sure to point your FreeBSD 12.0-REL systems to your new 12.0 > >repo, instead of your old 11.x repo. > > > >Regards > >Andrew > > You know, that there are both a: > > Port: postfix-current-sasl-3.4.20181202,5 > Path: /usr/ports/mail/postfix-current-sasl > Info: Experimental Postfix version > > and > > Port: postfix-sasl-3.3.2_1,1 > Path: /usr/ports/mail/postfix-sasl > Info: Postfix with Cyrus SASL support > > Why not just use one of them? I had no idea until it was mentioned to me off-list earlier. You learn something new every day :-) Thanks, Regards Andrew ___ 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: Updating poudriere jail
On Thu 2018-12-13 19:43:30 UTC+, Carmel NY (carmel...@outlook.com) wrote: > I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the > new version 12, what do I have to do to update the poudriere jail? Plus, if I > do update, will I have to rebuild all of my installed applications? > > Thanks :) I found it simplest to create a new poudriere jail named 12amd64 to coincide with my existing 11amd64 jail. In my case the only port I build that needs non-standard options is mail/postfix, to enable Cyrus SASL support. Consequently I have this setting in /usr/local/etc/poudriere.d/make.conf (outside the jail) which from what I understand applies to both my 11amd64 and 12amd64 (and future) poudriere jails: # build Postfix with Cyrus SASL support mail_postfix_SET=SASL Of course, be sure to point your FreeBSD 12.0-REL systems to your new 12.0 repo, instead of your old 11.x repo. Regards Andrew ___ 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: Correct __cplusplus where std::tr1::function turns into std::function ?
On Wed 2017-11-29 13:32:32 UTC-0800, Yuri (y...@freebsd.org) wrote: > |This code picks the latter (tr1) version on 11,1-STABLE while the correct > choice is the former variant. #elif __cplusplus >= 201103L || > (defined(_MSC_VER) && _MSC_VER >= 1800) using std::function; #else using > std::tr1::function; #endif symbols What is the correct __cplusplus then? And > how to find it for other symbols for future reference? (Googling failed to > find it.) Thanks! Yuri | You probably need to enable C++11 support: clang++ -std=c++11 otherwise clang++ sets __cplusplus to 199711L. ___ 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: Procmail Vulnerabilities check
On Sat 2017-11-25 22:20:13 UTC-0500, Kevin P. Neal (k...@neutralgood.org) wrote: > Is that the consensus to replace use of procmail with maildrop? > > A little googling makes it look like maildrop has the easy integration > with sendmail just like procmail. But is maildrop going to be around for > the next, oh, 20 years like procmail was? maildrop began circa 1999 and is part of the Courier Mail Server software. procmail began circa 1990. Arguably both are due for a modern replacement, although at least maildrop does not suffer from vulnerabilities, afaik. I migrated from procmail to maildrop a few years ago. My only real gripe with it is that it doesn't create Maildir subdirectories automatically, so you have to call 'maildirmake' from within each filter rule (but only if the subdirectory doesn't already exist!) making each maildroprc filter more complicated than necessary. ___ 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: Time for a firefox-56 port?
On Fri 2017-11-24 12:11:04 UTC+1100, Greg 'groggy' Lehey (g...@freebsd.org) wrote: > I'm sure I'm not the only person who relies on old addons. How about > a firefox-56 port until the current problems die down? Is using www/firefox-esr an option? ___ 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 updating crash in pkg-1.8.0
Hi,
The command "pkg updating" crashes since pkg-1.8.0.
Out of curiosity I rebuilt it from source, then single-stepped
pkg-static using gdb:
$ uname -a
FreeBSD blizzard.phoenix 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297264:
Fri Mar 25 02:10:02 UTC 2016
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
$ gdb --args pkg-static updating
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...
(gdb) break main
Breakpoint 1 at 0x40980e: file main.c, line 570.
(gdb) r
Starting program: /usr/home/ozzmosis/src/pkg/pkg-1.8.0/src/pkg-static updating
Breakpoint 1, main (argc=2, argv=0x7fffe4c8) at main.c:570
570 int64_t debug = 0;
Current language: auto; currently minimal
(gdb) n
584 struct option longopts[] = {
(gdb)
602 setvbuf(stdout, NULL, _IONBF, 0);
(gdb)
605 signal(SIGPIPE, SIG_IGN);
(gdb)
607 if (argc < 2)
(gdb)
616 if (setenv("POSIXLY_CORRECT", "1", 1) == -1)
(gdb)
626 while ((ch = getopt_long(argc, argv,
"+d"JAIL_OPT"c:C:R:r:lNvo:46", longopts, NULL)) != -1) {
(gdb)
671 argv += optind;
(gdb)
673 pkg_set_debug_level(debug);
(gdb)
675 if (version == 1)
(gdb)
678 if (show_commands && version == 0) {
(gdb)
686 umask(022);
(gdb)
687 pkg_event_register(_callback, );
(gdb)
690 optreset = 1;
(gdb)
691 optind = 1;
(gdb)
693 if (debug == 0 && version == 0)
(gdb)
462 child_pid = fork();
(gdb)
464 if (child_pid == 0) {
(gdb)
473 while (waitpid(child_pid, , 0) == -1) {
(gdb)
478 ret = WEXITSTATUS(status);
(gdb)
480 if (WIFEXITED(status) && ret != EX_NEEDRESTART)
(gdb)
482 if (WIFSIGNALED(status)) {
(gdb)
484 fprintf(stderr, "Child process pid=%d
terminated abnormally: %s\n",
(gdb)
485 (int)child_pid,
strsignal (WTERMSIG(status)));
(gdb)
484 fprintf(stderr, "Child process pid=%d
terminated abnormally: %s\n",
(gdb)
Child process pid=33151 terminated abnormally: Trace/BPT trap
486 ret = 128 + WTERMSIG(status);
(gdb)
492 exit(ret);
(gdb)
Program exited with code 0205.
(gdb)
I'm not really sure what's going on here but it might be obvious to
the devs.
Thanks,
Regards
Andrew
___
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: damage to pkg's sqlite data base
On Wed 2015-05-13 19:00:27 UTC+1000, Peter Jeremy (pe...@rulingia.com) wrote: On 2015-May-13 18:12:44 +1000, andrew clarke m...@ozzmosis.com wrote: You can reinstall just those ports. Check /var/log/messages, eg. $ grep pkg /var/log/messages May 12 14:34:38 blizzard pkg: poudriere upgraded: 3.1.4 - 3.1.6 May 12 14:38:08 blizzard pkg: git-lite-2.4.0 installed May 13 08:29:04 blizzard pkg: sqlite3 upgraded: 3.8.9_1 - 3.8.10.1 May 13 08:29:05 blizzard pkg: spamassassin reinstalled: 3.4.1_1 - 3.4.1_1 May 13 08:29:05 blizzard pkg: ca_root_nss upgraded: 3.18.1 - 3.19 That assumes you have syslog messages back to when you started using pkg. syslog was never intended to provide an audit trail. True. I'd been wondering about why the pkg developers didn't add logging functionality, but it looks like I just needed to add this to /etc/syslog.conf: !pkg *.* /var/log/pkg.log then run: sudo touch /var/log/pkg.log sudo service restart syslogd I think that's correct. I'm not sure the syslog.conf entry above will include pkg-static - maybe it should be !pkg* instead? I must admit I find the syslog.conf man page to be not very helpful. $ cat /var/log/pkg.log May 13 20:58:25 blizzard pkg: jive-1.1 deinstalled May 13 20:58:29 blizzard pkg: jive-1.1 installed I tend to think pkg.log creation use should be a normal thing for a new FreeBSD install. The trick is to revert to a known-good backup of the pkg database that's generated daily by /usr/local/etc/periodic/daily/411.pkg-backup in /var/backups/ : -rw-r--r-- 1 root wheel 2207320 2015-05-13 04:20:30 pkg.sql.xz -rw-r--r-- 1 root wheel 2196088 2015-05-12 04:21:24 pkg.sql.xz.2 Assuming that they aren't corrupt. But that's better than nothing. Note that the backup is taken every day, whether or not there has been any change to the pkg database, so you have 2 days of backups, not the last two revisions. Yes, that's a deficiency in the periodic script. Probably not difficult to improve either, with the correct use of /usr/bin/diff. On 2015-May-13 18:17:12 +1000, andrew clarke m...@ozzmosis.com wrote: Actually I was wrong about this. The pkg command has the sqlite3 interpreter built-in, accessed via pkg shell, that opens local.sqlite by default: Some experimenting suggests that none of the pragma commands work in pkg shell, so you probably will need to find a copy of sqlite3. Oh dear, that's unfortunate. Regards Andrew ___ 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: damage to pkg's sqlite data base
On Tue 2015-05-12 01:17:46 UTC-0500, Scott Bennett (benn...@sdf.org) wrote: For nearly two weeks I've been stymied by an apparently damaged record in the sqlite data base used by pkg(8) and pkg-static(8). Unfortunately, it is a record for a port that is depended upon rather heavily, lang/gcc. lang/gcc compiled and linked just fine, but any attempt to install the result ends up like this. === Checking if gcc already installed === Registering installation for gcc-4.8.4_3 Installing gcc-4.8.4_3... pkg-static: sqlite error while executing iterator in file pkgdb_iterator.c:931: database disk image is malformed pkg-static: sqlite error while executing INSERT OR REPLACE INTO files (path, sha256, package_id) VALUES (?1, ?2, ?3) in file pkgdb.c:1722: database disk image is malformed *** Error code 70 Stop. make: stopped in /usr/ports/lang/gcc database disk image is malformed is an error from SQLite, the underlying database library that pkg uses, not pkg itself. If you can confidently rule-out hardware or filesystem error then presumably there is a glitch in SQLite that causes it to corrupt the database it's writing to. It shouldn't happen, and is evidently very rare judging from the lack of FreeBSD PRs about it. SQLite is quite popular and is used by Mozilla Firefox Google Chrome internally. It's possible pkg did something to trigger a bug in SQLite, so it may be worthwhile uploading your local.sqlite to a web site somewhere for one of the pkg developers to investigate, and file a PR with a link to the file. A bit of Googling indicates a fix may be possible, along the lines of: $ sqlite3 /var/db/pkg/local.sqlite SQLite version 3.8.10.1 2015-05-09 12:14:55 Enter .help for usage hints. sqlite pragma integrity_check; ok [sqlite may give an error here, but you can hopefully keep going...] sqlite .mode insert sqlite .output local.sqlite.dump sqlite .dump sqlite .quit $ ls -l local.sqlite.dump -rw-r--r-- 1 ozzmosis ozzmosis 10113463 2015-05-13 17:24:46 local.sqlite.dump Note that the database dump is simply a text file: $ file local.sqlite.dump local.sqlite.dump: ASCII text We can then recreate the database from the dump we just made: $ sqlite3 local.sqlite.new SQLite version 3.8.10.1 2015-05-09 12:14:55 Enter .help for usage hints. sqlite .read local.sqlite.dump sqlite .quit Now we can use our newly created database, which should be error-free: $ sudo cp /var/db/pkg/local.sqlite /var/db/pkg/local.sqlite.backup $ sudo mv local.sqlite.new /var/db/pkg/local.sqlite I don't guarantee any of the above will work. It will depend on how much the database is corrupted etc. You will also need databases/sqlite3 installed, which unfortunately isn't provided in the FreeBSD base system. This could be a problem if pkg refuses to install anything. In that case I would either run the above sqlite3 commands on another machine (or a jail?) and sort it out there, or run the sqlite3 binary from the /usr/ports/databasess/sqlite3 directory without installing it, or if that's not possible, make a backup of local.sqlite, delete local.sqlite, install sqlite3 from ports (or pkg install), then work on fixing the corrupt database. Obviously another option is to simply declare pkg bankruptcy. Get a list of all your installed packages (with pkg info -ao pkglist.txt), delete the corrupt local.sqlite then reinstall your packages. Regards Andrew ___ 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: damage to pkg's sqlite data base
On Wed 2015-05-13 00:12:51 UTC-0500, Scott Bennett (benn...@sdf.org) wrote: Simply rename your (now) corrupt db, and copy the backup over. However, if I do that, then what happens to all the ports that have been updated or added since that version of the data base was backed up? I have run portmaster -a (with some additional options) quite a few times since the lang/gcc problem first appeared, so an old local.sqlite will no longer accurately reflect what is currently installed. You can reinstall just those ports. Check /var/log/messages, eg. $ grep pkg /var/log/messages May 12 14:34:38 blizzard pkg: poudriere upgraded: 3.1.4 - 3.1.6 May 12 14:38:08 blizzard pkg: git-lite-2.4.0 installed May 13 08:29:04 blizzard pkg: sqlite3 upgraded: 3.8.9_1 - 3.8.10.1 May 13 08:29:05 blizzard pkg: spamassassin reinstalled: 3.4.1_1 - 3.4.1_1 May 13 08:29:05 blizzard pkg: ca_root_nss upgraded: 3.18.1 - 3.19 4) I was unable to find any instructions for recreating a pkg data base if the data base gets damaged/destroyed. Is there a way to do that that I missed? There must be a way to do this, right? I mean, really, it's pretty fundamental that no new data base be put into production without a way to rebuild it. The FreeBSD developers haven't really broken so ancient and basic a principle, have they? So what's the trick? What is the method to rebuild /var/db/pkg/local.sqlite from scratch based upon the currently installed ports/packages? You can't rebuild it. You couldn't rebuild it in the years before pkgng existed, either. The trick is to revert to a known-good backup of the pkg database that's generated daily by /usr/local/etc/periodic/daily/411.pkg-backup in /var/backups/ : -rw-r--r-- 1 root wheel 2207320 2015-05-13 04:20:30 pkg.sql.xz -rw-r--r-- 1 root wheel 2196088 2015-05-12 04:21:24 pkg.sql.xz.2 The .sql.xz files are just a SQLite dump, in xz compressed format. Regards Andrew ___ 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: damage to pkg's sqlite data base
On Wed 2015-05-13 17:55:26 UTC+1000, andrew clarke (m...@ozzmosis.com) wrote: $ sqlite3 local.sqlite.new SQLite version 3.8.10.1 2015-05-09 12:14:55 Enter .help for usage hints. sqlite .read local.sqlite.dump sqlite .quit Now we can use our newly created database, which should be error-free: $ sudo cp /var/db/pkg/local.sqlite /var/db/pkg/local.sqlite.backup $ sudo mv local.sqlite.new /var/db/pkg/local.sqlite I don't guarantee any of the above will work. It will depend on how much the database is corrupted etc. You will also need databases/sqlite3 installed, which unfortunately isn't provided in the FreeBSD base system. This could be a problem if pkg refuses to install anything. In that case I would either run the Actually I was wrong about this. The pkg command has the sqlite3 interpreter built-in, accessed via pkg shell, that opens local.sqlite by default: $ pkg shell SQLite version 3.8.8.2 2015-01-30 14:30:45 Enter .help for usage hints. sqlite .quit So there is no real need to install databases/sqlite3. Regards Andrew ___ 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: damage to pkg's sqlite data base
On Tue 2015-05-12 23:47:02 UTC-0700, Chris H (bsd-li...@bsdforge.com) wrote: I whined about it the first time my DB blew up. It's become corrupted several times since on different boxes/versions. *but* after the first time, I made it a habit of making a copy of it *before* embarking on an upgrade, or install of any ports. Can you post a link to your message and/or a link to your FreeBSD PR on Bugzilla? I use FreeBSD on a number of machines (bare metal virtual) and have never encountered local.sqlite corruption, and maybe I haven't been paying attention but I haven't noticed anyone else mention it on the list until now. As I said to the OP, if you encounter this problem and you're sure it's not caused externally (hardware or filesystem corruption) then it's probably worthwhile making your corrupted local.sqlite available somewhere for it to be looked at by someone who understands SQLite. Regards Andrew ___ 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: Shared object libiconv.so.2 not found
On Fri 2014-12-12 09:44:10 UTC+0100, Joel Dahl (j...@vnode.se) wrote: I installed 10.1 on a new box. Rebooted. Did a ”pkg install tmux zsh open-vm-tools-nox11”. Added the vmware_guestd options to rc.conf. Rebooted again. Now I see the following during boot: /dev/da0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0p2: clean, 3260251 free (771 frags, 407435 blocks, 0.0% fragmentation) Mounting local file systems:. Shared object libiconv.so.2 not found, required by libglib-2.0.so.0 Shared object libiconv.so.2 not found, required by libglib-2.0.so.0 Shared object libiconv.so.2 not found, required by libglib-2.0.so.0 Shared object libiconv.so.2 not found, required by libglib-2.0.so.0 Writing entropy file:. Eh? What is this? Do you have libiconv installed? $ pkg which /usr/local//lib/libiconv.so.2 /usr/local/lib/libiconv.so.2 was installed by package libiconv-1.14_6 $ ls -l /usr/local//lib/libiconv* -rw-r--r-- 1 root wheel 1107752 2014-12-05 18:43:00 /usr/local//lib/libiconv.a lrwxr-xr-x 1 root wheel 17 2014-12-05 18:43:00 /usr/local//lib/libiconv.so - libiconv.so.2.5.1 lrwxr-xr-x 1 root wheel 17 2014-12-05 18:43:00 /usr/local//lib/libiconv.so.2 - libiconv.so.2.5.1 -rw-r--r-- 1 root wheel 1072522 2014-12-05 18:43:00 /usr/local//lib/libiconv.so.2.5.1 lrwxr-xr-x 1 root wheel 13 2014-12-05 18:43:00 /usr/local//lib/libiconv.so.3 - libiconv.so.2 Regards Andrew ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: exif-0.6.21
On Fri 2014-12-12 15:51:25 UTC+, James McGuire (james.a.mcguir...@virgin.net) wrote: Hi there, I recently used your port to attempt to clear the exif tags from a set of jpeg files I had taken while on holiday. The port failed to clear the model of camera used, the latitude and longitude when used in the following manner 'exif --remove *' and complains that my camera a Nikon Coolpix S9700 has 'corrupt data' apparently an unrecognised EXIF field: As a workaround you might want to try the graphics/jhead port. -deDelete the Exif header entirely. Leaves other metadata sections intact. See the jhead man page for other options. Regards Andrew ___ 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: port www/elog
On Wed 2014-12-10 03:18:39 UTC-0800, Thomas Mueller (mueller6...@bellsouth.net) wrote: I am using this software with outdated version of FreeBSD. As I can see, this port is DEPRECATED and no longer available. Can any step up to maintain it? Please! -Chen I just looked found www/elog was not in the ports tree. I am not familiar with elog and wouldn't know where to find it. Evidently elog was removed from the ports tree in September: Remove non staged ports without pending PR from www http://www.freshports.org/www/elog I suspect a FreeBSD 9.3 ISO from July 2014 should have a Ports tarball with the necessary www/elog files which you can then use as a basis to have it re-added to Ports by a maintainer. ___ 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: port www/elog
On Wed 2014-12-10 14:44:38 UTC+0100, Torsten Zuehlsdorff (mailingli...@toco-domains.de) wrote: I am not familiar with elog and wouldn't know where to find it. have a look at the old files in SVN: http://svnweb.freebsd.org/ports/head/www/elog/?pathrev=360228 I was under the wrong impression that deleted files disappeared from the SVN history. Disregard my previous reply about hunting down a FreeBSD 9.3, then. Obviously not necessary. ___ 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
poudriere ports -u, divide by zero
I'm assuming this is just a superficial bug in the output. Possibly related: I have pkg-1.4.0 installed. # poudriere ports -u [00:00:00] Updating portstree default Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. Fetching snapshot tag from ec2-ap-southeast-2.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Updating from Wed Dec 10 09:57:21 AEDT 2014 to Wed Dec 10 11:26:11 AEDT 2014. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 0 patches. dc: divide by zero dc: divide by zero (0/0) 0.00% done. done. Applying patches... done. Fetching 0 new ports or files... done. Ports tree is already up to date. ___ 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: virtualbox issue
On Tue 2014-11-25 09:34:17 UTC-0500, R. Scott Evans (freebsd-emulat...@rsle.net) wrote: I sucessfully updated virtualbox on my 9.3-RELEASE (amd64) hosts today without incident but trying to update an existing virtualbox-ose-4.3.18 port to 4.3.20 on a 10.1-RELEASE (amd64) box and I get a fail message that I don't have 32 bit libraries. Worked without them before but okay, I try and install the 32 bit libraries: cd /usr/src; make build32 install32 and I now choke on libmagic... ... cd /usr/src/lib/libmagic; WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS=-m /usr/src/tools/build/mk -m /usr/src/share/mk MAKEOBJDIRPREFIX=/usr/obj/lib32 make SSP_CFLAGS= DESTDIR= DIRPRFX=lib/libmagic/ -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS -DNO_CTF -DEARLY_BUILD build-tools cc -O2 -pipe -DMAGIC='/usr/share/misc/magic' -DHAVE_CONFIG_H -I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file/src -std=gnu99 -I/usr/obj/usr/src/tmp/legacy/usr/include -DCOMPILE_ONLY -L/usr/obj/usr/src/tmp/legacy/usr/lib -o mkmagic /usr/src/lib/libmagic/../../contrib/file/src/apprentice.c /usr/src/lib/libmagic/../../contrib/file/src/cdf_time.c /usr/src/lib/libmagic/../../contrib/file/src/encoding.c /usr/src/lib/libmagic/../../contrib/file/src/funcs.c /usr/src/lib/libmagic/../../contrib/file/src/magic.c /usr/src/lib/libmagic/../../contrib/file/src/print.c -lz -legacy /usr/bin/ld: cannot find -legacy cc: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 I encountered this last month: https://lists.freebsd.org/pipermail/freebsd-ports/2014-October/096077.html https://lists.freebsd.org/pipermail/freebsd-ports/2014-November/096359.html Regards Andrew ___ 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: archivers/arj fails to build
On Mon 2014-11-17 20:00:01 UTC+0100, Kurt Jaeger (li...@opsec.eu) wrote: Unfortunately, archivers/arj fails to build: I just tested it on my reference install (10.1, amd64). It just builds. ARJ builds OK here on 10.1. My first thought is the OP has something unusual in /etc/make.conf. My second thought is whether you actually need ARJ. ClamAV evidently has it as a dependency, but I think it probably shouldn't given that ARJ archives are rarely seen in the wild these days. In any case you can exclude arj from the rebuild with: portmaster [options] -x arj Regards Andrew ___ 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: Deleting ports distfiles
On Sun 2014-11-16 23:29:37 UTC+0100, Dr. Peter Voigt (pvo...@uos.de) wrote: I have just seen that /usr/ports/distfiles has grown up to 12 GiB. My hopefully not too stupid question is: Can I safely delete all files under /usr/ports/distfiles, e.g. # rm -rf /usr/ports/distfiles/* I strongly suppose so but I am not sure. Thanks for any feedback. Yes. Missing distfiles will be redownloaded when/if you rebuild a port. Regards Andrew ___ 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: cannot find -legacy error building /usr/lib32 with FreeBSD 10.1-RC3
On Thu 2014-10-23 22:45:52 UTC+1100, andrew clarke (m...@ozzmosis.com) wrote: My intention was to build virtualbox-ose-additions-4.3.18 from ports... # uname -a FreeBSD vbox-freebsd10 10.1-RC3 FreeBSD 10.1-RC3 #0 r273437: Tue Oct 21 23:55:15 UTC 2014 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 # cd /usr/ports/emulators/virtualbox-ose-additions # make Requires 32-bit libraries installed under /usr/lib32. Do: cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32 *** Error code 1 Stop. It turns out I just needed to download ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/10.1-RC3/lib32.txz untar it to / and then I could build the above port. Not sure why I didn't have lib32 already installed. I must've unchecked it during the initial 10.0 install for some reason. ___ 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
cannot find -legacy error building /usr/lib32 with FreeBSD 10.1-RC3
My intention was to build virtualbox-ose-additions-4.3.18 from ports... # uname -a FreeBSD vbox-freebsd10 10.1-RC3 FreeBSD 10.1-RC3 #0 r273437: Tue Oct 21 23:55:15 UTC 2014 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 # cd /usr/ports/emulators/virtualbox-ose-additions # make Requires 32-bit libraries installed under /usr/lib32. Do: cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32 *** Error code 1 Stop. make[1]: stopped in /usr/ports/emulators/virtualbox-ose-additions # cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32 ... cc -O2 -pipe -DMAGIC='/usr/share/misc/magic' -DHAVE_CONFIG_H -I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file/src -std=gnu99 -I/usr/obj/usr/src/tmp/legacy/usr/include -DCOMPILE_ONLY -L/usr/obj/usr/src/tmp/legacy/usr/lib -o mkmagic /usr/src/lib/libmagic/../../contrib/file/src/apprentice.c /usr/src/lib/libmagic/../../contrib/file/src/cdf_time.c /usr/src/lib/libmagic/../../contrib/file/src/encoding.c /usr/src/lib/libmagic/../../contrib/file/src/funcs.c /usr/src/lib/libmagic/../../contrib/file/src/magic.c /usr/src/lib/libmagic/../../contrib/file/src/print.c -lz -legacy /usr/bin/ld: cannot find -legacy cc: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Stop. make[2]: stopped in /usr/src/lib/libmagic *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src According to this thread, http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044253.html make build32 no longer works? make buildworld seems a little excessive just for a single port. Regards Andrew ___ 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: multimedia/mkvtoolnix gui
On Wed 2014-10-01 21:01:59 UTC-0700, Russell L. Carter (rcar...@pinyon.org) wrote: So my stupid question is, how do you invoke the gui? It should be at /usr/local/bin/mmg . ___ 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
pkg 1.3.6 output bug
Installing a package built on another system I noticed pkg 1.3.6 shows incorrect output when installing with a dependency: # ls -l total 41123 -rw-r--r-- 1 ozzmosis ozzmosis 2428 24 Aug 18:07 clang-devel-3.6.r216160.txz -rw-r--r-- 1 ozzmosis ozzmosis 19728928 24 Aug 18:08 llvm-devel-3.6.r216160.txz # pkg add clang-devel-3.6.r216160.txz Installing llvm-devel-3.6.r216160: 100% Installing llvm-devel-3.6.r216160: 100% # pkg -v 1.3.6 ie. llvm-devel is output twice, clang-devel not at all. Pretty sure this is a bug? Thanks, Regards Andrew ___ 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: Who was the mental genius
On Fri 2014-06-06 17:17:40 UTC+0200, Baptiste Daroussin (b...@freebsd.org) wrote: Yes it would have been a good idea to give a warning to the user about the fact that the ports tree won't be support long on after EOL of 8.3, given the ports tree will break again quite soon after EOL of 8.4 I should think about adding such a message right now (btw this is not Is it viable to add an EOL message to portsnap(8)? ___ 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
editors/uemacs
On Sat 2014-05-10 10:33:52 UTC-0500, Bryan Drewery (bdrew...@freebsd.org) wrote: On June 31st, all unstaged ports will be marked DEPRECATED and have their MAINTAINER reset. On August 31st, all unstaged ports will be removed from the ports tree. I'm the listed maintainer of editors/uemacs, which is currently unstaged. Since I switched to JED some time ago I haven't used MicroEMACS, so have little motivation in working through this just for a single port. If anyone still using uemacs would like to take over as maintainer, that'd be cool. Regards Andrew ___ 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: editors/uemacs
On Mon 2014-05-12 10:13:46 UTC+1000, andrew clarke (m...@ozzmosis.com) wrote: I'm the listed maintainer of editors/uemacs, which is currently unstaged. Since I switched to JED some time ago I haven't used MicroEMACS, so have little motivation in working through this just for a single port. If anyone still using uemacs would like to take over as maintainer, that'd be cool. Update: Joseph Benden submitted a patch already! http://www.freebsd.org/cgi/query-pr.cgi?pr=189689 Thanks Joseph. ___ 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: pkg audit -F segfault
On Tue 2013-12-10 21:53:16 UTC-0500, Phil Stone (phil.st...@gmx.com) wrote:
Hi,
I've just installed pkg-1.2.3 on FreeBSD 8.4-RELEASE-p6.
It's also segfaulting on 9.2-RELEASE-p2 here.
I noticed the segfault in my syslog just now, since pkg audit -F is
run daily from /usr/local/etc/periodic/security/410.pkg-audit.
Running the command pkg audit -F causes a segfault:
# pkg audit -F
Vulnxml file up-to-date.
Segmentation fault (core dumped)
#
(gdb) set args audit -F
(gdb) r
Starting program: /usr/ports/ports-mgmt/pkg/work/pkg-1.2.3/pkg/pkg audit -F
[New LWP 101360]
[New Thread 803407400 (LWP 101360/pkg)]
Vulnxml file up-to-date.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 803407400 (LWP 101360/pkg)]
0x000800ddb130 in archive_read_free () from /usr/lib/libarchive.so.5
(gdb) bt
#0 0x000800ddb130 in archive_read_free () from /usr/lib/libarchive.so.5
#1 0x00407772 in fetch_and_extract (src=0x803425070
http://www.vuxml.org/freebsd/vuln.xml.bz2;,
dest=0x7fffcfd0 /var/db/pkg/vuln.xml, xml=true) at audit.c:211
#2 0x0040902e in exec_audit (argc=0, argv=0x7fffd530) at
audit.c:882
#3 0x004105b0 in main (argc=2, argv=0x7fffd520) at main.c:754
Implementing the following patch solves the issue:
--- audit_orig.c 2013-12-11 03:36:21.390625000 +0100
+++ audit.c 2013-12-11 03:36:59.796875000 +0100
@@ -206,9 +206,10 @@
cleanup:
unlink(tmp);
- if (a != NULL)
+ if (a != NULL) {
archive_read_close(a);
archive_read_free(a);
+ }
if (fd = 0)
close(fd);
Thanks in advance for your help.
Phil
Indeed, adding the erroneously missing braces fixes the problem here.
Thanks Phil,
Regards
Andrew
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
portmaster glitch with /usr/ports/MOVED
I made the mistake of telling portmaster-3.17.3 to build mail/mutt-devel instead of mail/mutt. Evidently portmaster sees the port has moved based on /usr/ports/MOVED, which is good, but it erroneously calls pkg, apparently without arguments, and the remaining output looks a bit broken. Regards Andrew # portmaster mail/mutt-devel === The mail/mutt-devel port moved to mail/mutt === Reason: mail/mutt-devel is ready for primetime === Exiting Usage: pkg info pkg-name pkg info -a pkg info [-AbBDdefgiIklOqRrsx] pkg-name pkg info [-AbBDdfIlqRrs] -F pkg-file For more information see 'pkg help info'. === The second argument to -o can be a package name, or a port directory from /usr/ports does not seem to be installed, or listed as a dependency === No valid installed port, or port directory given === Try portmaster --help === Killing background jobs Terminated === Exiting ___ 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: www/aria2 dependencies lang/llvm33 build error
On Sun 2013-11-17 14:15:02 UTC+0100, Michael Gmelin (free...@grem.de) wrote: www/aria2 1.18.1 requires lang/clang33. Is this really necessary? Previous aria2 versions didn't require clang. I've now had a chance to check the aria2 sources and evidently it now requires C++11 support, which I find surprising, but that's progress I suppose... From a developer's standpoint this makes a lot of sense, since C++11 is more productive and a lot more fun to use. Sounds good. I just wonder about the logic behind doing that for a minor 1.17 - 1.18 release though. I just built sudo successfully on 9.1 using system clang 3.1 and CXX=clang++ CXXFLAGS+=-std=c++11 -stdlib=libc++ Yeah, I have no problem building sudo with clang. The sudo code is all C though, not C++. I upgraded from FreeBSD 8.4-REL to 9.2-REL during the week. Trying to build aria2 with or without the above in /etc/make.conf still results in: checking whether clang++ supports C++11 features by default... no The only place I can get aria2 1.18 to build successfully is under FreeBSD 10.0-BETA(3) (tested in a VM). So that tends to rule out aria2's configure script being broken at least. For the time being I'm using portdowngrade to install aria2 1.17. Not a big deal, and I suspect I'll be upgrading my servers from FreeBSD 9.2 to 10.x sometime early next year, whereby this issue will fix itself... The problem you're facing is probably the lack of libc++, which contains all the C++11 library features. You can use C++11 using the old gcc standard C++ library, but then you won't have access to about 2/3 of the new features which are all implemented in the library. To get those on a system that doesn't ship with clang already you could install devel/libc++. Unfortunately this won't build on older hosts due to the lack of aligned_alloc. While this can be worked around by defining your local aligned_alloc, you'll probably trip over the lack of xlocale(3) support, which is required to build libc++ successfully and first appeared in 9.1. Out of curiosity I tried building devel/libc++ under 9.2 but it failed with: Shared object libz.so.5 not found, required by libLLVM-3.3.so Evidently the fix is to add libz.so.5 libz.so to /etc/libmap.conf. I then point /etc/make.conf to lang/clang33: CC=clang33 CXX=clang++33 CPP=clang++33 -E aria2 1.18's configure still breaks though, darn: checking whether clang++33 supports C++11 features by default... no So basically I see two options for you: - Update to 9.2-RELEASE, 8.4 will be EoL soon anyway FWIW the reason I stuck with 8.4 was because it's EoL in June 2015, whereas 9.2 is EoL in September 2014. http://www.freebsd.org/security/security.html#sup Upgrading from 8.4 to 9.2 was surprisingly painless though, so I'm not as concerned with future upgrades. My main worry was root on ZFS, and whether the pool would be bootable from the newer kernel. It all went swimmingly though. Disk performance seems to have improved a little too which is nice. - Try building aria with a recent gcc instead I've had no success with that either! Thanks for the pointers, though. Regards Andrew ___ 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: www/aria2 dependencies lang/llvm33 build error
On Fri 2013-11-22 15:37:56 UTC+0100, Michael Gmelin (free...@grem.de) wrote: I just built sudo successfully on 9.1 using system clang 3.1 and CXX=clang++ CXXFLAGS+=-std=c++11 -stdlib=libc++ Yeah, I have no problem building sudo with clang. The sudo code is all C though, not C++. Well, that was supposed to be aria2 and not sudo (no idea why I wrote sudo in the first place, probably multitasking when I shouldn't have). A tried it specifically because it didn't build about two weeks earlier due to being incompatible with C++11. So it went straight from not working with C++11 to requiring C++11. Good times :) Ah. Then the obvious question is... How did you get aria2 to build in 9.1 when I can't get it to build in 9.2? ;-) Regards Andrew ___ 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: www/aria2 dependencies lang/llvm33 build error
On Fri 2013-11-22 15:51:14 UTC+0100, Michael Gmelin (free...@grem.de) wrote: Then the obvious question is... How did you get aria2 to build in 9.1 when I can't get it to build in 9.2? ;-) I built 9.1 from source using: WITH_LIBCPLUSPLUS=YES (and later WITH_CLANG_EXTRAS=1) (make buildworld installworld kernel) So I've got libc++. All ports are built using: CC=clang CXX=clang++ CXXFLAGS+= -std=c++11 -stdlib=libc++ CPP=clang-cpp I see! I'll give that a try if I get some free time, although the effort required seems excessive just to build the latest aria2 . :) Thanks Michael, Regards Andrew ___ 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: www/aria2 dependencies lang/llvm33 build error
Following up on my question from yesterday... On Sun 2013-11-17 00:22:13 UTC+1100, andrew clarke (m...@ozzmosis.com) wrote: I'm running FreeBSD 8.4-RELEASE-p4. www/aria2 1.18.1 requires lang/clang33. Is this really necessary? Previous aria2 versions didn't require clang. I've now had a chance to check the aria2 sources and evidently it now requires C++11 support, which I find surprising, but that's progress I suppose... If so, I already have lang/clang-devel (3.4) installed, but the port still wants to build lang/clang33, which of course requires devel/llvm33. I've just noticed for lang/clang-devel, the actual clang binary has been recently renamed to clang-devel, but this isn't mentioned in /usr/ports/UPDATING. If I set CXX=clang++-devel in make.conf, the aria2 configure script still fails though, complaining of missing C++11 support. Odd. However on 8.4-REL, currently llvm33 fails to build: gmake[1]: Leaving directory `/usr/ports/devel/llvm33/work/llvm-3.3.src/bindings' llvm[0]: * Completed Release Build sphinx-build -b man -d _build/doctrees . _build/man Traceback (most recent call last): File /usr/local/bin/sphinx-build, line 5, in module from pkg_resources import load_entry_point File build/bdist.freebsd-8.3-RELEASE-p3-amd64/egg/pkg_resources.py, line 2805, in module File build/bdist.freebsd-8.3-RELEASE-p3-amd64/egg/pkg_resources.py, line 696, in require File build/bdist.freebsd-8.3-RELEASE-p3-amd64/egg/pkg_resources.py, line 594, in resolve pkg_resources.DistributionNotFound: markupsafe gmake: *** [man] Error 1 *** Error code 2 On a hunch I tried reinstalling textproc/py-sphinx, which failed with the same error. Evidently py-sphinx is missing a dependency on textproc/py-MarkupSafe. Once markupsafe is installed I could build install llvm33 clang33. But even so, the aria2 build still complains about missing C++11 support: checking whether /usr/local/bin/clang++33 supports C++11 features by default... no checking whether /usr/local/bin/clang++33 supports C++11 features with -std=c++11 ... no checking whether /usr/local/bin/clang++33 supports C++11 features with -std=c++11 -stdlib=libc++... no checking whether /usr/local/bin/clang++33 supports C++11 features with -std=c++0x ... no checking whether /usr/local/bin/clang++33 supports C++11 features with -std=c++0x -stdlib=libc++... no configure: error: *** A compiler with support for C++11 language features is required. === Script configure failed unexpectedly. Any suggestions? Regards Andrew ___ 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
www/aria2 dependencies lang/llvm33 build error
Hi, I'm running FreeBSD 8.4-RELEASE-p4. www/aria2 1.18.1 requires lang/clang33. Is this really necessary? Previous aria2 versions didn't require clang. If so, I already have lang/clang-devel (3.4) installed, but the port still wants to build lang/clang33, which of course requires devel/llvm33. However on 8.4-REL, currently llvm33 fails to build: gmake[1]: Leaving directory `/usr/ports/devel/llvm33/work/llvm-3.3.src/bindings' llvm[0]: * Completed Release Build sphinx-build -b man -d _build/doctrees . _build/man Traceback (most recent call last): File /usr/local/bin/sphinx-build, line 5, in module from pkg_resources import load_entry_point File build/bdist.freebsd-8.3-RELEASE-p3-amd64/egg/pkg_resources.py, line 2805, in module File build/bdist.freebsd-8.3-RELEASE-p3-amd64/egg/pkg_resources.py, line 696, in require File build/bdist.freebsd-8.3-RELEASE-p3-amd64/egg/pkg_resources.py, line 594, in resolve pkg_resources.DistributionNotFound: markupsafe gmake: *** [man] Error 1 *** Error code 2 Stop in /usr/ports/devel/llvm33. *** Error code 1 Thanks. Regards Andrew ___ 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: Should /usr/bin/perl be a link to /usr/local/bin/perl ?
On Mon 2013-10-21 09:47:29 UTC-0700, Yuri (y...@rawbw.com) wrote: I found that many ports specify /usr/bin/perl as an interpreter. This comes from Linux. Examples: valgrind-snapshot, windowmaker, enscript-a4, a2ps, svgalib /usr/bin/perl isn't installed by perl port. There are several solutions, in the order of increasing complexity of solution: 1. Install the link /usr/bin/perl (hackish, but it will fix many broken ports in one shot) 2. Make a package scripts check for interpreter and break the install of offending packages 3. Fix all offending packages Which solution should be preferred in your opinion? Are you aware the Perl interpreter ports already have a make option to create symlinks in /usr/bin? $ pwd /usr/ports/lang/perl5.14 $ make showconfig | grep USE_PERL USE_PERL=on: Rewrite links in /usr/bin $ ls -l /usr/bin/perl lrwxr-xr-x 1 root wheel 25 10 Oct 14:04 /usr/bin/perl - /usr/local/bin/perl5.14.4 Regards Andrew ___ 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
net/tcpflow
Maybe it would be useful to have a make config option to disable
cairo in the net/tcpflow port? The Cairo dependency pulls in about
twenty X11 libraries that I'd prefer not to install on my server.
This was my quick dirty Makefile hack to disable Cairo:
--- Makefile.orig 2013-06-12 04:41:45.0 +1000
+++ Makefile2013-06-12 20:37:32.283320340 +1000
@@ -12,7 +12,7 @@
LICENSE= GPLv3
BUILD_DEPENDS=
${LOCALBASE}/include/boost/icl/interval.hpp:${PORTSDIR}/devel/boost-libs
-LIB_DEPENDS= cairo:${PORTSDIR}/graphics/cairo
+#LIB_DEPENDS= cairo:${PORTSDIR}/graphics/cairo
GNU_CONFIGURE= yes
CPPFLAGS+= -I${LOCALBASE}/include
Thanks,
Regards
Andrew
___
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/tcpflow
On Wed 2013-06-12 13:48:31 UTC+0200, Antoine Brodin (anto...@freebsd.org) wrote: Yes, cairo is needed to have a nice 1 page PDF summary. You can compile cairo with custom options if you don't want x11 etc. Ah, you're right. I wasn't expecting that. That removes the dependency count considerably. 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: net/tcpflow
On Wed 2013-06-12 22:38:47 UTC+1000, andrew clarke (m...@ozzmosis.com) wrote: Ah, you're right. I wasn't expecting that. That removes the dependency count considerably. Thank you! Erm. s/removes/lowers/ :-) ___ 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: State of pkgng?
On Wed 2013-02-20 17:45:52 UTC-0800, Darren Pilgrim (list_free...@bluerosetech.com) wrote: Reading the pkgng page on the wiki: As a consequence of the security incident on 11th November 2012, for the time being pre-compiled packages for pkgng are not available from any official FreeBSD repository. [...] Target dates for when service may be resumed have not been released. Is that still the case? Is pkgng presently a non-starter? Just to be clear, pkgng is not broken. You can still use it with the Ports tree or use it to install locally-built packages. ___ 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: 'pkg check -d' showing missing dependencies after upgrading lang/perl
On Wed 2012-10-24 14:48:59 UTC-0500, Mark Felder (f...@feld.me) wrote: I noticed at some point after installing and switching to pkgng, then upgrading Perl from 5.12 to 5.14 with 'portmaster -o lang/perl5.14 lang/perl5.12', the 'pkg check -d' command would still list some ports with perl5.12 as a missing dependency: What I failed to mention was that at this point if I ran 'portmaster irssi-scripts' to reinstall that port, the dependency on perl5.12 would remain after irssi-scripts had been reinstalled. Initially I thought this was because irssi-scripts depends on irssi, which also at the time had dependencies on both perl5.12 perl5.14. So then I ran 'portmaster irssi' to reinstall irssi, but the perl5.12 dependency still remained. At that point I got frustrated and just ran 'pkg del' on all of them, then began reinstalling them again. I think this is a bug with portmaster. Portmaster should have run this command on your behalf: # pkg set -o lang/perl5.14:lang/perl5.12 Ah! Thanks for that. I've since read the man page for 'pkg set' which has: # pkg set -o lang/perl5.12:lang/perl5.14 which I think is the correct order. So I'll make a note of that. But hopefully I won't have to do that again. This runs a query in the pkg sqlite database and update dependencies. This clearly didn't happen for you yet, so thats where your errors come from. Well I think it worked correctly for most ports, just those few that I listed earlier remained problematic and I couldn't figure out why. I've since tried to replicate it in a VM and got nowhere. Everything worked OK, so I'm a bit baffled. Thanks again, Regards Andrew ___ 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] fusefs-ntfs and fusefs-libs updates
On Thu 2012-10-25 16:44:08 UTC+0200, Dominic Fandrey (kamik...@bsdforen.de) wrote: Yes, I'm aware of the problems. We are working on making the fuse import from head work on older releases and update the fusefs-kmod with that. Also we are currently looking into the problem why certain fusefs filesystems don't work with the current versions in ports. Oh, thanks! If you need me to test anything ... Likewise. Am particularly keen on getting fusefs-encfs to work without segfaulting. Currently as a workaround I'm still using the older fusefs-kmod-0.3.9.p1.20080208_10, instead of _11. ___ 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
'pkg check -d' showing missing dependencies after upgrading lang/perl
I noticed at some point after installing and switching to pkgng, then
upgrading Perl from 5.12 to 5.14 with 'portmaster -o lang/perl5.14
lang/perl5.12', the 'pkg check -d' command would still list some ports
with perl5.12 as a missing dependency:
devel/gamin has a missing dependency: lang/perl5.12
devel/gio-fam-backend has a missing dependency: lang/perl5.12
irc/irssi has a missing dependency: lang/perl5.12
irc/irssi-scripts has a missing dependency: lang/perl5.12
mail/maildrop has a missing dependency: lang/perl5.12
misc/mc has a missing dependency: lang/perl5.12
mail/p5-Mail-SpamAssassin has a missing dependency: lang/perl5.12
Running 'pkg info -d irssi-scripts' would list both perl-5.12 and
perl-5.14.
Not being too familiar with pkgng's internals I decided I'd just do
pkg del gamin gio-fam-backend irssi (etc)
then rebuild reinstall those ports with portmaster, but presumably
there's a better alternative. ('pkg del perl5.12' wasn't it, though. :)
Also I can't say for certain whether I did something incorrectly
(wrong order?) with the Perl upgrade or if portmaster is to blame for
the duelling dependencies. So consider this more of an observation
than a bug report - at least until I can reproduce the problem in a VM
when I'm more awake. :-)
tl;dr: this may be my fault.
Regards
Andrew
___
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
editors/uemacs
I still use MicroEMACS occasionally. I noticed this in the Makefile for the FreeBSD port (editors/uemacs): DEPRECATED= No more public distfiles EXPIRATION_DATE= 2012-10-20 Evidently the distfile download links are broken: ftp://www.aquest.com/pub/uemacs400/disk2/ue400dev.zip is extremely slow, then stalls completely, at least for me. http://www.aquest.com/downloads/UE400DEV.ZIP does not match the original size/checksum. The author, Daniel M. Lawrence, passed away in 2010. Is it reasonable to provide an alternate download location? http://ozzmosis.com/uemacs/ue400dev.zip Regards Andrew ___ 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: editors/uemacs
On Fri 2012-10-19 13:18:32 UTC-0400, Eitan Adler (li...@eitanadler.com) wrote: Is it reasonable to provide an alternate download location? absolutely. would you like to help maintain the port? As there does not appear to be active development this would mostly be updating the port to new conventions over time. Sounds simple enough. I'll do it :-) http://ozzmosis.com/uemacs/ue400dev.zip in either case please let me know and I'll update the port. Regards Andrew ___ 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
mail/maildrop-2.6.0's maildirmake
I just discovered the maildirmake command has been inexplicably renamed maildrop-maildirmake between maildrop-2.5.5 and maildrop-2.6.0, which broke my maildrop rules. Maybe this should go into /usr/ports/UPDATING? Cheers. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: fusefs-encfs-1.7.4_1
On Thu 2012-09-27 13:09:09 UTC-0300, Joseph Mingrone (j...@ftfl.ca) wrote: It looks like encfs is crashing. ... zsh: segmentation fault (core dumped) encfs -d /usr/home/jrm/.crypt /usr/home/jrm/files/crypt I'm also experiencing segfaults with encfs on 8.3-RELEASE-p3 amd64. fusefs-kmod-0.3.9.p1.20080208_11 seems to be the culprit. Reverting back to 0.3.9.p1.20080208_10 stops the segfaults. ___ 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: Introducing fpart - a file partitioning tool
On Fri 2012-01-06 11:36:56 UTC+0100, Ganael LAPLANCHE (ganael.laplan...@martymac.org) wrote: Have you ever wondered how you could split a file tree into parts of the same size, or into parts with a limited size or file number ? I have developed a small BSD-licensed tool called fpart that can do that for you (see http://contribs.martymac.org and https://sourceforge.net/projects/fpart). This small C program will crawl a given set of file or directory paths, organize them and print resulting partitions. This can be useful to e.g. launch several rsync(1) in parallel or store files on media of limited size. Interesting! Thanks. I see there's a similar program called GAFFitter in the Ports tree (sysutils/gaffitter)... Genetic Algorithm File Fitter, or just GAFFitter, is a command-line software written in C++ that arranges--via a genetic algorithm--an input list of items or files/directories into volumes of a certain capacity (target), such as CD or DVD, in a way that the total wastage is minimized. By smartly arranging the input list, GAFFitter fits better the given items and so optimizes (reduces) the number of required volumes to pack them. Currently, GAFFitter runs on GNU/Linux and other POSIX systems, but it is designed in such manner that should be easily extended to non-POSIX operating environment. http://gaffitter.sourceforge.net/ ___ 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
editors/nano-devel makefile typo
The makefile for editors/nano-devel has a trivial typo that you may
have already fixed by the time you read this. Below is a patch to fix
it...
Aside, I'm not sure the ports tree supports FreeBSD pre-7.0, so the OS
version check may be redundant?
--- Makefile.orig 2011-11-07 15:24:54.0 +1100
+++ Makefile2011-11-07 16:23:25.414806093 +1100
@@ -36,7 +36,7 @@
.include bsd.port.pre.mk
# requires wide character curses
-.if (${OSVERSION} 700033
+.if (${OSVERSION} 700033)
CONFIGURE_ARGS+=--disable-utf8
.else
CONFIGURE_ARGS+=--enable-utf8
___
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: Replacing procmail with maildrop
On Sun 2011-09-25 22:01:13 UTC-0600, Warren Block (wbl...@wonkity.com) wrote: Recent discussion here about the desirability of replacing procmail finally convinced me to switch to maildrop. It turned out to be relatively painless. I took some notes that may be helpful for others considering the change: http://www.wonkity.com/~wblock/docs/html/maildrop.html Thanks for that. Looks like I'll be migrating across to maildrop in the next week or so :-) Something you may want to add is that if you use Maildir format and have this in ~/.procmailrc: DEFAULT=$HOME/Maildir/ You need the equivalent for maildrop's ~/.mailfilter: DEFAULT=$HOME/Maildir/ Without this, messages that were not filtered (ie. fell through) will be appended to the mbox file, /var/mail/$USER. Regards Andrew ___ 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
Upgrading sshguard
Hi, A recent FreeBSD ports change upgrades sshguard to 1.5. I'm not sure about other variants, but with sshguard-ipfw at least, from what I can tell, installing the port erroneously comments-out the following existing line from /etc/syslog.conf: auth.info;authpriv.info | exec /usr/local/sbin/sshguard To get sshguard-ipfw to work again you need to uncomment the above line and restart syslogd, eg. sudo service syslogd restart. Incidentally version 1.5 is somewhat more noisy than the previous version, sending this to /var/log/messages once every few hours: Jun 16 01:00:00 blizzard sshguard[7655]: Got exit signal, flushing blocked addresses and exiting... Jun 16 01:00:00 blizzard sshguard[8080]: Started successfully [(a,p,s)=(40, 420, 1200)], now ready to scan. (obviously a separate issue to the syslog.conf problem above) Regards Andrew ___ 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: Portmaster 3.1 upgrade
On Sun 2010-10-31 17:57:52 UTC+0100, Alexandre (axel...@ymail.com) wrote: I read in /usr/ports/UPGRADING the instructions to properly upgrade PORTMASTER 3.1. It is written to do : # pkg_delete -f portmaster* # cd /usr/ports/ports-mgmt/portmaster make clean make install clean But when I type the first one, I got the message : pkg_delete: No match. Your shell is trying to do pathname globbing. http://en.wikipedia.org/wiki/Glob_(programming) Instead, use: pkg_delete -f 'portmaster*' or: pkg_delete -f portmaster\* UPDATING should probably be amended upstream to correct this... Regards Andrew ___ 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: Portmaster 3.1 upgrade
On Sun 2010-10-31 19:27:17 UTC+0100, Michal Varga (varga.mic...@gmail.com) wrote: UPDATING should probably be amended upstream to correct this... Regards Andrew While I'm certainly no authority on the issue, I think that's the wrong approach and generally (really not speaking about any specific case) - people, or in this case, system administrators, should know how to operate their working environment and don't just blindly enter commands as they found them, without trying to understand what will happen next and/or how it will get interpreted. Indeed - that's why I wrote probably. I can imagine arguments for and against, as you describe... ___ 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
devel/autotools267 install error
Hi, $ uname -a FreeBSD blizzard.phoenix 7.3-RELEASE-p2 FreeBSD 7.3-RELEASE-p2 #0: Mon Jul 12 19:04:04 UTC 2010 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 $ pwd /usr/ports/devel/autoconf267 $ make reinstall : install -o root -g wheel -m 444 ./autoconf-2.67.info '/usr/local/share/info' : gmake[1]: Leaving directory /usr/ports/devel/autoconf267/work/autoconf-2.67' install-info --quiet /usr/local/info/autoconf-2.67.info /usr/local/info/dir install-info: No such file or directory for /usr/local/info/autoconf-2.67.info *** Error code 1 (The port is installing to /usr/local/share/info/autoconf-2.67.info but then looking for /usr/local/info/autoconf-2.67.info.) Thanks, Regards Andrew ___ 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
textproc/uni2ascii build failure on FreeBSD 7.3
Hi, uni2ascii no longer builds on FreeBSD 7.3: cc -DNEWSUMMARY -O2 -fno-strict-aliasing -pipe -o ascii2uni ascii2uni.o enttbl.o GetWord.o putu8.o SetFormat.o ascii2uni.o(.text+0xb23): In function main': : undefined reference to getline' Quoting the ChangeLog: 2010-08-29 Bill Poser po...@khunekcho.khunek * ascii2uni.c: Removed getline.c dependent on GNU_SOURCE since getline is standard as of POSIX2008. Relying on POSIX2008 support may be a bit ambitious. Thanks, Regards Andrew ___ 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
devel/subversion
Can anyone confirm that subversion fails to build with www/neon28 and requires www/neon29? This is not mentioned in UPDATING. Running FreeBSD 7.3-REL. Thanks, Regards Andrew ___ 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: devel/subversion
On Wed 2010-07-07 02:06:39 UTC+1000, andrew clarke (m...@ozzmosis.com) wrote: Can anyone confirm that subversion fails to build with www/neon28 and requires www/neon29? This is not mentioned in UPDATING. Building subversion 1.6.11_3 with neon28-0.28.6_1 installed: === Configuring for subversion-1.6.11_3 configure: Configuring Subversion 1.6.11 ... checking for pkg-config... /usr/local/bin/pkg-config configure: checking neon library checking neon library version... 0.28.6 configure: error: cannot find Neon === Script configure failed unexpectedly. Please report the problem to l...@freebsd.org [maintainer] and attach the /usr/ports/devel/subversion/work/subversion-1.6.11/config.log including the Looking at config.log: configure:5698: cc -o conftest -O2 -fno-strict-aliasing -pipe -g -O2 -I/usr/local/include/neon -L/usr/local/lib -L/usr/local/lib/db42 conftest.c -L/usr/local/lib -lneon 5 /usr/local/lib/libneon.so: undefined reference to `SSL_SESSION_cmp' At this point I thought I should try rebuilding openssl-1.0.0_2, however while that's re-building I decide to grep for SSL_SESSION_cmp in the neon29-0.29.3_1 sources and find this comment: OpenSSL 1.0 removed SSL_SESSION_cmp for no apparent reason with an apparent fix. So my conclusion is that building subversion needs neon29 to be installed if you're using OpenSSL 1.0. And this should probably be mentioned in UPDATING... Thanks, Regards Andrew ___ 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: Call for testers: www/shellinabox (Shell in a Box)
On Fri 2010-06-25 00:51:12 UTC+0200, Olivier Cochard-Labb? (oliv...@freenas.org) wrote: I've just finished my port of Shell in a Box: It's a secure web server that provide ajax terminal emulator. Very cool :-) More information on the official website: http://code.google.com/p/shellinabox/ Your port builds OK and seems to run fine here under FreeBSD 7.3-RELEASE. Thanks Olivier. ___ 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: MPlayer - Invalid and inefficient vfw-avi packed B frames detected
On Sat 2010-05-22 23:06:11 UTC+0900, Byung-Hee HWANG (b...@izb.knu.ac.kr) wrote: Recently, i upgraded packages all by csup(fetch: 2010-05-14) + portupgrade. I did mplayer, too. After all that, when i launched mplayer with some avi movie file, mplayer said Invalid and inefficient vfw-avi packed B frames detected. I don't use MPlayer in FreeBSD but I've seen this with recent Linux Windows builds, but only with some AVI files (that were not made by me). It was only a warning message and the videos continued to play without any noticable errors. ___ 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
gio-querymodules in devel/glib20
Running FreeBSD 7.3-REL, while building glib-2.24.1 the post-install part stalls, so the port never finishes installing. The offending line is: /usr/local/bin/gio-querymodules /usr/local/lib/gio/modules/ Running this manually produces the same result - gio-querymodules stalls with no output. ___ 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
misc/mc build failure with portconf installed
Hi,
=== Configuring for mc-4.7.0.1
configure: error: invalid variable name: +
=== Script configure failed unexpectedly.
I tracked this error down to some settings portconf-1.4 adds to
/etc/make.conf:
# Begin portconf settings
# Do not touch these lines
.if !empty(.CURDIR:M/usr/ports*) exists(/usr/local/libexec/portconf)
_PORTCONF!=/usr/local/libexec/portconf
.for i in ${_PORTCONF:S/|/ /g}
${i:S/%/ /g}
.endfor
.endif
# End portconf settings
Once I uninstall portconf, which removes the above lines from make.conf,
mc builds normally.
Regards
Andrew
___
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
editors/jed 0.99.19 freezing
Hi, After upgrading to the latest version of Jed from ports, Jed is now freezing when run from sh with the -c option: $ sh -c jed loading /usr/local/lib/jed/lib/emacs.sl I had to open another terminal and kill -9 the process. $ jed --version jed version: 0.99.19/Unix Compiled with GNU C 4.2 S-Lang version: 2.2.2 jed compile-time options: +LINE_ATTRIBUTES +BUFFER_LOCAL_VARS +SAVE_NARROW +TTY_MENUS +EMACS_LOCKING +MULTICLICK +SUBPROCESSES +DFA_SYNTAX +ABBREVS +COLOR_COLUMNS +LINE_MARKS -GPM_MOUSE +IMPORT Using JED_ROOT=/usr/local/lib/jed $ uname -a FreeBSD blizzard.phoenix 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct 2 12:21:39 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 Downgrading to jed-0.99.18_3 (but with libslang2-2.2.2 still installed) and the fault goes away. Thanks, Regards Andrew ___ 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: sqlite and tcl
On Tue 2009-11-10 15:51:11 UTC+0100, Alex Dupre (a...@freebsd.org) wrote: As you have seen, the up-to-date sqlite port requires tcl for *building*. A few of you complained about it, but I don't understand why you are not complaining about ports that have perl or python configure scripts, too ;-) In my case it was more a query about whether this new behaviour was correct, since TCL was required regardless of the TCLWRAPPER toggle in make config, and I thought that was unusual. I have no strong beliefs for or against TCL :-) ___ 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 databases/sqlite3 without TCL?
Hi, I notice TCL seems to be a dependency of sqlite3-3.6.19 even with TCL support disabled (using make config). Is this correct? This was not true for sqlite3-3.6.14.2, the previous version of databases/sqlite3 in the ports tree. 3:36 ozzmo...@blizzard [/usr/ports/databases/sqlite3]sudo make showconfig === The following configuration options are available for sqlite3-3.6.19: DEBUG=off Enable debugging verbose explain FTS3=off Enable FTS3 (Full Text Search) module RTREE=off Enable R*Tree module RAMTABLE=off Store temporary tables in RAM TCLWRAPPER=off Enable TCL wrapper METADATA=on Enable column metadata THREADSAFE=on Build thread-safe library === Use 'make config' to modify these settings 3:36 ozzmo...@blizzard [/usr/ports/databases/sqlite3]sudo make missing lang/tcl85 lang/tcl-modules 3:37 ozzmo...@blizzard [~]uname -v FreeBSD 7.2-RELEASE-p4 #0: Fri Oct 2 12:21:39 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC Thanks, Regards Andrew ___ 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/p5-Net-Twitter broken
On Thu 2009-07-30 10:07:28 UTC+0300, Sergey V. Dyatko (sergey.dya...@gmail.com) wrote: AC Warning: prerequisite MooseX::MultiInitArg 0 not found. AC Writing Makefile for Net::Twitter AC Is MooseX::MultiInitArg hidden somewhere in the ports tree? No, we haven't it. You may try install it via cpan How do I do that? ___ 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/p5-Net-Twitter broken
On Thu 2009-07-30 09:21:27 UTC+0200, Cezary Morga (c...@therek.net) wrote: Warning: prerequisite MooseX::MultiInitArg 0 not found. Writing Makefile for Net::Twitter Is MooseX::MultiInitArg hidden somewhere in the ports tree? Nope. It's a missing dependency (also visible here http://pointyhat.freebsd.org/errorlogs/i386-7-latest-logs/p5-Net-Twitter-3.03000.log). Please, fill in a PR for this. If you can prepare a proper patch for the new port and modification to net/p5-Net-Twitter/Makefile that would be even better. I'll attempt a PR, but I'm not at all competent enough in Perl to be confident in providing a patch. I have to wonder - why have these recent versions of this port been committed but not tested? If it was tested, presumably it would be flagged as BROKEN. But isn't the rationale of the Ports tree to have buildable, working software? ___ 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/p5-Net-Twitter broken
On Mon 2009-07-13 21:31:38 UTC+0200, Cezary Morga (c...@therek.net) wrote: First off, I'd start from something like following an look for any 'missing' modules, or ones that have wrong (too old) version number. cd /usr/ports/net/p5-Net-Twitter make clean configure Net::Twitter 3.03000 is now failing with a missing dependency. 16:17 ozzmo...@blizzard [/usr/ports/net/p5-Net-Twitter]sudo make clean configure === Cleaning for p5-Net-Twitter-3.03000 === Vulnerability check disabled, database not found === Extracting for p5-Net-Twitter-3.03000 = MD5 Checksum OK for Net-Twitter-3.03000.tar.gz. ... - MooseX::MultiInitArg ...missing. *** Module::AutoInstall configuration finished. Checking if your kit is complete... Looks good Warning: prerequisite MooseX::MultiInitArg 0 not found. Writing Makefile for Net::Twitter Is MooseX::MultiInitArg hidden somewhere in the ports tree? Thanks, Regards Andrew ___ 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/p5-Net-Twitter broken
On Mon 2009-07-13 21:31:38 UTC+0200, Cezary Morga (c...@therek.net) wrote:
I've been trying to get Twirssi (http://www.twirssi.com/) running
under Irssi but am encountering an error relating to Net::Twitter. My
Perl knowledge is very limited, so I'm not too sure what's going on.
The same error (below) occurs when I try to use this module from my
own program. I suspect the problem is within p5-Moose but I don't
know how to confirm this.
Strange, I had no such problem as you described.
First off, I'd start from something like following an look for any
'missing' modules, or ones that have wrong (too old) version number.
I don't think there's anything missing? My ports tree is up-to-date.
cd /usr/ports/net/p5-Net-Twitter make clean configure
Than I'd check if it passes all tests:
cd /usr/ports/net/p5-Net-Twitter make clean build
cd work/Net-Twitter-3.01000 make test
Ah, I wasn't aware of the test target. That should help.
OK, after installing devel/p5-Test-Exception, I get the same error as before:
PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.9 -MExtUtils::Command::MM -e
test_harness(0, 'inc', 'blib/lib', 'blib/arch') t/01_basic.t t/02_fails.t
t/10_net-twitter-regression.t t/11_useragent.t t/12_identica.t t/13_search.t
t/20_exceptions.t t/20_generated.t t/21_wraperror.t t/22_twitter_insanity.t
t/30_legacy.t t/99-pod_coverage.t t/99-pod_spelling.t t/99-pod_syntax.t
t/01_basic.
# Failed test 'use Net::Twitter;'
# at t/01_basic.t line 63.
# Tried to use 'Net::Twitter'.
# Error: I do not understand this option (is = bare) on attribute
(_trait_namespace) at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Attribute.pm line 79
# Moose::Meta::Attribute::new('Moose::Meta::Attribute',
'_trait_namespace', 'init_arg', undef, 'isa', 'Str', 'is', 'bare') called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Attribute.pm line 88
#
Moose::Meta::Attribute::interpolate_class_and_new('Moose::Meta::Attribute',
'_trait_namespace', 'init_arg', undef, 'isa', 'Str', 'is', 'bare') called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Class.pm line 587
[...]
Digging further, I see some potential problems with devel/p5-MooseX-Traits:
=== Configuring for p5-MooseX-Traits-0.06
Cannot determine perl version info from lib/MooseX/Traits.pm
Checking if your kit is complete...
Looks good
Warning: prerequisite Moose 0.84 not found. We have 0.81.
Warning: prerequisite ok 0 not found.
Writing Makefile for MooseX::Traits
And make test fails here, too:
PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.9 -MExtUtils::Command::MM -e
test_harness(0, 'inc', 'blib/lib', 'blib/arch') t/*.t
t/00-load.Can't locate ok.pm in @INC (@INC contains:
/spare/ports/devel/p5-MooseX-Traits/work/MooseX-Traits-0.06/inc
/spare/ports/devel/p5-MooseX-Traits/work/MooseX-Traits-0.06/blib/lib
/spare/ports/devel/p5-MooseX-Traits/work/MooseX-Traits-0.06/blib/arch
/usr/local/lib/perl5/5.8.9/BSDPAN /usr/local/lib/perl5/site_perl/5.8.9/mach
/usr/local/lib/perl5/site_perl/5.8.9 /usr/local/lib/perl5/5.8.9/mach
/usr/local/lib/perl5/5.8.9 . /usr/local/lib/perl5/5.8.9/BSDPAN
/usr/local/lib/perl5/site_perl/5.8.9/mach /usr/local/lib/perl5/site_perl/5.8.9
/usr/local/lib/perl5/5.8.9/mach /usr/local/lib/perl5/5.8.9 .) at t/00-load.t
line 6.
BEGIN failed--compilation aborted at t/00-load.t line 6.
# Looks like your test exited with 2 before it could output anything.
dubious
Test returned status 2 (wstat 512, 0x200)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/basic...I do not understand this option (is = bare) on attribute
(_trait_namespace) at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Attribute.pm line 79
Moose::Meta::Attribute::new('Moose::Meta::Attribute',
'_trait_namespace', 'init_arg', undef, 'isa', 'Str', 'is', 'bare') called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Attribute.pm line 88
[...]
Stop in /usr/ports/devel/p5-MooseX-Traits/work/MooseX-Traits-0.06.
Regards
Andrew
___
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/p5-Net-Twitter broken
I've been trying to get Twirssi (http://www.twirssi.com/) running under Irssi but am encountering an error relating to Net::Twitter. My Perl knowledge is very limited, so I'm not too sure what's going on. The same error (below) occurs when I try to use this module from my own program. I suspect the problem is within p5-Moose but I don't know how to confirm this. Some further progress. I bumped the version number of the following ports by hand-editing their corresponding Makefiles, and deleting the distinfo files. Now both Net::Twitter and Twirssi are working again. p5-Class-MOP-0.88 succeeds index (index has 0.86) p5-Moose-0.84 succeeds index (index has 0.81) So I guess these need to be committed to the ports tree at some point. :) Presumably portsnap will overwrite my Makefile changes when there are newer files available. Regards Andrew ___ 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
net/p5-Net-Twitter broken
FreeBSD blizzard.phoenix 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24
00:57:44 UTC 2009
r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386
p5-Net-Twitter-3.01000 = up-to-date with index
p5-Moose-0.81 = up-to-date with index
p5-MooseX-Traits-0.06 = up-to-date with index
I've been trying to get Twirssi (http://www.twirssi.com/) running
under Irssi but am encountering an error relating to Net::Twitter. My
Perl knowledge is very limited, so I'm not too sure what's going on.
The same error (below) occurs when I try to use this module from my
own program. I suspect the problem is within p5-Moose but I don't
know how to confirm this.
12:28 ozzmo...@blizzard [~/src/perl]cat twitter-test.pl
use Net::Twitter;
12:28 ozzmo...@blizzard [~/src/perl]perl twitter-test.pl
I do not understand this option (is = bare) on attribute (_trait_namespace) at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Attribute.pm line 79
Moose::Meta::Attribute::new('Moose::Meta::Attribute',
'_trait_namespace', 'init_arg', undef, 'isa', 'Str', 'is', 'bare') called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Attribute.pm line 88
Moose::Meta::Attribute::interpolate_class_and_new('Moose::Meta::Attribute',
'_trait_namespace', 'init_arg', undef, 'isa', 'Str', 'is', 'bare') called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Class.pm line 587
Moose::Meta::Class::_process_new_attribute('Moose::Meta::Class=HASH(0x85fc8b0)',
'_trait_namespace', 'init_arg', undef, 'isa', 'Str', 'is', 'bare') called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Class.pm line 580
Moose::Meta::Class::_process_attribute('Moose::Meta::Class=HASH(0x85fc8b0)',
'_trait_namespace', 'HASH(0x878ce1c)') called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Class.pm line 261
Moose::Meta::Class::add_attribute('Moose::Meta::Class=HASH(0x85fc8b0)',
'_trait_namespace', 'HASH(0x878ce1c)') called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Role/Application/ToClass.pm
line 122
Moose::Meta::Role::Application::ToClass::apply_attributes('Moose::Meta::Role::Application::ToClass=HASH(0x8776070)',
'Moose::Meta::Role=HASH(0x8789d74)', 'Moose::Meta::Class=HASH(0x85fc8b0)')
called at /usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Role/Application.pm
line 62
Moose::Meta::Role::Application::apply('Moose::Meta::Role::Application::ToClass=HASH(0x8776070)',
'Moose::Meta::Role=HASH(0x8789d74)', 'Moose::Meta::Class=HASH(0x85fc8b0)')
called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Role/Application/ToClass.pm
line 31
Moose::Meta::Role::Application::ToClass::apply('Moose::Meta::Role::Application::ToClass=HASH(0x8776070)',
'Moose::Meta::Role=HASH(0x8789d74)', 'Moose::Meta::Class=HASH(0x85fc8b0)')
called at /usr/local/lib/perl5/site_perl/5.8.9/Moose/Meta/Role.pm line 486
Moose::Meta::Role::apply('Moose::Meta::Role=HASH(0x8789d74)',
'Moose::Meta::Class=HASH(0x85fc8b0)') called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Util.pm line 117
Moose::Util::_apply_all_roles('Moose::Meta::Class=HASH(0x85fc8b0)',
'CODE(0x846f688)', 'MooseX::Traits') called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Util.pm line 82
Moose::Util::apply_all_roles('Moose::Meta::Class=HASH(0x85fc8b0)',
'MooseX::Traits') called at /usr/local/lib/perl5/site_perl/5.8.9/Moose.pm line
62
Moose::with('Net::Twitter::Core', 'MooseX::Traits') called at
/usr/local/lib/perl5/site_perl/5.8.9/Moose/Exporter.pm line 206
Moose::with('MooseX::Traits') called at
/usr/local/lib/perl5/site_perl/5.8.9/Net/Twitter/Core.pm line 11
require Net/Twitter/Core.pm called at
/usr/local/lib/perl5/site_perl/5.8.9/Net/Twitter.pm line 5
Net::Twitter::BEGIN() called at
/usr/local/lib/perl5/site_perl/5.8.9/Net/Twitter/Core.pm line 0
eval {...} called at
/usr/local/lib/perl5/site_perl/5.8.9/Net/Twitter/Core.pm line 0
require Net/Twitter.pm called at twitter-test.pl line 1
main::BEGIN() called at
/usr/local/lib/perl5/site_perl/5.8.9/Net/Twitter/Core.pm line 0
eval {...} called at
/usr/local/lib/perl5/site_perl/5.8.9/Net/Twitter/Core.pm line 0
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.8.9/Net/Twitter.pm line 5.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.8.9/Net/Twitter.pm line 5.
Compilation failed in require at twitter-test.pl line 1.
BEGIN failed--compilation aborted at twitter-test.pl line 1.
Thanks,
Regards
Andrew
___
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
www/youtube_dl build failure
On FreeBSD 7.2-REL: 16:40 ozzmo...@blizzard [/usr/ports/www/youtube_dl]sudo make === Vulnerability check disabled, database not found === Extracting for youtube_dl-2009.05.30_1 cannot open 2009.05.30/youtube-dl: No such file or directory *** Error code 2 Stop in /usr/ports/www/youtube_dl. Thanks, Regards Andrew ___ 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
misc/e2fsprogs-libuuid build failure
Hi, misc/e2fsprogs-libuuid is fails to build on my FreeBSD 6.4 machine: # uname -a FreeBSD blizzard.phoenix 6.4-RELEASE-p1 FreeBSD 6.4-RELEASE-p1 #0: Sun Dec 21 07:56:41 UTC 2008 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 # pwd /usr/ports/misc/e2fsprogs-libuuid # make === Vulnerability check disabled, database not found === Found saved configuration for e2fsprogs-libuuid-1.41.3_1 === Extracting for e2fsprogs-libuuid-1.41.5 = MD5 Checksum OK for e2fsprogs-1.41.5.tar.gz. ... gmake[1]: Leaving directory `/usr/ports/misc/e2fsprogs-libuuid/work/e2fsprogs-1.41.5/lib/uuid' cd /usr/ports/misc/e2fsprogs-libuuid/work/e2fsprogs-1.41.5/misc make uuidgen uuidgen.1 uuidd uuidd.8 CC ./uuidgen.c LD uuidgen SUBST uuidgen.1 CC uuidd.c LD uuidd SUBST uuidd.8 cd /usr/ports/misc/e2fsprogs-libuuid/work/e2fsprogs-1.41.5/lib/uuid make check LD_LIBRARY_PATH=../../lib DYLD_LIBRARY_PATH=../../lib ./tst_uuid UUID generate = ade56da6-e474-4020-a894-332975eea206 UUID: ade56da6e4744020a894332975eea206 UUID type = 4, UUID variant = 1 UUID random string = d5667181-163a-46c8-9733-c62173befd30 UUID: d5667181163a46c89733c62173befd30 UUID type = 4, UUID variant = 1 The build consistently stalls at this point. The only exit is with Ctrl+C. /usr/bin/top shows: PID USERNAMETHR PRI NICE SIZERES STATETIME WCPU COMMAND 65835 root 1 1200 1276K 732K RUN 0:23 92.54% tst_uuid Thanks, Regards Andrew ___ 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
textproc/asciidoc port with shells/bash dependency
Hi, With the recent problems involving the FreeBSD port of bash-4.0 got me curious as to why the bash shell was installed at all on my system, as it is not a standard component of FreeBSD. It turns out the only software on my system that requires bash is AsciiDoc, as a run dependency. Further investigation seems to indicate that it is only used by the a2x script as supplied with AsciiDoc. However on my system, a2x fails anyway: $ uname -a FreeBSD blizzard.phoenix 6.4-RELEASE-p1 FreeBSD 6.4-RELEASE-p1 #0: Sun Dec 21 07:56:41 UTC 2008 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 $ pkg_info | grep asciidoc asciidoc-8.3.5 A text document format for writing short documents and man $ a2x test.txt readlink: illegal option -- f usage: readlink [-n] [file ...] a2x: failed: enhanced getopt(1) required Assuming this isn't a fault with bash-4.0, and assuming a2x is also broken on FreeBSD 7.x, a short-term fix would be to not install a2x to /usr/local/bin/a2x, then the run dependency on bash could be removed. Longer-term, given that AsciiDoc is primarily written in Python, it seems odd to me that a2x isn't written in Python as well, which would obviously permanently remove the run dependency on bash. Thanks, Regards Andrew ___ 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: shells/bash-4.0 port horribly broken
On Thu 2009-03-12 08:03:23 UTC+1100, andrew clarke (m...@ozzmosis.com) wrote: $ sudo make === Vulnerability check disabled, database not found = bash-4.tar.gz is not in /usr/ports/shells/bash/distinfo. = Either /usr/ports/shells/bash/distinfo is out of date, or = bash-4.tar.gz is spelled incorrectly. *** Error code 1 Stop in /usr/ports/shells/bash. Update: After a recent ports tree update bash now builds correctly here. Thanks again :) ___ 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
shells/bash-4.0 port horribly broken
Apologies in advance if this is already fixed... $ uname -a FreeBSD blizzard.phoenix 6.4-RELEASE-p1 FreeBSD 6.4-RELEASE-p1 #0: Sun Dec 21 07:56:41 UTC 2008 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 $ sudo portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap1.FreeBSD.org... done. Latest snapshot on server matches what we already have. No updates needed. Ports tree is already up to date. $ sudo make === Vulnerability check disabled, database not found = bash-4.tar.gz is not in /usr/ports/shells/bash/distinfo. = Either /usr/ports/shells/bash/distinfo is out of date, or = bash-4.tar.gz is spelled incorrectly. *** Error code 1 Stop in /usr/ports/shells/bash. $ portlint FATAL: Makefile: extra item PATCHLEVEL placed in the PORTNAME section. FATAL: Package conflicts with itself. You should remove bash-[0-24-9].* from CONFLICTS. WARN: Makefile: PKGNAMESUFFIX has to appear earlier. WARN: Found IGNOREFILES. It is not recomended. FATAL: /usr/ports/shells/bash/distinfo: has no SIZE record for bash/bash-4.tar.gz. FATAL: -1: [no checksum record for bash/bash-4.tar.gz.]: WARN: /usr/ports/shells/bash/distinfo: no checksum records for all supported algorithms (SHA256 MD5) for bash/bash-4.tar.gz. 4 fatal errors and 3 warnings found. Thanks, Regards Andrew ___ 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
python25-2.5.4_1 build failure
Hi, python25-2.5.4_1 is failing to build on 6.4-REL-p1, and waits for input on stdin: # uname -a FreeBSD blizzard.phoenix 6.4-RELEASE-p1 FreeBSD 6.4-RELEASE-p1 #0: Sun Dec 21 07:56:41 UTC 2008 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 # pwd /usr/ports/lang/python25 # make clean === Cleaning for python25-2.5.4_1 # make === Vulnerability check disabled, database not found === Found saved configuration for python25-2.5.2_3 === Extracting for python25-2.5.4_1 = MD5 Checksum OK for python/Python-2.5.4.tgz. = SHA256 Checksum OK for python/Python-2.5.4.tgz. === Patching for python25-2.5.4_1 ... /usr/bin/sed -e 's|^#!.*|#!/usr/local/bin/python2.5|' /usr/ports/lang/python25/work/Python-2.5.4/Misc/python-config.in /usr/ports/lang/python25/work/python2.5-config /usr/bin/sed -e 's|^#!.*|#!/usr/local/bin/python-shared2.5|' /usr/ports/lang/python25/work/Python-2.5.4/Misc/python-config.in /usr/ports/lang/python25/work/python-shared2.5-config === Applying FreeBSD patches for python25-2.5.4_1 File to patch: Thanks, Regards Andrew ___ 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: Unable to build strace-4.5.18 under FreeBSD 6.4
On Sat 2008-12-27 02:57:04 UTC+1100, andrew clarke (m...@ozzmosis.com) wrote: === Building for strace-4.5.18 make all-am cc -DHAVE_CONFIG_H -I. -Ifreebsd/i386 -I./freebsd/i386 -Ifreebsd -I./freebsd -Wall -O2 -fno-strict-aliasing -pipe -MT strace.o -MD -MP -MF .deps/strace.Tpo -c -o strace.o strace.c mv -f .deps/strace.Tpo .deps/strace.Po cc -DHAVE_CONFIG_H -I. -Ifreebsd/i386 -I./freebsd/i386 -Ifreebsd -I./freebsd -Wall -O2 -fno-strict-aliasing -pipe -MT syscall.o -MD -MP -MF .deps/syscall.Tpo -c -o syscall.o syscall.c syscall.c: In function `internal_syscall': syscall.c:719: error: `sys_waitpid' undeclared (first use in this function) syscall.c:719: error: (Each undeclared identifier is reported only once syscall.c:719: error: for each function it appears in.) *** Error code 1 Update: Fixed in strace-4.5.18_1. Thanks! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Unable to build strace-4.5.18 under FreeBSD 6.4
# uname -a FreeBSD blizzard.phoenix 6.4-RELEASE FreeBSD 6.4-RELEASE #0: Wed Nov 26 11:43:51 UTC 2008 r...@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 # make === Vulnerability check disabled, database not found === Extracting for strace-4.5.18 = MD5 Checksum OK for strace-4.5.18.tar.bz2. = SHA256 Checksum OK for strace-4.5.18.tar.bz2. === strace-4.5.18 depends on file: /usr/local/bin/perl5.8.8 - found === Patching for strace-4.5.18 === strace-4.5.18 depends on file: /usr/local/bin/perl5.8.8 - found === Applying FreeBSD patches for strace-4.5.18 /usr/bin/sed -i.bak 's,/usr/bin/perl,/usr/local/bin/perl,' /spare/ports/devel/strace/work/strace-4.5.18/strace-graph === strace-4.5.18 depends on file: /usr/local/bin/perl5.8.8 - found === Configuring for strace-4.5.18 ... === Building for strace-4.5.18 make all-am cc -DHAVE_CONFIG_H -I. -Ifreebsd/i386 -I./freebsd/i386 -Ifreebsd -I./freebsd -Wall -O2 -fno-strict-aliasing -pipe -MT strace.o -MD -MP -MF .deps/strace.Tpo -c -o strace.o strace.c mv -f .deps/strace.Tpo .deps/strace.Po cc -DHAVE_CONFIG_H -I. -Ifreebsd/i386 -I./freebsd/i386 -Ifreebsd -I./freebsd -Wall -O2 -fno-strict-aliasing -pipe -MT syscall.o -MD -MP -MF .deps/syscall.Tpo -c -o syscall.o syscall.c syscall.c: In function `internal_syscall': syscall.c:719: error: `sys_waitpid' undeclared (first use in this function) syscall.c:719: error: (Each undeclared identifier is reported only once syscall.c:719: error: for each function it appears in.) *** Error code 1 Stop in /spare/ports/devel/strace/work/strace-4.5.18. *** Error code 1 Regards Andrew ___ 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: [ImageMagick] build problem
On Thu 2008-12-11 05:27:40 UTC-0800, David Wolfskill (da...@catwhisker.org) wrote: On Thu, Dec 11, 2008 at 11:48:07AM +0100, regisr wrote: When building ImageMagick-6.4.7-5 on FreeBSD 6.4 I have a build error: /usr/obj/home/ports/graphics/ImageMagick/work/ImageMagick-6.4.7-5/tests/.libs/co nstitute -storagetype double /usr/obj/home/ports/graphics/ImageMagick/work/Image Magick-6.4.7-5/tests/input_truecolor.miff cmy Constitute check failed: 6615/0.0587497/0.843137 FAIL: tests/constitute_double_cmy.sh For what it's worth, I did not encounter this. Me neither. Running on: FreeBSD g1-35.catwhisker.org 6.4-STABLE FreeBSD 6.4-STABLE #659: Thu Dec 11 05:01:52 PST 2008 r...@g1-35.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY i386 $ uname -a FreeBSD blizzard.phoenix 6.4-RELEASE FreeBSD 6.4-RELEASE #0: Wed Nov 26 11:43:51 UTC 2008 r...@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 $ pwd /usr/ports/graphics/ImageMagick $ cd /usr/ports/graphics/ImageMagick $ make showconfig === The following configuration options are available for ImageMagick-nox11-6.4.7.5: X11=off X11 support IMAGEMAGICK_TESTS=on Run bundled self-tests after build IMAGEMAGICK_OPENMP=off OpenMP for SMP (needs threads) IMAGEMAGICK_PERL=off Perl support IMAGEMAGICK_MODULES=off Modules support (broken) IMAGEMAGICK_BZLIB=on Bzlib support IMAGEMAGICK_16BIT_PIXEL=on 16bit pixel support IMAGEMAGICK_DJVU=off DJVU format support (needs threads) IMAGEMAGICK_LCMS=off LCMS support IMAGEMAGICK_HDRI=off High Dynamic Range Images (HDRI) IMAGEMAGICK_TTF=off Freetype support IMAGEMAGICK_FONTCONFIG=off Fontconfig support IMAGEMAGICK_JPEG=on JPG format support IMAGEMAGICK_OPENEXR=off OpenEXR support (needs threads) IMAGEMAGICK_PNG=on PNG format support IMAGEMAGICK_TIFF=on TIFF format support IMAGEMAGICK_FPX=off FPX format support IMAGEMAGICK_JBIG=off JBIG format support IMAGEMAGICK_JPEG2000=off JPEG2000 format support IMAGEMAGICK_DOT=off GraphViz dot graphs support IMAGEMAGICK_WMF=off WMF format support IMAGEMAGICK_SVG=off SVG format support IMAGEMAGICK_PDF=off PDF format support IMAGEMAGICK_GSLIB=off libgs (Postscript SHLIB) support === Use 'make config' to modify these settings ___ 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: sshguard-ipfw mashes /etc/syslog.conf
On Mon 2008-12-08 14:12:30 UTC+0900, Randy Bush ([EMAIL PROTECTED]) wrote: if you already run sshguard-ipfw you have an entry in /etc/syslog.conf that you like. it would be nice if upgrade of sshguard-ipfw did not mash it with a new one that is commented out. it is the commenting out that really bites. Seconded. Since reading this I just noticed sshguard-ipfw hasn't been running on my server ever since I ran portmaster sshguard-ipfw to rebuild it. (I upgraded from FreeBSD 6.3 to 6.4 recently and took the opportunity to rebuild all my installed ports...) I really wasn't expecting make deinstall to comment it out! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unable to build dovecot-1.1.6
On Sat 2008-11-15 21:02:30 UTC-0800, Jeremy Chadwick ([EMAIL PROTECTED]) wrote: You're right, there is. Our (FreeBSD porters) automated build/tester application called QAT caught that: http://lists.freebsd.org/pipermail/cvs-ports/2008-November/159599.html http://lists.freebsd.org/pipermail/cvs-ports/2008-November/159603.html I've committed a fix for this. There were more files than just distinfo and Makefile affected. Thanks Jeremy. All is well. :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
unable to build dovecot-1.1.6
Maybe this has been fixed by now but dovecot-1.1.6 is not building for me. It looks like there might be a stray carriage return in the Makefile or distinfo file? I wonder how that got in there? Thanks. Regards Andrew $ uname -a FreeBSD blizzard.phoenix 6.3-RELEASE-p5 FreeBSD 6.3-RELEASE-p5 #0: Wed Oct 1 05:34:19 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 $ cd /usr/ports/mail/dovecot $ make === Vulnerability check disabled, database not found === Found saved configuration for dovecot-1.1.6 .tar.gz is not in /usr/ports/mail/dovecot/distinfo. = Either /usr/ports/mail/dovecot/distinfo is out of date, or .tar.gz is spelled incorrectly. *** Error code 1 Stop in /usr/ports/mail/dovecot. *** Error code 1 Stop in /usr/ports/mail/dovecot. $ portlint WARN: Makefile: [114]: use of != in assignments is almost never a good thing to do. Try to avoid using them. See http://lists.freebsd.org/pipermail/freebsd-ports/2008-July/049777.html for some helpful hints on what to do instead. WARN: Makefile: only one MASTER_SITE configured. Consider adding additional mirrors. .TAL: Makefile: PORTVERSION looks illegal. You should modify 1.1.6 WARN: Makefile: PATCH_DIST_STRIP has to appear earlier. FATAL: /usr/ports/mail/dovecot/distinfo: has no SIZE record for dovecot-1.1.6. FATAL: -1: [no checksum record for dovecot-1.1.6.]: WARN: /usr/ports/mail/dovecot/distinfo: no checksum records for all supported algorithms (SHA256 MD5) for dovecot-1.1.6. FATAL: /usr/ports/mail/dovecot/distinfo: has no SIZE record for .tar.gz. FATAL: -1: [no checksum record for .tar.gz.]: WARN: /usr/ports/mail/dovecot/distinfo: no checksum records for all supported algorithms (SHA256 MD5) for .tar.gz. 5 fatal errors and 5 warnings found. $ make fetch-list .tar.gz not fetchedvecot-1.1.6bin/fetch -ApRr ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/dovecot-1.1.6 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports missing their packages.
On Wed 2008-10-29 04:42:18 UTC-0500, Scot Hetzel ([EMAIL PROTECTED]) wrote: So you are advocating that port maintainers have to create packages for all the supported FreeBSD architecture's (amd64, arm, i386, ia64, mips, pc98, powerpc, sparc64, sun4v). That would be 9 packages needing to be created at the time the port maintainer submits the upgrade PR. Or more if you want packages for both FreeBSD 6.x 7.x. Presumably the 6.x series wlll be retired before 8.x is released... :) That brings up a question (not directed at you, Scot) - what is the usual procedure for port maintainers so they can test their ports on both 6.x 7.x? In terms of building a port, is it a case of most porters running 7.x, and what compiles with gcc 4.2 without trouble is likely to be OK with gcc 3.4 also? I suppose you could install lang/gcc34 under 7.x and try building your port with that instead of the base gcc. Then it's just a matter of setting CC=gcc34. Or is there more to it than that? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: kdenetwork-kopete-0.12.8
On Sun 2008-10-26 18:17:48 UTC+0800, FBSD1 ([EMAIL PROTECTED]) wrote: This returns no sources found. What is the current status of this port/package? http://www.freebsd.org/cgi/pds.cgi?ports/net-im/kopete Are you saying the download fails? It looks fine to me. $ cd /usr/ports/net-im/kopete $ sudo make fetch === Vulnerability check disabled, database not found = kdenetwork-3.5.10.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/KDE. = Attempting to fetch from http://mirrors.isc.org/pub/kde/stable/3.5.10/src/. kdenetwork-3.5.10.tar.bz2 12% of 9117 kB 255 kBps ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: kdenetwork-kopete-0.12.8
On Sun 2008-10-26 18:43:38 UTC+0800, joeb ([EMAIL PROTECTED]) wrote: http://www.freebsd.org/cgi/pds.cgi?ports/net-im/kopete Are you saying the download fails? It looks fine to me. No what I am saying is when I go to that link it replies with no sources found. Ah, I see. You need to be MUCH clearer in your bug reports! ie. 1. Go to http://www.freebsd.org/ports/index.html 2. Search for kopete. URL is now http://www.freebsd.org/cgi/ports.cgi?query=kopete+stype=all 4. Click on Sources. URL is now http://www.freebsd.org/cgi/pds.cgi?ports/net-im/kopete Web page reads: Sources for ports/net-im/kopete Sorry, did not find the sources for ports/net-im/kopete This would seem to be an error on the FreeBSD web site itself, not a problem with the port. You can still see the status of the port: 1. Go to http://www.freebsd.org/ports/index.html 2. Search for kopete. URL is now http://www.freebsd.org/cgi/ports.cgi?query=kopete+stype=all 3. Click on kdenetwork-kopete-0.12.8 URL is now http://www.freebsd.org/cgi/cvsweb.cgi/ports/net-im/kopete/ Web page shows the port was last modified 8 weeks ago. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: kdenetwork-kopete-0.12.8
On Sun 2008-10-26 19:28:55 UTC+0800, FBSD1 ([EMAIL PROTECTED]) wrote: After researching in greater detail it seem that kopete has never had a package generated for it. The freebsd.org folks only have limited resources. Not all the ports have packages made for them. I did ftp of the packages server and checked all the different releases latest directory and find kopete has never been built as a package all the way back to release 5.0. There must be an error in the release package build system. It is not an error for a package to not exist. The packages made available on freebsd.org are really only provided for the convenience of sysadmins don't have to build all their ports from source. With several thousand ports in the ports tree it's just not practical to supply packages for all of them. It's just inevitable that some ports have to be built from source by the sysadmin. Anyway, it is pretty easy to build it yourself and make your own package. cd /usr/ports/net-im/kopete make package You can also use 'pkg_create -b' instead of 'make package'. Can a package be built for inclusion in current and 7.1 and 8.0 releases? Only commonly used ports (eg. Apache) are supplied on the release discs. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: It is illogical layout of ports
On Sat 2008-10-11 10:35:44 UTC+0300, Sokolov Alexey ([EMAIL PROTECTED]) wrote: The location of some ports contradictory. They need all rank in the categories you want. For me in most cases the category is superfluous. I will usually just use: cd /usr/ports/*/portname www/firefox-i18n mail/thunderbird-i18n Are these in the wrong category? net-im/echat (irc/echat?) net-im seems correct. I don't think eChat is an IRC client. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade -- sshguard compile failure
On Sat 2008-10-04 07:11:05 UTC-0700, David Southwell ([EMAIL PROTECTED]) wrote: cd .. /bin/sh /usr/ports/security/sshguard/work/sshguard-1.2/missing --run autoheader aclocal.m4:14: error: this file was generated for autoconf 2.61. This was fixed in sshguard 1.3. Update your ports tree. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
