RE: Php5 port and Apache Module
The php4 & php5 port apache module used to be default before FBSD 6.0. Many people before you on this list have wanted the php4/5 apache module turned back on as default but so far the port maintainer has not done anything in any way of justifying removing the apache module from the default setting or re-enable it as the default. This has forced all php4/5 users who want to use php in apache to compile it manually with the apache module option selected during the make install of the port. When it was part of the default the php4/5 package was so quick to install and ready to work with apache without any special handling. Hope you have better luck finding the justification for it being removed from the default. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Christopher Hilton Sent: Saturday, June 09, 2007 3:51 PM To: freebsd-ports@freebsd.org; User Questions Subject: Php5 port and Apache Module I can see that if I build the php5 port it defaults to CLI and CGI mode but the Apache module is not built. Am I wrong when I assume that the Apache Module will have the best performance? I guess that I'd just like to understand the engineering decisions behind the default in the port's configuration. -- Chris -- __o "All I was doing was trying to get home from work." _`\<,_ -Rosa Parks ___(*)/_(*)___ Christopher Sean Hilton pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: php5-gd-5.2.3
You just updated this port and the change log contains no entrees about this. You added a massive amount of new dependants as compared to php5-gd-5.2.1_3 port How can I turn off these new dependants as I don't see them listed in the make config options? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: mysql-server-3.23.59.n.20050301_3
Using the apache port as the standard example of how ports should be installed I have noticed 2 things wrong with the mysql-server port. First the port allocates the location for the databases to /var/db/mysql. This location has no space allocated to hold database data. It should be changed to /usr/local/mysql Next the mysql manual should be included in the port just like the apache manual is. These are not technical changes but will make the FBSD port of mysql more easy to use. Looking for feedback from the port team about these suggestions. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: mail/spamassassin
I tried to update this port. Got a no make file error. Is there anything I can do to get up to date? thanks, Bob ___ 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"
FreeBSD Port: mailman-2.1.9.r1
Hi folks: portaudit reports: Affected package: mailman-with-htdig-2.1.8_3 Type of problem: mailman -- Multiple Vulnerabilities. Reference: <http://www.FreeBSD.org/ports/portaudit/fffa9257-3c17-11db-86ab-00123ffe8333.html> An attempt to upgrade the port returns: # portupgrade mailman-with-htdig ---> Upgrading 'mailman-with-htdig-2.1.8_3' to 'mailman-with-htdig-2.1.9.r1' (mail/mailman) ---> Building '/usr/ports/mail/mailman' ===> Extracting for mailman-with-htdig-2.1.9.r1 => MD5 Checksum OK for mailman/mailman-2.1.9rc1.tgz. => SHA256 Checksum OK for mailman/mailman-2.1.9rc1.tgz. => No MD5 checksum recorded for mailman/indexing-2.1.6-0.1.patch.gz. => No SHA256 checksum recorded for mailman/indexing-2.1.6-0.1.patch.gz. => No suitable checksum found for mailman/indexing-2.1.6-0.1.patch.gz. => No MD5 checksum recorded for mailman/htdig-2.1.6-0.1.patch.gz. => No SHA256 checksum recorded for mailman/htdig-2.1.6-0.1.patch.gz. => No suitable checksum found for mailman/htdig-2.1.6-0.1.patch.gz. *** Error code 1 Stop in /usr/ports/mail/mailman. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade72882.0 make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! mail/mailman (mailman-with-htdig-2.1.8_3) (unknown build error) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed Looks like the checksum files for mailman-with-htdig-2.1.9.r1 are missing. Are they somewhere else? TIA Bob pgpAx4hhcttBs.pgp Description: PGP signature
Sound on rdesktop client and 8.0-stable
Since upgrading my system to 8.0-stable (from 7.2-stable) I no longer get sound on my FreeBSD system when connecting to my Windows 7 system via rdesktop. I start rdesktop like this: rdesktop -r sound:local ... and this was working on 7.2-stable. Now all I get is silence. Is anyone else experiencing this? My system's uname output is: FreeBSD luke.immure.com 8.0-STABLE FreeBSD 8.0-STABLE #31: Mon Dec 28 12:34:17 CST 2009 b...@luke.immure.com:/usr/obj/usr/src/sys/LUKE amd64 [Note that other X applications, pidgin to name one, output sounds] Thanks in advance for any help or advice you can offer, Bob -- Bob Willcox Nothing will ever be attempted b...@immure.com if all possible objections must be first overcome. Austin, TX -- Dr. Johnson ___ 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: GSoC: Making ports work with clang
On Mon, 03 May 2010 12:44:54 +0200 Dimitry Andric wrote: > On 2010-05-03 12:38, "C. Bergström" wrote: > > What's really the goal here? What problem are you working to > > solve? May I humbly say that building software with a different > > compiler in itself doesn't really accomplish anything. > > Of course it does. It forces you to make your software portable. So, is that the primary goal? ___ 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: Latest squid update
On 3 May 2010 18:30:38 - tmseck-li...@netcologne.de (Thomas-Martin Seck) wrote: > Since Squid 2.7/3.0 cannot separate cache and > log dir (they are subdirectories of the "localstatedir") I could > not intelligently separate logs from caches without major hackery. Sorry - I'm a but late to this discussion, having only recently joined the list. What exactly can't be separated? I run squid on a machine where the cache is in /cache (separate file system mounted on that) and the logs are in /var/log/squid. That's how I configured it in squid.conf. What am I missing? ___ 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: Upgrading Samba
On Wed, 22 Sep 2010 23:04:08 +0200 Andrea Venturoli wrote: > Hello. > > I'm using a 7.2/amd386 (soon to be 7.3) as PDC with Samba 3.0.37. > Since I have to add a Windows 7 machine, I need to upgrade to 3.4.x. > > Is this as simple as removing the port and installing the new one? > > I have no BDC, I'm not using LDAP or WinBind or anything fancy. > I do use pam_smb though (shouldn't matter, but I thought I'd write > this :-). I did this a while ago for the same reason. My logbook says that it wanted to use /var/run/samba34 (a directory) instead of the previous default. That was easy. Also that smbd wouldn't start because it needed the avahi-app package (and dependencies) but this presumably wasn't listed as a dependency because I had to install it by hand. I had to re-add the user rights for some reason - YMMV - this may be the use of different directories for 3.4. Probably wasn't necessary, but I moved smbusers to /usr/local/etc/samba34, and updated smb.conf. I can't remember how much of the above turned out to be essential. ___ 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: openoffice.org-3 does not build anymore
On Sun, 3 Oct 2010 12:40:33 +0200 David DEMELIER wrote: > Hi, > > I can't build openoffice.org-3 anymore, > > readlicense_oo > need(s) to be rebuilt > > Reason(s): > > ERROR: error 65280 occurred while > making /usr/obj/usr/ports/editors/openoffice.o > rg-3/work/OOO320_m19/readlicense_oo/ > > Attention: if you build and deliver the above module(s) you may > prolongue your t he build issuing command "build --from > readlicense_oo" > > rmdir /tmp/aTcGY4w2lp > *** Error code 1 > > Stop in /usr/ports/editors/openoffice.org-3. Quite often caused by running out of swap space. Or possibly actual disk space. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
New mutt-devel problems with text/html processing
The new version of mutt-devel nolonger honors my mailcap entry to invoke lynx when it encounters a text/html file type. Instead it simply displays the raw html text. According to their UPDATING file, they say: "all text/* parts can be displayed inline without mailcap" Which is suspiciously in the realm of the problem I'm seeing. Perhaps there's now some other way of displaying text/html files w/o mailcap and an external program that I'm missing? Thanks, Bob -- Bob WillcoxA great many people think they are thinking b...@immure.com when they are merely rearranging their prejudices. Austin, TX -- William James ___ 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: New mutt-devel problems with text/html processing
On Thu, Oct 07, 2010 at 06:51:38AM -0700, Jeremy Chadwick wrote: > On Thu, Oct 07, 2010 at 08:22:09AM -0500, Bob Willcox wrote: > > The new version of mutt-devel nolonger honors my mailcap entry to invoke > > lynx > > when it encounters a text/html file type. Instead it simply displays the raw > > html text. According to their UPDATING file, they say: > > > > "all text/* parts can be displayed inline without mailcap" > > > > Which is suspiciously in the realm of the problem I'm seeing. > > > > Perhaps there's now some other way of displaying text/html files w/o mailcap > > and an external program that I'm missing? > > Looks relevant, with a response from Michael Elkins explaining the > change: > > http://marc.info/?t=12847709334&r=1&w=2 > > Basically, it appears that as of 1.5.21, mutt only displays text/* MIME > types using its own internal engine. If you want the old behaviour, > when selecting the attachment/entry, press "m". > > Personally I don't like this change, but I'll deal with it. Thanks Jeremy, that was it. Guess I'll just have to get used to pressing 'm' now. Bob > > -- > | Jeremy Chadwick j...@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | -- Bob WillcoxA great many people think they are thinking b...@immure.com when they are merely rearranging their prejudices. Austin, TX -- William James ___ 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: New mutt-devel problems with text/html processing
On Fri, Oct 08, 2010 at 09:31:08AM +0100, Anton Shterenlikht wrote: > On Thu, Oct 07, 2010 at 11:26:06AM -0500, Bob Willcox wrote: > > On Thu, Oct 07, 2010 at 06:51:38AM -0700, Jeremy Chadwick wrote: > > > On Thu, Oct 07, 2010 at 08:22:09AM -0500, Bob Willcox wrote: > > > > The new version of mutt-devel nolonger honors my mailcap entry to > > > > invoke lynx > > > > when it encounters a text/html file type. Instead it simply displays > > > > the raw > > > > html text. According to their UPDATING file, they say: > > > > > > > > "all text/* parts can be displayed inline without mailcap" > > > > > > > > Which is suspiciously in the realm of the problem I'm seeing. > > > > > > > > Perhaps there's now some other way of displaying text/html files w/o > > > > mailcap > > > > and an external program that I'm missing? > > > > > > Looks relevant, with a response from Michael Elkins explaining the > > > change: > > > > > > http://marc.info/?t=12847709334&r=1&w=2 > > > > > > Basically, it appears that as of 1.5.21, mutt only displays text/* MIME > > > types using its own internal engine. If you want the old behaviour, > > > when selecting the attachment/entry, press "m". > > > > > > Personally I don't like this change, but I'll deal with it. > > > > Thanks Jeremy, that was it. Guess I'll just have to get used to pressing 'm' > > now. > > I missed the beginning of this thread. I had mutt-devel until > about a week ago, when, after some update, it became extremely > slow. For example, using just /var/mail it would take 10 seconds > or more to move from one message to another in index. The same > delay for opening messages in pager. The size of messages was > same as before, mostly 2-3 lines with occasional attachment. > > Anyway, I rolled back to mutt-1.4.2.3_5, which works fine. > > This has probably nothing to do with the Subject, just > thought perhaps somebody else seen a significant slow down > after the update? I haven't seen this behavior. My only issue was the change in how the latest mutt-devel handles text/* type attachements. I've seen no change in performance. Bob > > many thanks > anton > Sorry if this has nothin > > > > Bob > > > > > > > > -- > > > | Jeremy Chadwick j...@parodius.com | > > > | Parodius Networking http://www.parodius.com/ | > > > | UNIX Systems Administrator Mountain View, CA, USA | > > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > -- > > Bob WillcoxA great many people think they are thinking > > b...@immure.com when they are merely rearranging their > > prejudices. > > Austin, TX -- William James > > ___ > > 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" > > -- > Anton Shterenlikht > Room 2.6, Queen's Building > Mech Eng Dept > Bristol University > University Walk, Bristol BS8 1TR, UK > Tel: +44 (0)117 331 5944 > Fax: +44 (0)117 929 4423 -- Bob WillcoxA great many people think they are thinking b...@immure.com when they are merely rearranging their prejudices. Austin, TX -- William James ___ 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: [ANNOUNCE]: clang compiling ports, take 2
On Sun, 04 Sep 2011 12:22:35 +0200 Matthias Andree wrote: > Am 04.09.2011 10:45, schrieb Ivan Klymenko: > > В Sun, 04 Sep 2011 09:34:33 +0200 > > Matthias Andree пишет: > > > >> Am 04.09.2011 09:12, schrieb Ivan Klymenko: > >> > >>> Maybe this will help: > >>> *rdup_entry = *rdup_entry; > >> > >> This is just guessing and probably triggers the same warning unless > >> it's volatile. > >> > >> Have the original author look at it. > > > > This is not guesswork. > > It is DANGEROUS guesswork. Assigning stuff to itself is pointless, so > this is a code bug. > > The only valid exception I know is if you're writing back data to a > command register in a peripheral device, which isn't the case here. > > Fix the bug, not the symptom! I agree, but I can think of another valid exception. System with Hamming correction on the memory, gets a single bit (correctable) error. Need to rewrite the memory contents to reset all the parity bits! (sorry for the drift...) ___ 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/asterisk] Asterisk 1.8 fails to build a package
As it says. I can do: make clean make make package and it installs fine, but then: - ===> Building package for asterisk18-1.8.1.1 tar: lib/asterisk/modules/cel_pgsql.so: Cannot stat: No such file or directory tar: lib/asterisk/modules/cel_radius.so: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 *** Error code 1 Stop in /usr/ports/net/asterisk. *** Error code 1 Stop in /usr/ports/net/asterisk. - ___ 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/asterisk] Asterisk 1.8 fails to build a package
On Wed, 29 Dec 2010 07:50:03 -0600 Scot Hetzel wrote: > On Wed, Dec 29, 2010 at 4:12 AM, Bob Eager wrote: > > As it says. I can do: > > > > make clean > > make > > make package > > > > and it installs fine, but then: > > > > - > > ===> Building package for asterisk18-1.8.1.1 > > tar: lib/asterisk/modules/cel_pgsql.so: Cannot stat: No such file > > or directory tar: lib/asterisk/modules/cel_radius.so: Cannot stat: > > No such file or directory tar: Error exit delayed from previous > > errors. pkg_create: make_dist: tar command failed with code 256 > > *** Error code 1 > > > > Stop in /usr/ports/net/asterisk. > > *** Error code 1 > > > > Stop in /usr/ports/net/asterisk. > > Update your ports tree as the problem was recently fixed. > > http://www.freebsd.org/cgi/cvsweb.cgi/ports/net/asterisk/pkg-plist.diff?r1=1.45;r2=1.46;f=h I updated it this morning...but will try 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"
Re: [net/asterisk] Asterisk 1.8 fails to build a package
On Wed, 29 Dec 2010 07:50:03 -0600 Scot Hetzel wrote: > On Wed, Dec 29, 2010 at 4:12 AM, Bob Eager wrote: > > As it says. I can do: > > > > make clean > > make > > make package > > > > and it installs fine, but then: > > > > - > > ===> Building package for asterisk18-1.8.1.1 > > tar: lib/asterisk/modules/cel_pgsql.so: Cannot stat: No such file > > or directory tar: lib/asterisk/modules/cel_radius.so: Cannot stat: > > No such file or directory tar: Error exit delayed from previous > > errors. pkg_create: make_dist: tar command failed with code 256 > > *** Error code 1 > > > > Stop in /usr/ports/net/asterisk. > > *** Error code 1 > > > > Stop in /usr/ports/net/asterisk. > > Update your ports tree as the problem was recently fixed. > > http://www.freebsd.org/cgi/cvsweb.cgi/ports/net/asterisk/pkg-plist.diff?r1=1.45;r2=1.46;f=h Thanks...done. Something I wouldn't have thought of doing, as I'd updated the tree only hours before...! ___ 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: C12
On Thu, 30 Dec 2010 13:41:32 + Robin Carey wrote: > Dear Sir/Madam, > > I have written (and perfected) some open source software called C12. > > It is an E-mail security and file encryption/decryption tool for *BSD > and Linux. > > I was wondering how I would go about submitting my software to beceom > a FreeBSD port. > > Thanks ... http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ ___ 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"
Generate Latest entries?
Is there a script around anywhere to regenerate the entries in packages/latest, from those in packages/All? It seems an obvious thing to have, but I don't see one. Don't mind doing it myself, but it'd be a waste of time if I've just mis-Googled/searched and missed it..! ___ 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: Makefile, ${VARIABLE}= vs. ${VARIABLE}?=
On Sun, 13 Feb 2011 14:14:17 + (UTC) "Helmut Schneider" wrote: > Hi, > > [helmut@BSDHelmut ~]$ grep -ir latest /usr/ports/www/apache2? > /usr/ports/www/apache20/Makefile:LATEST_LINK= apache20 > /usr/ports/www/apache22/Makefile:LATEST_LINK?= apache22 > [helmut@BSDHelmut ~]$ > > So, what's the difference between e.g. "LATEST_LINK=" and > "LATEST_LINK?="? As it says in the man page... "Assign the value to the variable if it is not already defined" ___ 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: KDE3?
On Thu, 3 Mar 2011 13:04:59 -0500 Outback Dingo wrote: > On Thu, Mar 3, 2011 at 12:47 PM, Heino Tiedemann > wrote: > > > Tilman Keskinöz wrote: > > > > > On 03/02/2011 05:26 PM, Heino Tiedemann wrote: > > >> is KDE3 "out"? > > >> > > >> > > >> - misc/kdeutils3 (marked as IGNORE) > > >> > > >> or will it be compilable soon? > > >> > > > > > > Is there actually still interest in KDE3? > > > > at least me :) > > > > you might be the sole surviving user Not at all. I use it...and I know a load of people who aren't happy with KDE4. ___ 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: Future direction of virtualbox-ose port on FreeBSD
Hi, On 13 Apr 2011, at 12:38, Bernhard Froehlich wrote: > Hi VirtualBox users. > > I'm sending this because there are a few problems in how we currently > maintain the emulators/virtualbox-ose ports on FreeBSD. [etc] A question: woud there be any advantage in separating out the kernel module from the rest of it? Just asking, because I have no idea about the stability of the components and interfaces. -- Bob Bishop +44 (0)118 940 1243 r...@gid.co.ukfax +44 (0)118 940 1295 mobile +44 (0)783 626 4518 ___ 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: Would anyone like to volunteer to take over sysutils/fcron?
OK, I'll do it. My experience: two ports of my own released, plus two more I made for private use. On Mon, 18 Jul 2011 11:49:01 -0600 Brad Huntting wrote: > Dear Ports People: > > I'm looking for someone to take over maintaining the fcron FreeBSD > port. It's an easy port to maintain as the fcron source is quite > stable and changes but rarely. > However, it does require that you actually have a FreeBSD machine to > run it on, and at the moment I don't. > Would anyone like to volunteer to take over sysutils/fcron? > > > thanks in advance, > brad huntting > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Which to bump for distfile location change?
Following a recent post to this list, I need to update a port, just to change a distfile location. It seems excessive to bump PORTREVISION, so what is the best thing to change (if any). ___ 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 xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
The info in /usr/ports/UPGRADING describing the steps to upgrade xorg says to run xorg-upgrade. Unfortunately, I can't find *anything* with this name anywhere on my system. Here's my uname output: [EMAIL PROTECTED]:pf /usr/ports> uname -a FreeBSD sarlacc.austin.ibm.com 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #20: Wed Jan 2 11:29:25 CST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SARLACC amd64 I have (just today) updated my ports tree (via cvsup). Anyone have any idea where I might find the xorg-upgrade file? Perhaps it isn't required any longer. If that's the case, that would be good to know as well. Thanks, Bob -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
On Thu, Jan 31, 2008 at 03:56:23PM -0500, Wesley Shields wrote: > On Thu, Jan 31, 2008 at 02:34:26PM -0600, Bob Willcox wrote: > > The info in /usr/ports/UPGRADING describing the steps to upgrade xorg > > says to run xorg-upgrade. Unfortunately, I can't find *anything* with > > this name anywhere on my system. Here's my uname output: > > > > [EMAIL PROTECTED]:pf /usr/ports> uname -a > > FreeBSD sarlacc.austin.ibm.com 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #20: > > Wed Jan 2 11:29:25 CST 2008 [EMAIL > > PROTECTED]:/usr/obj/usr/src/sys/SARLACC amd64 > > > > I have (just today) updated my ports tree (via cvsup). > > > > Anyone have any idea where I might find the xorg-upgrade file? Perhaps > > it isn't required any longer. If that's the case, that would be good to > > know as well. > > What that entry is talking about is using script(1) in order to get an > accurate account of exactly what you did in case something goes wrong. No, I'm not interested in the script(1) part. I am familiar with script but wasn't interested in using it here. What I want is the xorg-upgrade program that is used to move a bunch of x11 files to new places for the 7.x version. Bob > > More information is available in the script man page. > > -- WXS -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
On Fri, Feb 01, 2008 at 01:02:03AM +, Parish wrote: > Bob Willcox wrote: >> No, I'm not interested in the script(1) part. I am familiar with script >> but wasn't interested in using it here. What I want is the xorg-upgrade >> program that is used to move a bunch of x11 files to new places for the >> 7.x version. >> > > xorg-upgrade is the file that script(1) spews all the output into so, if > the upgrade fails, you've got all the info to work out why (which is why > UPDATING suggests using script(1)). IIRC when I did the 6.9 -> 7.x upgrade > xorg-upgrade ended up being something like 30MB!! > > From script(1): > > script [-akq] [-t time] [file [command ...]] > > [...] > > If the argument file is given, script saves all dialogue in file. > > HTH Thanks for the info Mark, however I do know what script does and why one might use it (I've used it for years for just that, and I'm not even trying to use it here). What I was asking about (please re-read my subject line) was the xorg-upgrade command itself. Where is it located? I can't find it anywhere on any of my 10 FreeBSD systems (and I know it used to exist because I have used it in the past). Bob > > Regards, > > Mark -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
On Fri, Feb 01, 2008 at 01:30:23AM +0100, Operator wrote: > In article <[EMAIL PROTECTED]>, > Bob Willcox <[EMAIL PROTECTED]> writes: > > > What I want is the xorg-upgrade > > program that is used to move a bunch of x11 files to new places for the > > 7.x version. > > /usr/ports/Tools/scripts/mergebase.sh Is mergebase.sh a replacement for xorg-upgrade? -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
On Fri, Feb 01, 2008 at 12:12:15AM -0600, Scot Hetzel wrote: > On 1/31/08, Jeremy Messenger <[EMAIL PROTECTED]> wrote: > > On Thu, 31 Jan 2008 21:26:38 -0600, Bob Willcox <[EMAIL PROTECTED]> wrote: > > > > > On Fri, Feb 01, 2008 at 01:30:23AM +0100, Operator wrote: > > >> In article <[EMAIL PROTECTED]>, > > >> Bob Willcox <[EMAIL PROTECTED]> writes: > > >> > > >> > What I want is the xorg-upgrade > > >> > program that is used to move a bunch of x11 files to new places for > > >> the > : > > > > In the /usr/ports/UPDATING said: > : > > > ># script xorg-upgrade > : > We should change this in UPDATING to: > > # script xorg-upgrade.log > > Then there would be less confusion about the xorg-upgrade file. That probably would have helped me. The really sad thing about my mis-reading this is that is the third time I've worked through this particular UPDATING entry to upgrade X. It's been about 8 to 10 months since I last did it, but that doesn't make it any less embarrassing. :) Bob > > Scot -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
On Fri, Feb 01, 2008 at 02:40:44PM +1030, Wayne Sierke wrote: > > On Thu, 2008-01-31 at 21:26 -0600, Bob Willcox wrote: > > On Fri, Feb 01, 2008 at 01:30:23AM +0100, Operator wrote: > > > In article <[EMAIL PROTECTED]>, > > > Bob Willcox <[EMAIL PROTECTED]> writes: > > > > > > > What I want is the xorg-upgrade > > > > program that is used to move a bunch of x11 files to new places for the > > > > 7.x version. > > > > > > /usr/ports/Tools/scripts/mergebase.sh > > > > Is mergebase.sh a replacement for xorg-upgrade? > > > > Bob, > > Re-read the previous replies and re-read man script(1) paying careful > attention to the syntax of the (optional) arguments. xorg-upgrade is the > name of the output file that script(1) will write to (i.e. name it > anything you want, how about xorg-upgrade.log). xorg-upgrade is merely a > suggested name for it. > > The wording of the /usr/ports/UPDATING entry can be misleading if you > read it quickly and make what appears to be a reasonable assumption > about how script(1) is used, viz. "run the xorg 7.2 upgrade inside a > script(1) session." followed by the "# script xorg-upgrade" example. Ok, my dumb mistake...of course you guys are all right! I've been pretty sick is my only (lame) excuse, and it must be effecting my ablity to think. :) Thanks and I apologize for all the noise. Bob > > > Wayne -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
GraphicsMagick Port Status
I am the maintainer for the image processing package known as GraphicsMagick. A few weeks ago, the FreeBSD port maintainer for GraphicsMagick became upset and quit. This leaves me a bit concerned since my project is left in limbo. As of yesterday, the current GraphicsMagick releases are 1.1.14 (legacy stable) and 1.2.3 (current stable). FreeBSD only offers 1.1.12. There are important security fixes (what Debian classifies as "grave") contained in these releases. I see that someone has picked up the ImageMagick port. Can someone please take responsibility for the GraphicsMagick port so that GraphicsMagick users (e.g. KDE) are not left behind? Maintaining the GraphicsMagick port is similar to maintaining the ImageMagick port (except for being much easier). It is important that FreeBSD ports make it over the hurdle and move up to the 1.2.X baseline. There are four additional years of development and bug fixing in the 1.2 branch. Due to time constraints, usually only fixes for serious issues are back-ported to the 1.1 branch. Thanks, Bob ====== Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Asterisk GUI port?
On Thu, 17 May 2012 19:45:21 +0100 Kaya Saman wrote: > Hi, > > I'm wondering if there is any port for a version of the Asterisk GUI?? > > Either asterisk-ui or FreePBX ?? > > > I currently have an old and broken version of Trixbox CE installed > and I want to move away from Linux as much as possible as FreeBSD is > so much better in so many areas. > > > Could anyone suggest anything or do I have to go back to Linux again? > > I have seen a port called asterisk-ui but running FreeBSD 8.2 AMD64 > RELEASE I couldn't find it within the ports tree I looked under > /usr/ports/net/ cd /usr/ports; make search name=asterisk One of the items is /usr/ports/www/asterisk-gui - that may be what you want. ___ 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: [RFC] Seeking Approval: include bsd.port.pre.mk so SRC_BASE is defined before referenced
On 05/21/12 15:04, Jason Helfman so wittily quipped: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am working on the following pr, and would like to get others approval to the following patch: http://people.freebsd.org/~jgh/files/pre-patch.txt http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/165994 This patch is fixing several use cases of SRC_BASE before it is defined. (re: comms/uarduno port) Now that I understand what the patch is for I totally agree, it should be applied to comms/uarduno as well. I believe I copied my port from one of the others that had the 'bad logic' in it, so thanks for catching it. Do I need to make the change or are you going to do it on your end? ___ 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"
The xpdf binary is MIA with xpdf-3.03_2
When building the xpdf port the xpdf executable is no longer being built or installed into /usr/lib/libexec/xpdf. I suspect that this happened as the result of a change that was made on 10/12/2012 with version xpdf-3.03_2. My other systems that I've not updated the ports tree on lately have the xpdf-3.03_1 version and there the executable is being built and istalled. Is anyone else seeing this (I have it failing on two of my recently ports tree updated systems here)? Bob -- Bob Willcox Why bother building anymore nuclear b...@immure.comwarheads until we use the ones we have? Austin, TX ___ 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, 19 Oct 2012 13:18:32 -0400 Eitan Adler wrote: > On 19 October 2012 12:38, andrew clarke 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. > > > http://ozzmosis.com/uemacs/ue400dev.zip > > in either case please let me know and I'll update the port. > > If Andrew doesn't, then I'll take it on. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On Thu, 24 May 2018 09:08:17 +0100 Johannes Lundberg wrote: > In addition to that it would be nice (if it's not already done) to > store this information in a log file somewhere so that one can > revisit and see what needs to be manually configured for each > installed package. I have this in syslog.conf: !pkg,pkg-static *.* /var/log/pkg.log ___ 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: make package "*** Error code 1"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 8 Jun 2018 05:58:01 -0400
Matthew Seaman wrote:
> On 07/06/2018 21:17, Eugene Grosbein wrote:
> > 08.06.2018 8:12, duckmanjbr wrote:
> >
> >> do-install:
> >>${MKDIR} ${STAGEDIR}${PREFIX}/pkg
> >>${MKDIR} ${STAGEDIR}${PREFIX}/bin/localrepo
> >>${MKDIR} ${STAGEDIR}/etc/inc/priv
> >>${MKDIR} ${STAGEDIR}${DATADIR}
> >>${INSTALL_DATA} -m 0644
> >> ${FILESDIR}${PREFIX}/pkg/localrepo.xml \ ${STAGEDIR}${PREFIX}/pkg
> >>${INSTALL_DATA} ${FILESDIR}${PREFIX}/pkg/localrepo.inc \
> >>${STAGEDIR}${PREFIX}/pkg
> >>${INSTALL_DATA}
> >> ${FILESDIR}${PREFIX}/bin/localrepo/localrepo.conf \
> >> ${STAGEDIR}${PREFIX}/bin/localrepo ${INSTALL_DATA}
> >> ${FILESDIR}/etc/inc/priv/localrepo.priv.inc \
> >> ${STAGEDIR}/etc/inc/priv ${INSTALL_DATA}
> >> ${FILESDIR}${DATADIR}/info.xml \ ${STAGEDIR}${DATADIR}/info.xml
> >>@${REINPLACE_CMD} -i '' -e
> >> "s|%%PKGVERSION%%|${PKGVERSION}|" \
> >>
> >> .include
> >
> > Here is obvious bug: the line with REINPLACE_CMD has continuation
> > backslash without any continuation text and without file name to
> > process. Fix it.
>
> Actually, since the next line is a blank line, that's going to be
> pretty harmless. It should be fixed as a matter of style though.
>
> The thing that is actually biting the OP is that ${REINPLACE_CMD}
> expands to this:
>
> % make -V REINPLACE_CMD
> /usr/bin/sed -i.bak
>
> So you're already passing a '-i' flag to sed(1), and it's the
> additional -i '' on your command line that sed(1) doesn't like.
That may be wrong, but the complaint is about using -i on standard
input. There is definitely a missing filename.
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEEVgdI2KeVldPAhUYaKBdf2az8e6gFAlsaWUwACgkQKBdf2az8
e6hyfggAi80w3j2VL0Bnv6Hvh0cs6oxS+HlCF4WV+VU1sAxDNPz6Sd799FuCQBpJ
n2/E4F+Cf1DwdPgnE/ks+VDi3YDH6th6pUqSvNfcJK03qsqt9c0Td8k5W+KAMGVu
jPg+nte+2eCQLtTeW2tSE6oxw1TYlhfo0avyQ2ZtJJoBvo1myk52TmrRFE+qzdgm
17NvyU0gmBtMNS89AL0AiHHcHXvRCc5szLtNF9PoCyVCxu26Q1l24IR8SiDhz2UU
gJXKRsBUy91T2uCBvlZMrH9GIcCDHwVJxhVBRXL3/PFWOxWgMOSvOIt/wjrk4Knh
jTCCaoK0Babb1CQo5DuRG6m8IN9p9g==
=H8JY
-END PGP SIGNATURE-
___
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: Any way to prevent do-extract chmod and chown?
On Wed, 27 Jun 2018 19:06:44 -0400 Joseph Ward wrote: > When I "make extract", the "do-extract" target is performing a chmod > and chown on everything, as seen from the following excerpt from the > bsd.port.mk file: . . . > Short of commenting those lines out (which I really don't want to do > because I have 0 idea why it's there or what I'd break with other > ports) is there any way at all to maintain the ownership of the > files? If the ownership is well defined and not complex, you could add a post-extract: target in your Makefile and fix up the ownerships then. Or, you could override the do-extract: target with your own, and extract the files as you want (probably replicating part of the real do-extract: target). ___ 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: how to make ports not install xorg or dependencies
On Tue, 31 Jul 2018 11:41:17 +0100 tech-lists wrote: > Hello, > > context: freebsd-12 r336215 arm64 > > I don't want xorg or X11 or any of its components installed on this > system. I install ports in the traditional way, in other words cd > port && make config && make install. Any ports that in a generic > config want to install xorg libs, I want the no-x11 variant. > > There used to be a way to enforce this no-xorg in make.conf but > looking at /usr/share/examples/etc/make.conf I can find no reference > to X Xorg x11 or xorg. I presume there's a new method. If there is, > can anyone please tell me how? In make.conf, it should be just: OPTIONS_SET+= NO-X11 ___ 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: Delete a port
On Sat, 4 Aug 2018 10:42:36 -0700
Eitan Adler wrote:
> On Sat, 4 Aug 2018 at 08:13, Chris Rees wrote:
> >
> > Hey,
> >
> > On 4 August 2018 15:15:23 BST, Eugene Grosbein
> > wrote:
> > >04.08.2018 21:03, Romain Tartière wrote:
> > >
> > >> On Sat, Aug 04, 2018 at 12:28:41PM +0200, Matthias Fechner
> > >> wrote:
> > >>> ./rmport: svnlog: not found
> > >>>
> > >>> Anyone an idea what is wrong?
> > >>
> > >> Never used this script, but I guess you are hitting line 390:
> > >>
> > >> | $EDITOR svnlog
> > >>
> > >> Any chance $EDITOR is not set?
> > >
> > >It seems, rmport script needs a patch:
> > >
> > >Index: Tools/scripts/rmport
> > >===
> > >--- Tools/scripts/rmport(revision 476322)
> > >+++ Tools/scripts/rmport(working copy)
> > >@@ -39,6 +39,7 @@
> > > # MAINTAINER= cr...@freebsd.org
> > > #
> > >
> > >+EDITOR=${EDITOR:-vi}
> > > PORTSDIR=${PORTSDIR:-/usr/ports}
> > > INDEX=${PORTSDIR}/`make -C ${PORTSDIR} -V INDEXFILE`
> >
> > Thanks both.
> >
> > Feel free to commit, but please use the absolute path to vi?
>
> Why? Would't one want to respect the user's preference when it comes
> to an editor? This preference is implicit when it comes to PATH.
>
>
This simply adds vi as a default; it doesn't force it to be used.
___
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: workflow question: how do you maintain the port in sync with upstream?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 14 Aug 2018 17:33:38 +0200
Mathieu Arnold wrote:
> On Tue, Aug 14, 2018 at 10:41:43PM +0800, blubee blubeeme wrote:
> > This one is fairly straight forward, you can simply replace that
> > string with a regex command;
> > This is an example of running a replace command for strings after
> > the patch phase of the build;
> >
> > post-patch:
> > @${REINPLACE_CMD} -e 's|for Linux|for FreeBSD|g'
> > ${WRKSRC}/README
>
> Patching files in post-patch using sed SHOULD only be used to replace
> dynamic content, never static content.
Indeed. One of the most annoying things is that it breaks 'make
makepatch'.
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEEVgdI2KeVldPAhUYaKBdf2az8e6gFAltzD60ACgkQKBdf2az8
e6h2QQgApKsemAO02PhYYAhAYhSTEZeBB99wNtrfhlFv341kyzlfgRmtj+Boum4P
a6dxBKUllppOcw4515fa/I6Q36LE4OCTkH3c2gUSATZArummj1cdBRCrqfgxYMww
dc6OntuSnXZ1r6zaBNKVi0wmnFh2Q1oOagx5IrtJ/ysDXgt1oNhNrtWfYjOQyGuL
AajyTzb+NAa0Y+FVIptLYUmcezrHCUuZQUqaLAKlg72C/OvnQYxyP+kzHkztgiH/
zVkgW+jZeLP+vmSjqmtFIHZC6VzC0Sg53dZJlLfIbG4qmyyOgET1mDP9c5WfR3vq
0E6sQxsLrTs8RzLnx61TYD1fP0eSPQ==
=yKsq
-END PGP SIGNATURE-
___
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"
error: undefined symbol: OPENSSL_cpuid_setup
While playing with compiling www/chromium, I'm seeing make stop with /usr/bin/ld.lld: error: undefined symbol: OPENSSL_cpuid_setup This is on a Raspberry Pi 3 running FreeBSD www.zefox.org 12.0-ALPHA7 FreeBSD 12.0-ALPHA7 r338880 GENERIC with ports at 480613 World and kernel build, install and run acceptably, so the system as a whole isn't hugely broken. Can anybody suggest a fix/workaround? Thanks for reading! bob prohaska ___ 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: error: undefined symbol: OPENSSL_cpuid_setup
On Mon, Sep 24, 2018 at 07:26:08PM -0700, bob prohaska wrote: > While playing with compiling www/chromium, I'm seeing make stop with > /usr/bin/ld.lld: error: undefined symbol: OPENSSL_cpuid_setup > > This is on a Raspberry Pi 3 running > FreeBSD www.zefox.org 12.0-ALPHA7 FreeBSD 12.0-ALPHA7 r338880 GENERIC > with ports at > 480613 > > World and kernel build, install and run acceptably, so the system as > a whole isn't hugely broken. Can anybody suggest a fix/workaround? Changed the make command to make -DBATCH DISABLE_VULNERABILITIES=yes DEFAULT_VERSIONS+=ssl=base > make.log but make stopped with the same error: /usr/bin/ld.lld: error: undefined symbol: OPENSSL_cpuid_setup >>> referenced by crypto.c >>> crypto.o:(do_library_init) in archive >>> obj/third_party/boringssl/libboringssl.a c++: error: linker command failed with exit code 1 (use -v to see invocation) It's not clear to me if this is an issue with the port, or the base system. Any advice appreciated! bob prohaska ___ 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: error: undefined symbol: OPENSSL_cpuid_setup
On Wed, Sep 26, 2018 at 09:53:32AM +, Lorenzo Salvadore via freebsd-ports wrote: > > > While playing with compiling www/chromium, I'm seeing make stop with > > > /usr/bin/ld.lld: error: undefined symbol: OPENSSL_cpuid_setup > > > This is on a Raspberry Pi 3 running > > > FreeBSD www.zefox.org 12.0-ALPHA7 FreeBSD 12.0-ALPHA7 r338880 GENERIC > > > with ports at > > > 480613 > > > World and kernel build, install and run acceptably, so the system as > > > a whole isn't hugely broken. Can anybody suggest a fix/workaround? > > > > Changed the make command to > > make -DBATCH DISABLE_VULNERABILITIES=yes DEFAULT_VERSIONS+=ssl=base > > > make.log > > > > but make stopped with the same error: > > /usr/bin/ld.lld: error: undefined symbol: OPENSSL_cpuid_setup > > > > > > > referenced by crypto.c > > > > > crypto.o:(do_library_init) in archive > > > > > obj/third_party/boringssl/libboringssl.a > > > > c++: error: linker command failed with exit code 1 (use -v to see > > invocation) > > > > It's not clear to me if this is an issue with the port, or the base system. > > Any advice appreciated! > > I might be wrong, but I see some similiraties with an issue discussed in > those days > under the subject "error: undefined symbol: main in poudriere jail". It was a > linking problem that appeared only on 12.0-ALPHA7 (or current any anyway, not > on > 11.2-RELEASE). I suggest you take a look into it. > > Here are the links to the most relevant messages (from the week archive, so > they > will not work anymore after the week pass and then you will have to search > them > in an other archive): > https://docs.freebsd.org/cgi/getmsg.cgi?fetch=87161+0+current/freebsd-ports > https://docs.freebsd.org/cgi/getmsg.cgi?fetch=108259+0+current/freebsd-ports > My situation is much simpler than the one described, there's no jail, just a plain "make" in /usr/ports/www/chromium. Hopefully it'll be less complex! Thanks for reading and posting, bob prohaska ___ 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-static: xorgproto-2018.4 conflicts with glproto-1.4.17
In trying to get a usable web browser running on a Raspberry Pi 2 running 11.2-STABLE #3 r339214 I keep running into conflicts between ports trying to put files in the same place. In this particular case, the make command was root@www:/usr/ports/graphics/gdk-pixbuf # make -DBATCH DISABLE_VULNERABILITIES=yes MAKE_JOBS_UNSAFE=yes FORCE_PKG_REGISTER=yes with an overall goal of compiling www/epiphany, or any graphical browser that works. Xfce4 managed to compile and work, but it didn't build a browser. What's the customary way to resolve conflicts of this type? It would be OK to break older ports if necessary; I just want to get a web browser that runs and don't need a desktop environment. TWM is enough for my purposes. Thanks for reading, bob prohaska ___ 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: pkg-static: xorgproto-2018.4 conflicts with glproto-1.4.17
On Sun, Oct 07, 2018 at 06:57:15PM +0200, Walter Schwarzenfeld wrote: > /usr/ports/MOVED > > x11/glproto|x11/xorgproto|2018-07-31|merged into x11/xorgproto. > > run > > grep proto /usr/ports/MOVED > > a lot of "*proto-ports" are merged into xorgproto. > That got me past the ports conflict, alas to no avail. Epiphany wants gnome3, gnome3 stopped with editor/meson.build:120:0: ERROR: Invalid version of dependency, need 'glib-2.0' ['>= 2.55.1'] found '2.50.3'. Is there any GUI browser available for 11-stable on the Pi2? Lynx runs, but it's effectively unusable on modern, graphics-formatted websites. Thanks for your help, bob prohaska ___ 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: pkg-static: xorgproto-2018.4 conflicts with glproto-1.4.17
On Sun, Oct 07, 2018 at 07:52:48PM +0200, Walter Schwarzenfeld wrote: > Recent version?? of glib20 is 2.56.1. > > Ahh! I knew the latest was 2.56.1 but failed to guess it was called glib20. Tried just about everything but Thank you! bob prohaska ___ 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"
Missing globaladdr implementation for www/webkit2-gtk3
In trying to compile numerous ports on an RPI3 that depend on www/webkit2-gtk3 the process stops with errors along the lines of DerivedSources/JavaScriptCore/LLIntAssembly.h:1349:2: error: Missing globaladdr implementation #error Missing globaladdr implementation Both the system and ports tree are current. The make command is simply make -DBATCH Is there a workaround? Thanks for reading, bob prohaska ___ 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"
Compiling firefox on Raspberry Pi 2
Attempts to compile firefox63 on an RPI2 fail with ===> rust-1.29.2 is only for aarch64 amd64 i386, while you are running armv6 (reason: requires prebuilt bootstrap compiler). *** Error code 1 while compilation of firefox-esr stops with dt_modtext:/usr/src/cddl/contrib/opensolaris/lib/libdtrace/common/dt_link.c(856): arm not implemented dtrace: failed to link script /usr/ports/www/firefox-esr/work/firefox-52.8.0esr/js/src/devtools/javascript-trace.d: an error was encountered while processing jsarray.o gmake[5]: *** [/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/rules.mk:788: js-dtrace.o] Error 1 gmake[5]: Leaving directory '/usr/ports/www/firefox-esr/work/.build/js/src' gmake[4]: *** [/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/recurse.mk:71: js/src/target] Error 2 gmake[4]: Leaving directory '/usr/ports/www/firefox-esr/work/.build' gmake[3]: *** [/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/recurse.mk:33: compile] Error 2 gmake[3]: Leaving directory '/usr/ports/www/firefox-esr/work/.build' gmake[2]: *** [/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/rules.mk:523: all] Error 2 Can anybody suggest workaround for either problem? Thanks for reading, bob prohaska ___ 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: Compiling firefox on Raspberry Pi 2
On Sat, Oct 20, 2018 at 11:01:15AM +0200, Ronald Klop wrote: > > Not a workaround. Buy you can try to port rust to armv6. Which will > benefit some other ports also. > Rust has tier 2 support for linux/arm, so it might be not so hard to do. > https://forge.rust-lang.org/platform-support.html > You give me too much credit 8-), but I'll look into it. I thought there was an option somewhere to disable rust-dependent features, but I can't find it now. > For Firefox-esr, try to disable DTRACE in the build options of the port. > It says it is not implemented on arm. The default is to build without dtrace: one has to check the box to "Build with DTrace probes" which I've been leaving unchecked. Is there something else I'm missing? Thanks! bob prohaska > > > > > Thanks for reading, > > > > bob prohaska > > > > ___ > > 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" > ___ > 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" ___ 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"
Config dialog seems to crash on RPI#
The configuration dialog box for at least some ports seems to be crashing on an RPI# running recent -current, with a ports tree that was updated in the last day. The crash seems only to suppress changes made, apparently leaving the defaults intact. Make doesn't seem to mind. Right now uname -a reports FreeBSD www.zefox.org 13.0-CURRENT FreeBSD 13.0-CURRENT r339680 GENERIC arm64 An example is security/openssl, but chromium and firefox have behaved similarly: [config dialog didn't copy/paste] Segmentation fault (core dumped) ===> Options unchanged ===> Installing for openssl-1.0.2p_1,1 ===> Checking if openssl already installed ===> Registering installation for openssl-1.0.2p_1,1 Installing openssl-1.0.2p_1,1... I'm wondering if this suggests a more systematic problem on my system. >From time to time clang crashes with a segfault, other times it runs without issue. Thanks for reading, and any ideas. bob prohaska ___ 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: Config dialog seems to crash on RPI#
On Wed, Oct 24, 2018 at 08:15:36PM +0200, Walter Schwarzenfeld wrote: > I cannot say if it helps, but with dialog problems in the past mostly > helps to recompile ports-mgmt/dialog4ports. > Recompiling dialog4ports certainly didn't hurt, afterwards it worked for chromium (chromium didn't compile anyway, as expected). The whole OS is recompiling now. Thanks for posting, bob prohaska ___ 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"
Can't run pkg-static install on rpi3 at r339840
All of a sudden an attempt to run make in /usr/ports/www/chromium reports pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended but running pkg-static install -f pkg reports pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended Updating FreeBSD repository catalogue... pkg-static: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory pkg-static: http://pkg.FreeBSD.org/FreeBSD:13:aarch64/latest/meta.txz: Not Found repository FreeBSD has no meta file, using default settings pkg-static: http://pkg.FreeBSD.org/FreeBSD:13:aarch64/latest/packagesite.txz: Not Found Unable to update repository FreeBSD Error updating repositories! Any suggestions appreciated! Thanks for reading, bob prohaska ___ 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: Can't run pkg-static install on rpi3 at r339840
On Mon, Oct 29, 2018 at 07:35:38PM +, Nathan Owens via freebsd-ports wrote: > Try pkg-static update first > > > Alas, no luck. Same result as before. Running pkg -N reports ld-elf.so.1: /usr/local/lib/libcrypto.so.9: version OPENSSL_1_1_0 required by /usr/local/lib/libpkg.so.4 not defined, running pkg-static -N reports pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended pkg-static: 511 packages installed So maybe this is fallout of the SSL update. It's unclear to me if the "Warning" message can simply be ignored. Make doesn't seem to stop. I'd be grateful for any pointers to a way out of this pickle. Thanks for reading, bob prohaska ___ 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: options DOCS + EXAMPLES
On Fri, 2 Nov 2018 11:33:11 +0100 Harry Schmalzbauer wrote: > Am 02.11.2018 um 11:24 schrieb Mathieu Arnold: > > On Fri, Nov 02, 2018 at 10:49:52AM +0100, Harry Schmalzbauer > > wrote: > >> Hello, > >> > >> found out that the need to define DOCS and EXAMPLES in > >> OPTIONS_DEFINE was made mandatory some time ago, which > >> ports-mgmt/portlint isn't aware about yet (found > >> https://reviews.freebsd.org/D13036). > >> > >> I intentionally haven't defined it, because I want to make use of > >> the bsd.ports.mk handling of PORTDOCS and PORTEXAMPLES, but don't > >> want to spam the UI. EXAMPLES and DOCS shall stay mandatory for > >> my port, as long as the user changes the corresponding defaults. > >> > >> How do I hide the user selection for EXAMPLES and DOCS after the > >> change (which I wasn't able to find by reading commit logs)? > > > > I am not sure what you are asking. > > > > To be able to use PORTDOCS or PORTEXAMPLES, you must define a DOCS > > or an EXAMPLES option. > > > > The users must be allowed to choose if they want documentation or > > examples to be installed. If you personnaly do not want the options > > dialog to show up when you build ports, you can set BATCH in your > > environment. > > Thank you for your answer. > In my case, I have additional options, so I can't use BATCH. > Please see my opinion about the DOCS/EXAMPLES selection in the reply > to myself, where I reference the commit introducing this change and > where I explain why in many/most cases, I consider these > DOCS/EXAMPLES/NLS options as spam. Yes, but it's possible to turn off DOCS and EXAMPLES (and indeed any other named option) globally (for all ports). That can be useful when building for certain targets. ___ 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"
Inkscape compiles but crashes on startup
On an RPI3 running 13.0-CURRENT r339983 inkscape compiled without obvious errors but reports (process:35330): Gtk-WARNING **: 17:00:23.081: Locale not supported by C library. Using the fallback 'C' locale. Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. (inkscape:35330): Gtk-WARNING **: 17:00:33.357: ChannelsAction: missing action ChannelsAction [much snippage, ending with] (inkscape:35330): Gtk-WARNING **: 17:00:33.510: ConnectorOverlapAction: missing action ConnectorOverlapAction Abort (core dumped) If anybody has a fix or workaround I'd be pleased to try it. Thanks for reading, bob prohaska ___ 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: Inkscape compiles but crashes on startup
On Sat, Nov 03, 2018 at 01:29:58AM +0100, Walter Schwarzenfeld wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232073 > > The patch should working. > I tried deleting and recompiling devel/libgmm, but simply re-starting inkscape produces the same error. Is it necessary to recompile other things? Thanks for replying! bob prohaska ___ 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: Inkscape compiles but crashes on startup
On Sat, Nov 03, 2018 at 07:18:52AM +0100, Walter Schwarzenfeld wrote: > Wait, fix of the primal cause of it is committed right now. > > https://svnweb.freebsd.org/ports?view=revision&revision=483878 > Alas, no luck. Updating the ports tree and recompiling inkscape got rid of the locale error, but inkscape still crashes with an otherwise similar error stream from Gtk. Thanks for reading, bob prohaska ___ 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: Inkscape compiles but crashes on startup
On Sun, Nov 04, 2018 at 10:47:22AM +0100, T??l Coosemans wrote: > On Sat, 3 Nov 2018 22:31:34 -0700 bob prohaska wrote: > > On Sat, Nov 03, 2018 at 07:18:52AM +0100, Walter Schwarzenfeld wrote: > >> Wait, fix of the primal cause of it is committed right now. > >> > >> https://svnweb.freebsd.org/ports?view=revision&revision=483878 > > > > Alas, no luck. Updating the ports tree and recompiling inkscape got > > rid of the locale error, but inkscape still crashes with an otherwise > > similar error stream from Gtk. > > You have to rebuild devel/glib20. That did the trick, thank you! bob prohaska ___ 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"
ninja error building webkit2-gtk3 on rpi3
Ports are at 484411, system is at 133. Attempts to compile webkit2-gtk3 stops with -c DerivedSources/JavaScriptCore/unified-sources/UnifiedSource86.cpp ninja: build stopped: subcommand failed. ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make: stopped in /usr/ports/www/webkit2-gtk3 I can't find a more detailed statement of what went wrong anywhere in the make output. Thanks for reading, any suggestions appreciated. bob prohaska ___ 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: ninja error building webkit2-gtk3 on rpi3
On Thu, Nov 08, 2018 at 01:23:20PM +0100, Ronald Klop wrote: > On Thu, 08 Nov 2018 02:18:57 +0100, bob prohaska > wrote: > > > Ports are at 484411, system is at 133. Attempts to compile > > webkit2-gtk3 > > stops with > > > > > > -c DerivedSources/JavaScriptCore/unified-sources/UnifiedSource86.cpp > > ninja: build stopped: subcommand failed. > > ===> Compilation failed unexpectedly. > > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure > > to > > the maintainer. > > > Do this part of the message. Before building: > > export MAKE_JOBS_UNSAFE=yes > > That will give a more clear error. > For some reason the export command isn't found (I'm using whatever shell su gives me for root) but digging through the make log found an old error that's been around for some time: In file included from /usr/ports/www/webkit2-gtk3/work/webkitgtk-2.20.5/Source/JavaScriptCore/l lint/LowLevelInterpreter.cpp:559: DerivedSources/JavaScriptCore/LLIntAssembly.h:795:2: error: Missing globaladdr implementation #error Missing globaladdr implementation If somebody is aware of a fix please clue me in. Thanks for reading, bob prohaska ___ 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: ninja error building webkit2-gtk3 on rpi3
On Fri, Nov 09, 2018 at 04:57:23PM +0100, Kurt Jaeger wrote: > Hi! > > > > > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the > > > > failure > > > > to > > > > the maintainer. > > > > > > Do this part of the message. Before building: > > > > > > export MAKE_JOBS_UNSAFE=yes > > > > > > That will give a more clear error. > > > > > For some reason the export command isn't found (I'm using whatever shell su > > gives me for root) > > Which is csh, so: > > setenv MAKE_JOBS_UNSAFE yes > > would work. > > > DerivedSources/JavaScriptCore/LLIntAssembly.h:795:2: error: Missing > > globaladdr implementation > > #error Missing globaladdr implementation > > > > If somebody is aware of a fix please clue me in. > > Walter pointed me to a PR which had a fix. I added the fix to the > port, please test if it helps. > Yes, webkit2-gtk3 now compiles successfully on RPI3. Thank you! bob prohaska ___ 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"
More troubles building www/epiphany
Now that webkit2-gtk3 compiles correctly make in www/epiphany stops on what looks like a version of the openssl upgrade problem: ld-elf.so.1: /usr/local/lib/libcrypto.so.9: version OPENSSL_1_1_0 required by /usr/local/lib/libarchive.so.13 not defined Command '['/usr/ports/devel/appstream-glib/work/appstream-glib-0.7.8/_build/tmp-introspect4zt426i5/AppStreamGlib-1.0', '--introspect-dump=/usr/ports/devel/appstream-glib/work/appstream-glib-0.7.8/_build/tmp-introspect4zt426i5/functions.txt,/usr/ports/devel/appstream-glib/work/appstream-glib-0.7.8/_build/tmp-introspect4zt426i5/dump.xml']' returned non-zero exit status 1. ninja: build stopped: subcommand failed. *** Error code 1 Stop. make[4]: stopped in /usr/ports/devel/appstream-glib *** Error code 1 Stop. make[3]: stopped in /usr/ports/devel/appstream-glib *** Error code 1 Stop. make[2]: stopped in /usr/ports/x11-fonts/cantarell-fonts *** Error code 1 Stop. make[1]: stopped in /usr/ports/x11/gnome-desktop *** Error code 1 Stop. make: stopped in /usr/ports/www/epiphany At this point /etc/make.conf contains the single line DEFAULT_VERSIONS+=ssl=openssl in response to a warning from earlier make attempts. /etc/src.conf is not present. What's the best way to proceed? I started to compile security/openssl111 but was greeted by an immediate conflict warning with no obvious resolution. The system is at FreeBSD 13.0-CURRENT r340325 GENERIC arm64 Thanks for reading, bob prohaska ___ 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: More troubles building www/epiphany
On Sun, Nov 11, 2018 at 12:16:47AM +0100, Dimitry Andric wrote: > > After r339270 (the upgrade of base OpenSSL to 1.1.1) and r339709 > (bumping of OpenSSL shared libraries to version 111), you must delete > all your ports, and rebuild them from scratch. > > Yes, it sucks. :) > Ok, at least I know now. Thanks! bob prohaska ___ 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: More troubles building www/epiphany
On Sat, Nov 10, 2018 at 03:35:59PM -0800, bob prohaska wrote: > On Sun, Nov 11, 2018 at 12:16:47AM +0100, Dimitry Andric wrote: > > > > After r339270 (the upgrade of base OpenSSL to 1.1.1) and r339709 > > (bumping of OpenSSL shared libraries to version 111), you must delete > > all your ports, and rebuild them from scratch. > > > > Yes, it sucks. :) > > > > Ok, at least I know now. > For lack of a better idea, I tried running "make deinstall" in /usr/ports/ to clean house. It appeared to at least partly work, but now trying to make -DBATCH in www/webkit2-gtk3 the make process stops while building cmake: [ 5%] Built target cmsys [ 7%] Built target cmsys_c [ 7%] Built target cmcompress [ 74%] Built target CMakeLib [ 75%] Built target CMakeServerLib [ 88%] Built target CTestLib [ 88%] Built target ctest [ 94%] Built target CPackLib [ 95%] Built target cpack [ 96%] Built target cmake [ 99%] Built target ccmake [100%] sphinx-build man: see Utilities/Sphinx/build-man.log Traceback (most recent call last): File "/usr/local/bin/sphinx-build", line 6, in from pkg_resources import load_entry_point File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3112, in @_call_aside File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3096, in _call_aside f(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3125, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 578, in _build_master ws.require(__requires__) File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 895, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 781, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'typing' distribution was not found and is required by Sphinx *** Error code 1 Stop. make[4]: stopped in /usr/ports/devel/cmake/work/cmake-3.12.4 *** Error code 1 Stop. make[3]: stopped in /usr/ports/devel/cmake/work/cmake-3.12.4 *** Error code 1 Stop. make[2]: stopped in /usr/ports/devel/cmake/work/cmake-3.12.4 *** Error code 1 Stop. make[1]: stopped in /usr/ports/devel/cmake *** Error code 1 Stop. make: stopped in /usr/ports/devel/cmake The file Utilities/Sphinx/build-man.log is present, but empty. This is a new problem, apparently precipitated by attempting to delete old ports. For the moment I'm trying to manually compile python27, to see if it helps. If there's a better thing to try please let me know. Thanks for reading, bob prohaska ___ 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: More troubles building www/epiphany
On Sun, Nov 11, 2018 at 06:55:12PM +0100, Walter Schwarzenfeld wrote: > Compile CMake with DOCS=off. > For some reason it wasn't necessary, cmake compiled after a couple cycles of cleaning and reinstalling. Now webkit2-gtk3 is getting stuck compiling libsoup: checking for glib-networking (glib TLS implementation)... no configure: error: libsoup requires glib-networking for TLS support. If you are building a package, you can pass --disable-tls-check to allow building libsoup anyway (since glib-networking is not actually required at compile time), but you should be sure to add a runtime dependency on it. ===> Script "configure" failed unexpectedly. Please report the problem to gn...@freebsd.org [maintainer] and attach the "/usr/ports/devel/libsoup/work/libsoup-2.62.2/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make[2]: stopped in /usr/ports/devel/libsoup *** Error code 1 The really strange thing is that glib-networking compiled and installed without visible errors, so it's not clear why the test failed. Any ideas appreciated, including a way to cleanly remove all ports and start over! This is on an RPI3, so there are, far as I know, no precompiled packages available. Thanks for reading, bob prohaska ___ 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"
libsoup can't find glib-networking on rpi3
For some reason attempts to compile libsoup stop on a failure to find glib-networking, despite the latter being installed and up-to-date. I've experimented with simply commenting out the BUILD_DEPENDS and RUN_DEPENDS lines in the Makefile, make fails in the same way, which is slightly surprising. I expected at least a different error. Ports are at 484876, sources are at 340358. The goal here is to compile www/epiphany, which depends on webkit2-gtk3, which dpends on libsoup, which requires glib-networking. If there's another way to go about compiling a graphical browser that works please advise me. Thanks for reading, bob prohaska ___ 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"
Resolving ports conflicts for ImageMagick6
In trying to bring inkscape up to date on r340487 the process is getting stuck with ===> Registering installation for ImageMagick6-6.9.10.14,1 as automatic Installing ImageMagick6-6.9.10.14,1... pkg-static: ImageMagick6-6.9.10.14,1 conflicts with ImageMagick-6.9.9.28_2,1 (installs files into the same place). Problematic file: /usr/local/bin/Magick++-config *** Error code 70 The problem seems to have its origin in the rename of the imagemagick port mentioned in /usr/ports/UPDATING for November 10th. How does one work past a problem like this? Thanks for reading, bob prohaska ___ 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: Resolving ports conflicts for ImageMagick6
On Sun, Nov 18, 2018 at 10:32:15AM -0800, David Wolfskill wrote: > On Sun, Nov 18, 2018 at 09:43:39AM -0800, bob prohaska wrote: > > In trying to bring inkscape up to date on r340487 the process > > is getting stuck with > > > > ===> Registering installation for ImageMagick6-6.9.10.14,1 as automatic > > Installing ImageMagick6-6.9.10.14,1... > > pkg-static: ImageMagick6-6.9.10.14,1 conflicts with > > ImageMagick-6.9.9.28_2,1 (installs files into the same place). Problematic > > file: /usr/local/bin/Magick++-config > > *** Error code 70 > > I did so via "pkg delete -f graphics/ImageMagick". > That worked, Thank you! bob prohaska ___ 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: Resolving ports conflicts for ImageMagick6
On Sun, Nov 18, 2018 at 07:49:41PM +0100, Christoph Moench-Tegeder wrote: > ## bob prohaska (f...@www.zefox.net): > > > Installing ImageMagick6-6.9.10.14,1... > > pkg-static: ImageMagick6-6.9.10.14,1 conflicts with > > ImageMagick-6.9.9.28_2,1 (installs files into the same place). Problematic > > file: /usr/local/bin/Magick++-config > > *** Error code 70 > > Make sure your installed packages are up-to-date with your ports tree. > Using old packages with a new ports tree (or vice versa) results in... this. I neglected to mention this in on an RPI3, so packages aren't available. It never crossed my mind that pkg could be used to remove a port compiled from source. I tried "make deinstall", but by then the old ImageMagick port had morphed into ImageMagick6 and deinstall didn't work. bob prohaska ___ 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"
Inkscape package troubles, "libicuuc.so.62" not found
Using pkg delete resolved the ImageMagick vs ImageMagic6 conflict, allowing inkscape to build successfully from ports on an RPI3. Alas, I somehow deleted libicuuc.so.62, causing a runtime failure. Rebuilding devel/icu got version 63, so that didn't help. Noticing that inkscape is now available as a package, I tried installing that, expecting it to recover the older library needed for the current version of inkscape. The install brought down roughly 1 GB of files, but not the needed library. Is there a resolution to this dilemma, other than just waiting for inkscape to catch up? Is it possible to determine which revision of the ports tree can make a runnable version of a particular port? Thanks for reading, bob prohaska ___ 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: Inkscape package troubles, "libicuuc.so.62" not found
On Mon, Nov 19, 2018 at 04:43:18PM -0800, Steve Kargl wrote: > On Mon, Nov 19, 2018 at 03:57:22PM -0800, bob prohaska wrote: > > Using pkg delete resolved the ImageMagick vs ImageMagic6 conflict, allowing > > inkscape to build successfully from ports on an RPI3. > > > > Alas, I somehow deleted libicuuc.so.62, causing a runtime failure. > > Rebuilding > > devel/icu got version 63, so that didn't help. > > > > The simple (temporary) workaround is > > echo 'libicuuc.so.62 libicuuc.so.63' >> /etc/libmap.conf > Thank you very much, I didn't know about libmap.conf. bob prohaska ___ 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: Inkscape package troubles, "libicuuc.so.62" not found
On Tue, Nov 20, 2018 at 09:53:28AM -0800, David Wolfskill wrote: > I strongly suspect that you are encountering "complications" because of > a lack of consistency with respect to installed ports/packages on the > system in question. > > That is, "consistency" with respect to the state of the underlying ports > tree(s) that was/were used to build the ports & packages in question. > I broke inkscape by mistakenly deleting an old library required by the old(ish) port of inkscape. Libmap.conf provided an escape in this case. More generally, is there a way to determine what revision of the ports tree will successfully compile/run a given port, if it existed in the past? Thanks for reading, bob prohaska ___ 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"
Can't compile sysutils/u-boot-rpi3 on rpi3
In trying to compile sysutils/u-boot-rpi3 natively the compilation stops with many errors caused by rsa-sign.c /usr/bin/ld: error: undefined symbol: OPENSSL_init_ssl >>> referenced by rsa-sign.c >>> tools/lib/rsa/rsa-sign.o:(rsa_sign) /usr/bin/ld: error: undefined symbol: EVP_MD_CTX_new >>> referenced by rsa-sign.c >>> tools/lib/rsa/rsa-sign.o:(rsa_sign) and so on. The system is at r341083, ports are at 486064. Buildworld and buildkernel both work, so the basics are ok. I'd like to try updating u-boot to see if it fixes Timeout poll on interrupt endpoint messages that seem to interfere with hands-off rebooting. Thanks for reading, bob prohaska ___ 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: Can't compile sysutils/u-boot-rpi3 on rpi3
On Wed, Nov 28, 2018 at 02:38:34PM +0900, KIRIYAMA Kazuhiko wrote: > At Tue, 27 Nov 2018 18:06:59 -0800, > bob prohaska wrote: > > > > In trying to compile sysutils/u-boot-rpi3 natively the compilation > > stops with many errors caused by rsa-sign.c > > > > /usr/bin/ld: error: undefined symbol: OPENSSL_init_ssl > > >>> referenced by rsa-sign.c > > >>> tools/lib/rsa/rsa-sign.o:(rsa_sign) > > > > /usr/bin/ld: error: undefined symbol: EVP_MD_CTX_new > > >>> referenced by rsa-sign.c > > >>> tools/lib/rsa/rsa-sign.o:(rsa_sign) > > > > > > and so on. > > Maybe OpenSSL 1.1 API problems [1]. > The errors listed in the bug report didn't include any of the form "undefined symbol". Not sure how significant the distinction is, but it looks different to a naive eye. > [1] https://wiki.freebsd.org/OpenSSL/1.1.0 > Thanks for reading! bob prohaska ___ 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"
How much memory to compile www/chromium?
How much memory should be required for make -DBATCH in www/chromium? Make issues warnings about disk space required, but I don't recall seeing anything about RAM or swap. The system in question is an RPI3 running r341643. Make reached part [18416/30819], at which point it seems to have stalled. The machine is still (sluggishly) responsive, gstat is reporting dT: 10.050s w: 10.000s L(q) ops/sr/s kBps ms/rw/s kBps ms/wd/s kBps ms/d %busy Name 8588149708 25.7439 20567.7 0 00.0 100.0 mmcsd0 8588149708 25.7439 20567.8 0 00.0 100.0 mmcsd0s2 8588149708 25.7439 20567.8 0 00.0 100.0 mmcsd0s2b That it got stuck on reading, rather than writing, is a little surprising. Swapinfo reports Device 1K-blocks UsedAvail Capacity /dev/mmcsd0s2b4404252 2705928 169832461% If this is expected, is there a way to reduce the number of threads started by make? It's using four now, all in state SWREAD showing WCPU of zero to a few percent. Top is reporting mostly idle, with system and interrupt at less than 10%. There are swap_pager_getswapspace(32): failed messages on the console, so it really is out of memory. Thanks for reading! bob prohaska ___ 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: How much memory to compile www/chromium?
On Wed, Dec 12, 2018 at 07:41:49PM +0100, Christoph Moench-Tegeder wrote: > ## bob prohaska (f...@www.zefox.net): > > > How much memory should be required for > > make -DBATCH > > in www/chromium? > > Quite a lot, multiple GBs. > > > I'm not even sure if your SD card will survive that :) > That's ok, I'm trying to discover what is and isn't practical on a Pi3 > > If this is expected, is there a way to reduce the number of > > threads started by make? > > See bsd.ports.mk: DISABLE_MAKE_JOBS (as in "make -DDISABLE_MAKE_JOBS"). > Thank you, I think that's the information needed. Come to think of it, will the -j option, such as -j2, work in this situation also? Two threads are much better than one 8-) As it happens, the machine isn't stuck. Make still seems to be running, now it's up to [18466/30819], admittedly not making fast progress. I'll let it run for now, just to see what happens. Thanks for your help, bob prohaska ___ 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: How much memory to compile www/chromium?
On Wed, Dec 12, 2018 at 09:25:04PM +0100, Christoph Moench-Tegeder wrote: > ## bob prohaska (f...@www.zefox.net): > > > > See bsd.ports.mk: DISABLE_MAKE_JOBS (as in "make -DDISABLE_MAKE_JOBS"). > > > > > Thank you, I think that's the information needed. Come to think of it, > > will the -j option, such as -j2, work in this situation also? Two threads > > are much better than one 8-) > > If you had looked into bsd.port.mk yourself... right below the docs of > DISABLE_MAKE_JOBS (line 814) is some documentation for MAKE_JOBS_NUMBER > and MAKE_JOBS_NUMBER_LIMIT. -j won't help because there's a lot of Setting MAKE_JOBS_NUMBER_LIMIT=2 seems to have the desired effect. Still, top reports four c++ processes, but only two are running and swap use seldom exceeds 1GB at worst. So far, that's been enough to prevent stalling. Editing /usr/ports/Mk/bsd.port.mk looks like it'll affect all ports; what's the convention for making the change local to www/chromium only? Thanks for your patience! bob prohaska ___ 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: How much memory to compile www/chromium?
On Fri, Dec 14, 2018 at 05:59:21AM +0100, Jan Beich wrote:
>
> MAKE_JOBS_NUMBER_LIMIT is a user variable, so you can either set in
> make.conf or Makefile.local e.g.,
>
> $ cat <<\. >>${__MAKE_CONF:-/etc/make.conf}
> .if ${.CURDIR:M*/www/chromium}
> MAKE_JOBS_NUMBER_LIMIT=2
> .endif
Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile successfully
over
several days. The -DBATCH option was used, in hopes it'd fetch the right
options.
Swap usage fluctuated over the course of the build, from a minimum of
around 230MB to over one GB at several points. Past about 500MB the CPU
usage dropped, evidently from I/O limitations to the microSD based swap
partition, which was far too big at 4GB.
One curiousity was a gradual increase in minimum swap usage, from about 230
MB initially to about 280 MB a couple days later. This wasn't a highly
systematic observation, just me looking at a top window from time to time.
When the build finished swap use dropped back to ~20MB, which is the normal
idle state.
The resulting executable turned up in /usr/local/bin/chrome, which was
slightly surprising; the port's name is chromium, after all It seems
to run, but is too slow to play Youtube videos smoothly. For static pages
it seems fine.
The major problem is a complete lack of audio. I'm using an HDMI to DVI cable
and plugging the audio system into the Pi3's headphone jack. Is there some
trick to getting the headphone jack to work?
Thanks for reading, and everyone's help getting chromium to work on the Pi3.
bob prohaska
___
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"
RPI3 sound for www/chromium, was Re: How much memory to compile www/chromium?
On Tue, Dec 18, 2018 at 11:41:44PM +, Jamie Landeg-Jones wrote: > bob prohaska wrote: > > > Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile > > successfully over > > several days. The -DBATCH option was used, in hopes it'd fetch the right > > options. > > Use "make config-recursive" before you start. It will present to you upfront > all > the option screens that would appear during the build. > > I've noticed it sometimes misses some, if you add some dependency in one of > the menus. > So to be sure, once it's finished its run, if you've made any option changes, > run > it again, and again and again etc.. until you no longer get menus popping up. > That's a good idea provided one knows beforehand which options to select. I very seldom know which options apply, especially on the first try. After a few failures my guesses sometimes improve In the case of www/chromium it looks like the sound support is wrong, but so far it isn't obvious which sound option is correct. Would anybody hazard a guess as to what sound support works on a Pi3? The clearest hint so far is a report of ALSA lib pcm_oss.c:835:(_snd_pcm_oss_open) Cannot open device /dev/dsp when starting up chrome. Thanks for reading! bob prohaska ___ 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: RPI3 sound for www/chromium, was Re: How much memory to compile www/chromium?
On Wed, Dec 19, 2018 at 05:14:07PM +1100, Brian Scott wrote: > > I believe the problem now is that support for builtin sound on the RPI3 > is still a work in progress (it goes through the HDMI subsystem and I > think it was a 32 vs. 64 bit issue but is a mystery to me beyond that). > I infer that sound is only a distant murmur on the Pi3. 8-) Thanks for the clarification! bob prohaska > ___ 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"
Deletion of the grpn port
I just noticed that grpn has been delete from the freebsd ports. This is apparently due to its use of glib12 (which is deprecated) and lack of a maintainer. Anyone know how much difference there is between glib12 and the current version (glib20 I believe)? I've been using grpn for more years than I can remember and hate to see it disappear. -- Bob Willcox| If more of us valued food and cheer and song above hoarded b...@immure.com | gold, it would be a merrier world. Austin, TX | -- J. R. R. Tolkien ___ 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: Deletion of the grpn port
On Thu, Dec 27, 2018 at 07:16:16PM +0200, Andriy Gapon wrote: > On 26/12/2018 21:52, Bob Willcox wrote: > > I just noticed that grpn has been delete from the freebsd ports. This is > > apparently due to its use of glib12 (which is deprecated) and lack of a > > maintainer. Anyone know how much difference there is between glib12 and the > > current version (glib20 I believe)? I've been using grpn for more years > > than I > > can remember and hate to see it disappear. > > Perhaps, math/galculator could take its place?.. Thanks for the tip...I have built it and so far, so good! :) > -- > Andriy Gapon -- Bob Willcox| If more of us valued food and cheer and song above hoarded b...@immure.com | gold, it would be a merrier world. Austin, TX | -- J. R. R. Tolkien ___ 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: How much memory to compile www/chromium?
On Tue, Dec 18, 2018 at 09:49:03AM -0800, bob prohaska wrote: > > Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile successfully > over > several days. The -DBATCH option was used, in hopes it'd fetch the right > options. > Just for fun I added a mechanical hard disk with a 4 GB swap partition and re-ran the www/chromium compilation with MAKE_JOBS_NUMBER_LIMIT unset, to see what happens. OOMA was turned off with vm.pageout_oom_seq="2048" in /boot/loader.conf. After ~11 days the process finished. Log files of gstat output and make output are at http://www.zefox.net/~fbsd/rpi3/swaptests/r342204/chromium/mech_sd/ in case anyone's curious. The log files are around 100MB, it seems quickest to download them to look around. Swap use peaked at 3522008 kB. If gstat is to be believed the bottleneck appears to be the mechanical hard disk, which showed near 100% busy when the microSD swap partition was around 15% busy. Apart from a few "indefinite wait..." warnings on the console there was no indication of errors. As a further test, I'ved added two additional USB flash swap devices and am re-running the compilation of www/chromium. The swap layout is quite lopsided, with the USB flash devices having only 2 GB swap partitions on each, contrasting to the 4 GB swap partitions on the microSD card and mechanical disk. The first oddity is that top doesn't seem to see the extra swap space, reporting only 7192M total. Swapinfo does seem to plausibly report swap status as Device 1K-blocks UsedAvail Capacity /dev/mmcsd0s2b440425252228 4352024 1% /dev/da0p1419430450848 4143456 1% /dev/da2p5209715228232 2068920 1% /dev/da1f 209715228060 2069092 1% Total12792860 159368 12633492 1% after running overnight. "indefinite wait..." warnings on the console have returned in abundance with the use of USB flash swap, even though swap usage is still less than 200MB. Thanks for reading, bob prohaska ___ 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: How much memory to compile www/chromium?
On Tue, Jan 01, 2019 at 03:14:26PM -0800, Mark Millard wrote: > > > On 2019-Jan-1, at 10:21, bob prohaska wrote: > > > On Tue, Dec 18, 2018 at 09:49:03AM -0800, bob prohaska wrote: > > > > > > As a further test, I'ved added two additional USB flash swap devices and am > > re-running > > the compilation of www/chromium. The swap layout is quite lopsided, with > > the USB flash > > devices having only 2 GB swap partitions on each, contrasting to the 4 GB > > swap partitions > > on the microSD card and mechanical disk. > > > > The first oddity is that top doesn't seem to see the extra swap space, > > reporting only > > 7192M total. > > If you start top before changing the swap space (swapon or > swapoff), top does not change to match: it does not monitor > the swap space total size over time. But I've no other clue > to the ordering that actually occurred. > In fact I made that mistake so I quit and restarted top. The incorrect swap total number persisted. After a fashion the number makes some sense: The small swap partitions are 2 GB, if the swap is used uniformly the total would be 8 GB. 7192 MB is less wrong than the ~13GB reported by swapinfo. > > You might want to report the types/models of the USB flash devices that > were in used. Also relevant is the past usage pattern and amount of > prior use on the USB flash devices. > > The flash devices are the same Sandisk Extreme "thumb drives" used in earlier swap experiments with buildworld. One is model SDCZ80-064, the other SDCZ800-064. The former is rated USB3.0, the latter USB3.1. They're certainly not new, but neither are they obviously broken (yet). Thanks for reading! bob prohaska ___ 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: How much memory to compile www/chromium?
> > On 2019-Jan-1, at 10:21, bob prohaska wrote: > > > On Tue, Dec 18, 2018 at 09:49:03AM -0800, bob prohaska wrote: > >> > >> Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile > >> successfully over > >> several days. The -DBATCH option was used, in hopes it'd fetch the right > >> options. > >> > > > > Just for fun I added a mechanical hard disk with a 4 GB swap partition and > > re-ran > > the www/chromium compilation with MAKE_JOBS_NUMBER_LIMIT unset, to see what > > happens. > > OOMA was turned off with vm.pageout_oom_seq="2048" in /boot/loader.conf. > > > > After ~11 days the process finished. Log files of gstat output and make > > output are at > > http://www.zefox.net/~fbsd/rpi3/swaptests/r342204/chromium/mech_sd/ > > > > As a further test, I'ved added two additional USB flash swap devices and am > > re-running > > the compilation of www/chromium. The swap layout is quite lopsided, with > > the USB flash > > devices having only 2 GB swap partitions on each, contrasting to the 4 GB > > swap partitions > > on the microSD card and mechanical disk. > > The attempt to compile chromium using four USB swap partitions didn't complete, but it might have gotten far enough to be surprising. Swap use peaked around 2.4 GB, while the dual swap partition setup used around 3.5 GB of swap at maximum. The make failure happened near the 17000 counter point, when the controlling ssh connection was dropped. I _think_ that's past the point of maximum swap use, but I'll have to re-try to make sure. The log files are at http://www.zefox.net/~fbsd/rpi3/swaptests/r342204/chromium/flash_mech_sd/ in case anybody is curious. Thanks for reading, bob prohaska ___ 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"
How to alert committer?
I have a PR on one of my ports, and I agree with the patch provided. I'm not sure how to signal to have the port committed. I can obviously ask here (and am now doing so) but is there an automated way of doing that please? Port: math/rexx-regmath PR: 235512 This is a fix to the Makefile to allow compilation on non-Clang systems. ___ 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: How to alert committer?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 5 Feb 2019 12:21:43 +0100 Mathieu Arnold wrote: > On Tue, Feb 05, 2019 at 11:08:01AM +0000, Bob Eager wrote: > > I have a PR on one of my ports, and I agree with the patch provided. > > > > I'm not sure how to signal to have the port committed. I can > > obviously ask here (and am now doing so) but is there an automated > > way of doing that please? > > > > Port: math/rexx-regmath > > PR: 235512 > > > > This is a fix to the Makefile to allow compilation on non-Clang > > systems. > > All you need to do is set the "maintainer feedback" thing to a +, it > then should appears in the "maintainer approved" search. Yes, I had done that. > Maybe you > need to set the "maintainer approval" thing on the patch though, and > not on the PR itself. I've now done that too! Thanks. -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEVgdI2KeVldPAhUYaKBdf2az8e6gFAlxZdB0ACgkQKBdf2az8 e6jIOgf/az9KgSE2rIvwKDhsk/bR00DupK8CfGxBEEwe1iEb6pIUGGT41U9AMpod JS7VW9vWYjgybYUgss1BYINepx+HU7u3xwJkG1j7jXjbIFjKQinpZOiqBOZom2hO 5DRBIHswVFhUq7aJUZYNTM10SdQ2uqDGUZ6e3dFyukBkesxVBptiE5pmlNKG7FwE Gvhe55dAJA0lG2+LLxr44T30byQt5eGTlodjtlLCGtkoVQEtZ8znRK7NR+NSwfzo upigxgPFfjOvc4bFljwSKxsoOVe4izqV/vB0Onwoc8i36gMmN5cE1BKpCOUeETUE mZXH6iEIO1vR9jlnjNy/yQAl8o8TOQ== =7T+9 -END PGP SIGNATURE- ___ 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"
Missing modules in devel/rust-cbindgen
In trying to compile /usr/ports/devel/rust-cbindgen on an rpi3 running -current make fails with errors such as error[E0412]: cannot find type `c_long` in the crate root It's tempting to think this is some sort of configuration error. Can anyone suggest a workaround? There don't seem to be any user-configurable options. Rust itself now builds successfully on the rpi3, I think rust-cbindgen might be the only remaining obstacle to compiling some flavor of firefox. Thanks for reading, and any guidance! bob prohaska ___ 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: Missing modules in devel/rust-cbindgen
On Fri, Feb 22, 2019 at 03:43:14PM +0100, Jan Beich wrote: > bob prohaska writes: > > > In trying to compile /usr/ports/devel/rust-cbindgen on an > > rpi3 running -current make fails with errors such as > > > > error[E0412]: cannot find type `c_long` in the crate root > > > > It's tempting to think this is some sort of configuration > > error. Can anyone suggest a workaround? There don't seem > > to be any user-configurable options. > > See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063 > libc-0.2.49 with the fixes is yet to be released. > > > Rust itself now builds successfully on the rpi3, I think > > rust-cbindgen might be the only remaining obstacle to > > compiling some flavor of firefox. > > See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234253 > Need help with upstreaming Skia fix. Also waiting for libc-0.2.49. Ok, not so simple after all. Thanks for letting me know. bob prohaska ___ 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"
Config inconsistency for firefox-esr on rpi2
In playing with www/firefox-esr on an rpi2 at r343555 using ports at 493769 make stops with ===> Configuring for firefox-esr-52.8.0,1 firefox-esr-52.8.0,1: Needs gtk3 with WAYLAND support enabled. *** Error code 1 despite both wayland and gtk3 being selected in the config dialog. I've retried several times, the error persists. Any suggestions? Thanks for reading, bob prohaska ___ 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: Config inconsistency for firefox-esr on rpi2
On Sun, Feb 24, 2019 at 11:12:47PM +0100, Dimitry Andric wrote: > > This actually means that you have to rebuild the *gtk3* port with > WAYLAND enabled. It could be worded a little better, maybe. :) > Indeed, it could be worded much better.8-\ There doesn't seem to be a port named gtk3, but there are quite a few with gtk3 in the name. The most likely candidates seem to be: /usr/ports/www/webkit2-gtk3 /usr/ports/www/webkit-gtk3 /usr/ports/www/vimb-gtk3 /usr/ports/devel/gwenhywfar-gtk3 /usr/ports/x11/keybinder-gtk3 /usr/ports/net/avahi-gtk3 /usr/ports/x11-toolkits/rubygem-gtk3 /usr/ports/x11-toolkits/wxgtk30 /usr/ports/x11-toolkits/gtk30 /usr/ports/x11-toolkits/wxgtk31 /usr/ports/audio/libcanberra-gtk3 My first guess would be /usr/ports/x11-toolkits/gtk30, is that right? Thanks for reading! bob prohaska > -Dimitry > ___ 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: Config inconsistency for firefox-esr on rpi2
On Tue, Feb 26, 2019 at 12:54:23AM +0100, Miroslav Lachman wrote: > > Take a look at a dependencies of firefox-esr > https://www.freshports.org/www/firefox-esr/ > > in build dependencies: > gtk3>=3.14.6 : x11-toolkits/gtk30 > I tried for a while to compile various *gtk3 ports, always getting stuck. Most of the trouble seemed to be missing or failed dependencies. Sometimes going to the home of the failure and running make there resolved the problem for that step, but other difficulties always came out of the woodwork. Eventually I think the process ran aground on an error with gstreamer and I gave up. For the moment /usr/src was updated and world is building; much has changed. Then I'll update /usr/ports and start over. > in library dependencies: > libgtk-x11-2.0.so : x11-toolkits/gtk20 > libgtk-3.so : x11-toolkits/gtk30 > > quite confusing gtk20 vs gtk30... > Would it help if there were a uniform method for naming ports and versions and any resulting binaries? Near as I can tell there isn't; some use 1 digit suffixes, some use 2 digits, some delimit with dots, some delimit with dashes. The variety seems endless 8-) > gtk20 has not option WAYLAND so you need to rebuild gtk30 with option > WAYLAND enabled. I neglected to take notes, but gtk30 wouldn't build with wayland enabled by default. Wayland did build by itself, but that's not the problem. It isn't obvious to me if there's a way for multiple ports with conflicting dependencies to automatically name them so the names don't conflict. Seems like it would have to be done at both the source and binary level. Right now it's sometimes hard to figure out what source directory is needed to create a given binary. Thanks for reading, bob prohaska ___ 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: Config inconsistency for firefox-esr on rpi2
On Tue, Feb 26, 2019 at 12:54:23AM +0100, Miroslav Lachman wrote: > > Take a look at a dependencies of firefox-esr > https://www.freshports.org/www/firefox-esr/ > > in build dependencies: > gtk3>=3.14.6 : x11-toolkits/gtk30 > > in library dependencies: > libgtk-x11-2.0.so : x11-toolkits/gtk20 > libgtk-3.so : x11-toolkits/gtk30 > > quite confusing gtk20 vs gtk30... > > gtk20 has not option WAYLAND so you need to rebuild gtk30 with option > WAYLAND enabled. > For some reason gtk30 stops with root@www:/usr/ports/x11-toolkits/gtk30 # gdkkeys-wayland.c:34:10: fatal error: 'fribidi.h' file not found #include I tried compiling gtk20 in the hopes it might provide the missing file, but it completed successfully and fribidi.h remains absent. Last resort was to remake wayland, but that didn't help, gtk30 still stops with missing fribidi.h Is there a way out of this box? Thanks for reading, bob prohaska ___ 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: Config inconsistency for firefox-esr on rpi2
On Wed, Feb 27, 2019 at 07:42:57PM +0100, Walter Schwarzenfeld wrote: > Install converters/fribidi. > Already present, and reinstalled to see if it helps. No luck. The file is in /usr/local/include/fribidi/fribidi.h so there must be some sort of path issue. Thanks for reading! bob prohaska ___ 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"
unknown type name '__uint128_t'
On an rpi3 with system at r344605, ports at 494124 and
CFLAGS=-O2 in /etc/make.conf, an attempt to compile
www/chromium stopped, reporting
In file included from ../../base/third_party/libevent/event.c:49:
In file included from /usr/include/signal.h:42:
/usr/include/machine/ucontext.h:46:2: error: unknown type name '__uint128_t'
__uint128_t fp_q[32];
^
1 error generated.
followed a few lines later by
In file included from ../../base/third_party/libevent/evdns.c:37:
In file included from /usr/include/sys/types.h:46:
/usr/include/machine/endian.h:89:19: error: invalid operand in inline asm:
'rev16 ${0:w}, ${1:w}'
__asm __volatile("rev16 %w0, %w1\n"
^
/usr/include/machine/endian.h:89:19: error: invalid operand in inline asm:
'rev16 ${0:w}, ${1:w}'
/usr/include/machine/endian.h:89:19: error: unexpected token in operand
:1:8: note: instantiated into assembly here
rev16 ,
^
In file included from ../../base/third_party/libevent/evdns.c:37:
In file included from /usr/include/sys/types.h:46:
/usr/include/machine/endian.h:89:19: error: invalid operand in inline asm:
'rev16 ${0:w}, ${1:w}'
__asm __volatile("rev16 %w0, %w1\n"
^
/usr/include/machine/endian.h:89:19: error: invalid operand in inline asm:
'rev16 ${0:w}, ${1:w}'
Errors continue in the same general vein until make gives up.
A month ago chromium would compile (with clang difficulties) and
even run more or less reasonably, so whatever is wrong happened
in a fairly recent timeframe.
Can anybody suggest a fix or workaround?
Thanks for reading,
bob prohaska
___
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: Missing timestamp implementation on rpi3
On Sun, Mar 03, 2019 at 02:39:58PM -0700, Ian Lepore wrote: > On Sun, 2019-03-03 at 10:54 -0800, bob prohaska wrote: > > > > The error it encountered is: > > > > No TimeStamp implementation on this platform. Build will not > > succeed > > > > Correct the error condition and try again. > > > See if this helps... > > https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201510&action=diff > > -- Ian The patch applied without complaint, but restarting make in www/firefox promptly repeated the error. I'm trying make clean followed by make in www/firefox presently. Does lang/rust and friends need rebuilding? Thanks very much! bob prohaska ___ 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: Missing timestamp implementation on rpi3
On Sun, Mar 03, 2019 at 03:46:39PM -0800, bob prohaska wrote: > On Sun, Mar 03, 2019 at 02:39:58PM -0700, Ian Lepore wrote: > > On Sun, 2019-03-03 at 10:54 -0800, bob prohaska wrote: > > > > > > The error it encountered is: > > > > > > No TimeStamp implementation on this platform. Build will not > > > succeed > > > > > > Correct the error condition and try again. > > > > > > See if this helps... > > > > https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201510&action=diff > > > > -- Ian > > The patch applied without complaint, but restarting make in www/firefox > promptly repeated the error. I'm trying make clean followed by make > in www/firefox presently. Does lang/rust and friends need rebuilding? > After cleaning www/firefox compiled and runs (slowly!). Rust seems to have rebuilt as part of the bycatch. Thank you! bob prohaska ___ 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"
Man pages for wireshark don't happen
Just tried making net/wireshark on raspberry pi 2 11.2/stable. GUI failed in gtk5, but CLI version installed successfully. Where does it put the man pages? man wireshark reports No manual entry for wireshark and the docs I could find seemed to talk about the GUI version. Thanks, bob prohaska ___ 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"
Can't compile www/node on rpi2
Recent attempts to compile www/node using 11-Stable on an rpi2 fail with ../src/node_file.cc:2023:15: error: use of undeclared identifier 'uv_fs_lchown' uv_fs_lchown, *path, uid, gid); ^ ../src/node_file.cc:2029:14: error: use of undeclared identifier 'uv_fs_lchown' uv_fs_lchown, *path, uid, gid); followed by many more errors in the same vein. Sources are at r345414, ports are at 496629, this has been going on for some weeks now. Is there a fix or workaround? Thanks for reading, bob prohaska ___ 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"
