Re: RPI3 sound for www/chromium, was Re: How much memory to compile www/chromium?

2018-12-18 Thread Jan Beich
bob prohaska  writes:

> 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.

According to https://svnweb.freebsd.org/changeset/base/222980 sound(4)
was enabled by default only on x86 archs.
___
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?

2018-12-18 Thread bob prohaska
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: How much memory to compile www/chromium?

2018-12-18 Thread Jamie Landeg-Jones
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.

cheers, Jamie
___
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: sysutils/apachetop needs a commiter

2018-12-18 Thread Kurt Jaeger
Hi!

> I'm the apachetop maintainter, there's a pending update (and compile
> fix) that I approved.
> 
> Can someone commit it please?
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227865

Done.

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
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"


sysutils/apachetop needs a commiter

2018-12-18 Thread Łukasz Wąsikowski
Hi,

I'm the apachetop maintainter, there's a pending update (and compile
fix) that I approved.

Can someone commit it please?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227865

Thank you in advance.

-- 
best regards,
Lukasz Wasikowski
___
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: Building devel/llvm60 on FreeBSD 12.0

2018-12-18 Thread Yasuhiro KIMURA
From: Carmel NY 
Subject: Building devel/llvm60 on FreeBSD 12.0
Date: Tue, 18 Dec 2018 16:41:27 +

> Has anyone, besides me of course, had a problem building "devel/llvm60" after
> updating to FreeBSD 12.0-RELEASE?

Host:
FreeBSD rolling-vm-freebsd2.home.utahime.org 12.0-RELEASE FreeBSD 12.0-RELEASE 
r341666 GENERIC  amd64
Clean installed

Poudriere:
3.2.8

Jail:
JAILNAME VERSION ARCH  METHOD TIMESTAMP   PATH  

120amd64 12.0-RELEASEamd64 ftp2018-12-14 04:46:41 
/usr/local/poudriere/jails/120amd64   

Ports tree:
Path: /usr/ports
Working Copy Root Path: /usr/ports
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 487713
Node Kind: directory
Schedule: normal
Last Changed Author: garga
Last Changed Rev: 487713
Last Changed Date: 2018-12-18 06:02:00 +0900 (Tue, 18 Dec 2018)

Result:
https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/120amd64-local/2018-12-19_02h39m00s/logs/llvm60-6.0.1_4.log

Just FYI.

---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: devel/jsoncpp and staging?

2018-12-18 Thread Steve Kargl
On Wed, Dec 19, 2018 at 03:46:33AM +0900, Yasuhiro KIMURA wrote:
> From: Steve Kargl 
> Subject: Re: devel/jsoncpp and staging?
> Date: Tue, 18 Dec 2018 10:07:05 -0800
> 
> > Thanks for the pointer to email thread.  Guess I'll
> > upgrade from 341703 to top-of-tree and see if that
> > fixes the issue.  I reverted recent changes to sh 
> > and bmake, but those did not seem to help.
> 
> I guess the problem comes from kernel rather than userland. So I
> recommend you to upgrade or rollback kernel.
> 

Thanks for the info.  A complete buildworld/buildkernel cycle
has "fixed" the issue.

-- 
Steve
___
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?

2018-12-18 Thread bob prohaska
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"


Re: devel/jsoncpp and staging?

2018-12-18 Thread Yasuhiro KIMURA
From: Steve Kargl 
Subject: Re: devel/jsoncpp and staging?
Date: Tue, 18 Dec 2018 08:21:46 -0800

>> I cannot reproduce the error you encounter, what version of FreeBSD are
>> you running?
> FreeBSD sleepdirt 13.0-CURRENT FreeBSD 13.0-CURRENT r341703 HPC  amd64
> This corresponds to a /usr/src from Dec. 7, 2018.

I experienced same problem with 13.0-CURRENT r341690. See thread
starting with following message for more detail.

https://lists.freebsd.org/pipermail/freebsd-current/2018-December/072355.html

Regards.

---
Yasuhiro KIMURA
___
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"


Building devel/llvm60 on FreeBSD 12.0

2018-12-18 Thread Carmel NY
Has anyone, besides me of course, had a problem building "devel/llvm60" after
updating to FreeBSD 12.0-RELEASE?

My build, using poudriere, keeps ending with this error message:

c++: error: unable to execute command: Killed
c++: error: clang frontend command failed due to signal (use -v to see
invocation)
FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM
6.0.1)
Target: x86_64-unknown-freebsd12.0

My system:
uname -a
FreeBSD scorpio.seibercom.net 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC 
 amd64


Thanks!

-- 
Carmel
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: devel/jsoncpp and staging?

2018-12-18 Thread Steve Kargl
On Tue, Dec 18, 2018 at 08:54:29AM +0100, Mathieu Arnold wrote:
> On Mon, Dec 17, 2018 at 07:25:10PM -0800, Steve Kargl wrote:
> > On Mon, Dec 17, 2018 at 05:48:57PM -0800, Steve Kargl wrote:
> > > I must be missing a change in how staging works.
> > > 
> > > % cd /usr/ports/devel/jsoncpp
> > > % make
> > > 
> > > ===>  Staging for jsoncpp-1.8.1_5
> > > ===>   Generating temporary packing list
> > > (cd /usr/ports/devel/jsoncpp/work/jsoncpp-1.8.1/include/ && /bin/sh -c 
> > > '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 2>&1) &&  
> > > /usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd '\''$2'\'' 
> > > && chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd 
> > > '\''$2'\'' && chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE json/ 
> > > /usr/ports/devel/jsoncpp/work/stage/usr/local/include/jsoncpp/)
> > > chmod: json/allocator.h: No such file or directory
> > > chmod: json/assertions.h: No such file or directory
> > > chmod: json/autolink.h: No such file or directory
> > > chmod: json/config.h: No such file or directory
> > > chmod: json/features.h: No such file or directory
> > > chmod: json/forwards.h: No such file or directory
> > > chmod: json/json.h: No such file or directory
> > > chmod: json/reader.h: No such file or directory
> > > chmod: json/value.h: No such file or directory
> > > chmod: json/version.h: No such file or directory
> > > chmod: json/writer.h: No such file or directory
> > > 
> > > % ls work/stage/usr/local/include/jsoncpp/json
> > > 
> > > 
> > > Now, let's re-run make
> > > 
> > > %  make
> > 
> > Same problem with news/xpn, except running make multiple
> > times does not correct the missing files problem.  So,
> > is there away to use the ports collection with staging
> > disabled?  src.conf documents WITHOUT_STAGING, but the
> > port collections seems to ignore this varible.
> 
> src.conf is about the source tree, it has absolutely nothing to do with
> ports.  Staging is a mandatory feature of every port.

That's unfortnutely.

> I cannot reproduce the error you encounter, what version of FreeBSD are
> you running?

FreeBSD sleepdirt 13.0-CURRENT FreeBSD 13.0-CURRENT r341703 HPC  amd64

This corresponds to a /usr/src from Dec. 7, 2018.

I did not have this problem circa Oct. 5th.  That's when I 
successfully installed news/xpn.  sh(1) has had 4 commits and
bmake was updated on Dec. 5.  Perhaps, an incompatible change
has entered the tree.  The end of 'make -dA' gives

do-install:> = 
/bin/mkdir -p /usr/ports/devel/jsoncpp/work/stage/usr/local/include/jsoncpp
Execute: '/bin/mkdir -p 
/usr/ports/devel/jsoncpp/work/stage/usr/local/include/jsoncpp'
Applying[.MAKE.EXPORTED] :O to "META_MODE LANG LC_ALL LANG LC_ALL"
Result[.MAKE.EXPORTED] of :O is "LANG LANG LC_ALL LC_ALL META_MODE"
Applying[.MAKE.EXPORTED] :u to "LANG LANG LC_ALL LC_ALL META_MODE"
Result[.MAKE.EXPORTED] of :u is "LANG LC_ALL META_MODE"
Applying[GH_TAGNAME] :S to "1.8.1"
Modifier pattern: "/"
Modifier pattern: "-"
Result[GH_TAGNAME] of :S is "1.8.1"
Applying[GH_TAGNAME_SANITIZED] :C to "1.8.1"
Modifier pattern: "^[vV]([0-9])"
Modifier pattern: "\1"
Result[GH_TAGNAME_SANITIZED] of :C is "1.8.1"
Applying[GH_TAGNAME_SANITIZED] :S to "1.8.1"
Modifier pattern: "+"
Modifier pattern: "-"
Result[GH_TAGNAME_SANITIZED] of :S is "1.8.1"
(cd /usr/ports/devel/jsoncpp/work/jsoncpp-1.8.1/include/ && /bin/sh -c 
'(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 2>&1) &&  
/usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd '\''$2'\'' && 
chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd '\''$2'\'' && 
chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE json/ 
/usr/ports/devel/jsoncpp/work/stage/usr/local/include/jsoncpp/)
Execute: '(cd /usr/ports/devel/jsoncpp/work/jsoncpp-1.8.1/include/ && /bin/sh 
-c '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 2>&1) &&  
/usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd '\''$2'\'' && 
chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd '\''$2'\'' && 
chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE json/ 
/usr/ports/devel/jsoncpp/work/stage/usr/local/include/jsoncpp/)'
Applying[.MAKE.EXPORTED] :O to "META_MODE LANG LC_ALL LANG LC_ALL"
Result[.MAKE.EXPORTED] of :O is "LANG LANG LC_ALL LC_ALL META_MODE"
Applying[.MAKE.EXPORTED] :u to "LANG LANG LC_ALL LC_ALL META_MODE"
Result[.MAKE.EXPORTED] of :u is "LANG LC_ALL META_MODE"
+ cd /usr/ports/devel/jsoncpp/work/jsoncpp-1.8.1/include/
+ /bin/sh -c $'(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 
2>&1) &&  /usr/bin/find -Ed $1 $3 \\(   -type d -exec /bin/sh -c \'cd \'$2\' && 
chmod 755 "$@"\' . {} +  -o -type f -exec /bin/sh -c \'cd \'$2\' && chmod 0644 
"$@"\' . {} + \\)' COPYTREE_SHARE json/ 
/usr/ports/devel/jsoncpp/work/stage/usr/local/include/jsoncpp/
chmod: json/allocator.h: No such file or directory
chmod: json/assertions.h: No such file or directory
chmod: json/autolink.h: No such file or directory
chmod: json/config.h: No such 

FreeBSD ports you maintain which are out of date

2018-12-18 Thread portscout
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
mail/libetpan   | 1.9.1   | 1.9.2
+-+
x11-toolkits/granite| 0.5 | 5.2.2
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
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"