Re: Bind9 security upgrade

2021-02-06 Thread DutchDaemon - FreeBSD Forums Administrator 

On 06/02/2021 20:53, bob prohaska wrote:

perl5-5.32.0_1
perl5.30-5.30.3_1


The former is correct; no idea where the latter comes from; Perl 5.30 
usually looks like 'perl5-5.30.0'.


Older version follow that notation (perl5-5.26.2).

Manual install?

I don't know what to advise you here? I would probably nuke my installed 
ports (pkg delete -a -f -y), clear out /usr/local/ (except 
/usr/local/etc) and make sure that the ports tree is current, and start 
over.




OpenPGP_signature
Description: OpenPGP digital signature

Re: Bind9 security upgrade

2021-02-06 Thread DutchDaemon - FreeBSD Forums Administrator 

On 06/02/2021 18:31, bob prohaska wrote:

On Sat, Feb 06, 2021 at 06:03:38PM +0100, DutchDaemon - FreeBSD Forums 
Administrator wrote:

On 06/02/2021 17:50, bob prohaska wrote:

Would installing the autoconf port install autoreconf?

autoconf-wrapper-20131203 is a requirement of autoconf-2.69_3, so yes.


Aye, there's the rub:

root@pelorus:/usr/ports/devel/autoconf # make -DBATCH > make.log
./configure: /usr/local/bin/perl: not found
configure: error: Perl 5.006 or better is required
root@pelorus:/usr/ports/devel/autoconf #

Which closes the circle back the perl problem:

root@pelorus:/usr/ports/devel/autoconf # perl -v
perl: Command not found.
root@pelorus:/usr/ports/devel/autoconf # whereis perl
perl: /usr/local/lib/perl5/5.30/perl/man/man1/perl.1.gz 
/usr/ports/devel/git/work-default/git-2.30.0/perl
root@pelorus:/usr/ports/devel/autoconf #

It looks like perl isn't installed, but also isn't recognized as a
dependency that needs to be compiled. The existence of libs and
man but no bin seems odd.

At this point I'm baffled. Must I install some version of perl
manually from ports?


It should be pulled in:

/usr/ports/devel/autoconf > # make all-depends-list
/usr/ports/ports-mgmt/pkg
/usr/ports/devel/m4
/usr/ports/print/texinfo
/usr/ports/misc/help2man
/usr/ports/devel/p5-Locale-gettext
/usr/ports/devel/gettext-tools
/usr/ports/devel/libtextstyle
/usr/ports/converters/libiconv
/usr/ports/print/indexinfo
/usr/ports/devel/gettext-runtime
>>> /usr/ports/lang/perl5.32
/usr/ports/devel/gmake
/usr/ports/devel/p5-Locale-libintl
/usr/ports/converters/p5-Text-Unidecode
/usr/ports/textproc/p5-Unicode-EastAsianWidth
/usr/ports/devel/autoconf-wrapper

Your system appears to belive it /has/ Perl. What does pkg info -ix perl 
yield?


OpenPGP_signature
Description: OpenPGP digital signature

Re: Bind9 security upgrade

2021-02-06 Thread DutchDaemon - FreeBSD Forums Administrator 

On 06/02/2021 17:50, bob prohaska wrote:

Would installing the autoconf port install autoreconf?


autoconf-wrapper-20131203 is a requirement of autoconf-2.69_3, so yes.



OpenPGP_signature
Description: OpenPGP digital signature

Re: Testing official self-extract makeself .run fails to extract / anyone could test it?

2021-01-15 Thread DutchDaemon - FreeBSD Forums Administrator 

On 15/01/2021 12:38, Nuno Teixeira wrote:

Hello,

I need that someone test official archivers/makeself self-extratable bin to
see if error is the same:

https://github.com/megastep/makeself/issues/238

Download link:
https://github.com/megastep/makeself/releases/download/release-2.4.2/makeself-2.4.2.run

Run: sh makeself-2.4.2.run

Thanks,

Nuno Teixeira


# ./makeself-2.4.2.run
Creating directory makeself-2.4.2
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing Makeself v2.4.2  100%   ... Extraction failed.
Terminated

--

# sh -x makeself-2.4.2.run
+ umask
+ ORIG_UMASK=0022
+ test n '=' n
+ umask 077
+ CRCsum=3945225848
+ MD5=6ec4e617e8ed15e4612e05e0a8ad18cd
+ SHA=
+ TMPROOT=/tmp
+ USER_PWD=/tmp/test
+ export USER_PWD
+ ARCHIVE_DIR=.
+ export ARCHIVE_DIR
+ label='Makeself v2.4.2'
+ script=echo
+ scriptargs='Makeself has extracted itself'
+ cleanup_script=''
+ licensetxt=''
+ helpheader=''
+ targetdir=makeself-2.4.2
+ filesizes=31397
+ keep=y
+ nooverwrite=n
+ quiet=n
+ accept=n
+ nodiskspace=n
+ export_conf=n
+ decrypt_cmd=''
+ skip=668
+ print_cmd_arg=''
+ type printf
+ print_cmd=printf
+ test -d /usr/xpg4/bin
+ test -d /usr/sfw/bin
+ unset CDPATH
+ finish=true
+ xterm_loop=''
+ noprogress=n
+ nox11=n
+ copy=none
+ ownership=n
+ verbose=n
+ cleanup=y
+ cleanupargs=''
+ initargs=''
+ true
+ break
+ test xn '=' xy -a xn '=' xy
+ id -u
+ test xn '=' xy -a 0 -ne 0
+ test xnone '!=' xphase2
+ MS_PrintLicense
+ test x '!=' x
+ test xn '=' xn
+ tty -s
+ :
+ test xmakeself-2.4.2 '=' x.
+ test xy '=' xy
+ test xn '=' xy
+ test xn '=' xn
+ echo 'Creating directory makeself-2.4.2'
Creating directory makeself-2.4.2
+ tmpdir=makeself-2.4.2
+ dashp=-p
+ mkdir -p makeself-2.4.2
+ pwd
+ location=/tmp/test
+ test x '!=' x1
+ MS_Check makeself-2.4.2.run
+ 
OLD_PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin:
+ 
PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin::/bin:/usr/bin:/sbin:/usr/local/ssl/bin:/usr/local/bin:/opt/openssl/bin

+ MD5_ARG=''
+ exec
+ MD5_PATH=''
+ test -x ''
+ exec
+ MD5_PATH=/sbin/md5
+ test -x /sbin/md5
+ 
PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin:

+ exec
+ SHA_PATH=/usr/local/bin/shasum
+ test -x /usr/local/bin/shasum
+ test xn '=' xn
+ MS_Printf 'Verifying archive integrity...'
+ printf 'Verifying archive integrity...'
Verifying archive integrity...+ head -n 668 makeself-2.4.2.run
+ wc -c
+ tr -d ' '
+ offset=16914
+ verb=''
+ i=1
+ echo 3945225848
+ cut '-d ' -f1
+ crc=3945225848
+ test -x /usr/local/bin/shasum
+ basename /usr/local/bin/shasum
+ test xshasum '=' xshasum
+ SHA_ARG='-a 256'
+ echo 
+ cut '-d ' -f1
+ sha=
+ test x 
'=' x

+ test x '=' xy
+ test -x /sbin/md5
+ basename /sbin/md5
+ test xmd5 '=' xdigest
+ echo 6ec4e617e8ed15e4612e05e0a8ad18cd
+ cut '-d ' -f1
+ md5=6ec4e617e8ed15e4612e05e0a8ad18cd
+ test x6ec4e617e8ed15e4612e05e0a8ad18cd '=' 
x

+ MS_dd_Progress makeself-2.4.2.run 16914 31397
+ test xn '=' xy
+ file=makeself-2.4.2.run
+ offset=16914
+ length=31397
+ pos=0
+ bsize=4194304
+ test 4194304 -gt 31397
+ expr 4194304 / 4
+ eval '/sbin/md5 '
+ /sbin/md5
+ cut -b-32
+ bsize=1048576
+ test 1048576 -gt 31397
+ expr 1048576 / 4
+ bsize=262144
+ test 262144 -gt 31397
+ expr 262144 / 4
+ bsize=65536
+ test 65536 -gt 31397
+ expr 65536 / 4
+ bsize=16384
+ test 16384 -gt 31397
+ expr 31397 / 16384
+ blocks=1
+ expr 31397 % 16384
+ bytes=15013
+ dd 'ibs=16914' 'skip=1' 'count=0'
+ expr 0 + 16384
+ pos=16384
+ MS_Printf ' 0%% '
+ printf ' 0%% '
 0% + test 1 -gt 0
+ test 16384 -le 31397
+ dd 'bs=16384' 'count=1'
+ expr 31397 / 100
+ pcent=313
+ expr 16384 / 313
+ pcent=52
+ test 52 -lt 100
+ MS_Printf '\b\b\b\b\b\b\b'
+ printf '\b\b\b\b\b\b\b'
+ test 52 -lt 10
+ MS_Printf '   52%% '
+ printf '   52%% '
   52% + expr 16384 + 16384
+ pos=32768
+ test 32768 -le 31397
+ test 15013 -gt 0
+ dd 'bs=15013' 'count=1'
+ MS_Printf '\b\b\b\b\b\b\b'
+ printf '\b\b\b\b\b\b\b'
+ MS_Printf ' 100%%  '
+ printf ' 100%%  '
 100%  + md5sum=6ec4e617e8ed15e4612e05e0a8ad18cd
+ test x6ec4e617e8ed15e4612e05e0a8ad18cd '!=' 
x6ec4e617e8ed15e4612e05e0a8ad18cd

+ test xn '=' xn
+ MS_Printf ' MD5 checksums are OK.'
+ printf ' MD5 checksums are OK.'
 MD5 checksums are OK.+ crc=00
+ verb=n
+ test

Re: mail/milter-greylist aborts

2021-01-12 Thread DutchDaemon - FreeBSD Forums Administrator 

On 12/01/2021 11:42, DutchDaemon - FreeBSD Forums Administrator wrote:

On 11/01/2021 22:39, Greg Rivers via freebsd-ports wrote:
since the update from 4.6.2 to 4.6.3 today. It starts, but as soon as 
the MTA writes to the listening socket, it aborts, e.g.:


pid 54733 (milter-greylist), jid 0, uid 26: exited on signal 6

resulting in:
sm-mta[54648]: 10BKxX7b054648: Milter (greylist): error connecting to 
filter: Connection refused by /var/milter-greylist/milter-greylist.sock

sm-mta[54648]: 10BKxX7b054648: Milter (greylist): to error state
sm-mta[54648]: 10BKxX7b054648: Milter: initialization failed, temp 
failing commands


Is anyone else seeing this?


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252516 - patch 
available




A quick fix is to rebuild the port with GeoIP2 toggled to off.



OpenPGP_signature
Description: OpenPGP digital signature

Re: mail/milter-greylist aborts

2021-01-12 Thread DutchDaemon - FreeBSD Forums Administrator 

On 11/01/2021 22:39, Greg Rivers via freebsd-ports wrote:

since the update from 4.6.2 to 4.6.3 today. It starts, but as soon as the MTA 
writes to the listening socket, it aborts, e.g.:

pid 54733 (milter-greylist), jid 0, uid 26: exited on signal 6

resulting in:
sm-mta[54648]: 10BKxX7b054648: Milter (greylist): error connecting to filter: 
Connection refused by /var/milter-greylist/milter-greylist.sock
sm-mta[54648]: 10BKxX7b054648: Milter (greylist): to error state
sm-mta[54648]: 10BKxX7b054648: Milter: initialization failed, temp failing 
commands

Is anyone else seeing this?


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252516 - patch available



OpenPGP_signature
Description: OpenPGP digital signature

Re: Can anyone build www/node right now?

2020-06-28 Thread DutchDaemon - FreeBSD Forums Administrator 
On 2020-06-28 22:49, Christoph Moench-Tegeder wrote:
> ## Dutch Daemon - FreeBSD Forums Administrator (dutchdae...@freebsd.org):
>
>> In absence of a make.conf in the jail it pulled in python36-3.6.11 as the 
>> default.
> Uhm. From your log, we see that you have a make.conf with a python
> version override:
>
>  95.  /usr/local/etc/poudriere.d/testamd64-make.conf 
>  [...]
> 116. DEFAULT_VERSIONS= perl5=5.30 python=3.6 python3=3.6 php=73 apache=2.4 
> mysql=56 ssl=openssl
>
> The default "default python" is 3.7.


Ah, it pulled in the generic /etc/make.conf., which was never there
until I tested something (else) with it; forgot to remove it.

I'll try Python 3.7 in all of the build jails that need www/node and
remove the hard Python default.

Thanks guys!




signature.asc
Description: OpenPGP digital signature

Can anyone build www/node right now?

2020-06-28 Thread DutchDaemon - FreeBSD Forums Administrator 
I have tried to build www/node for weeks now, and it always fails. This is on a 
fresh Poudriere jail, amd64, 12.1-REL-p6.

Opened a ticket for it, with full output, but no response yet. To rule any 
interference out, I built this in a clean jail, without any make.conf or port 
options, bog standard defaults.

All 33 (from pkg to binutils) dependencies built correctly (as was always the 
case), but www/node bombed on the same error as always.

See https://pastebin.pl/view/3a6f48db for this latest clean build; the error is 
invariably:

---
Traceback (most recent call last):

  File "tools/genv8constants.py", line 23, in 

    bufsize=-1, stdout=subprocess.PIPE, text=True).stdout

TypeError: __init__() got an unexpected keyword argument 'text'

gmake[2]: *** [node_dtrace_ustack.target.mk:13: 
/wrkdirs/usr/ports/www/node/work/node-v14.4.0/out/Release/obj/gen/v8constants.h]
 Error 1

gmake[2]: *** Waiting for unfinished jobs

rm ad3fd4c76aef3b4797bbb2572833f9000cee0294.intermediate 
ea2d89ddb30e54c8a8d75f33fc84b228111d7c67.intermediate 
ed36ab92458644e121416e8697a6b64c051c72b0.intermediate

gmake[1]: *** [Makefile:101: node] Error 2

gmake[1]: Leaving directory '/wrkdirs/usr/ports/www/node/work/node-v14.4.0'

===> Compilation failed unexpectedly.

Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to

the maintainer.

*** Error code 1
---

Previous build attempts on 12-REL-p5 amd 64, with clean and resued jails:

https://pastebin.pl/view/4953a503
https://pastebin.pl/view/db278ac3
https://pastebin.pl/view/e3c16e57
https://pastebin.pl/view/f3fcdfbf



signature.asc
Description: OpenPGP digital signature

Re: Updating Samba

2019-06-20 Thread DutchDaemon - FreeBSD Forums Administrator 
On 2019-06-20 14:17, Carmel NY wrote:
> The 20190619 entry in "UPDATING" recommends certain actions for
> updating Samba4[6-8] utilizing either 'portmaster' or 'portupgrade'.
> Are there4 any special actions that have to be taken if utilizing


Poudriere built the ports correctly; I did have to run pkg upgrade twice
because of conflicting dependencies; which were solved by running it twice.




signature.asc
Description: OpenPGP digital signature

Re: openssl problem

2017-10-24 Thread DutchDaemon - FreeBSD Forums Administrator 
On 24-10-2017 16:00, Ernie Luzar wrote:
> I do "pkg install openssl" that works ok.
>
> But from that point I get 2 different messages at port make time
> depending on the port being installed.
>
> /usr/ports/sysutils/qjail >make install clean
> /!\ WARNING /!\
>
> You have security/openssl installed but do not have
> DEFAULT_VERSIONS+=ssl=openssl set in your make.conf
>
> Which stops if I add DEFAULT_VERSIONS+=ssl=openssl to /etc/make.conf
>
>
> Get this error all the time, even with /etc/make.com populated with
> DEFAULT_VERSIONS+=ssl=openssl
>
> /usr/ports/www/links >make install clean
> make: "/usr/ports/Mk/Uses/ssl.mk" line 77: You are using
> an unsupported SSL provider openssl
>
> I see this needing 2 solutions.
>
> 1. The openssl port needs to be changes so it populates /etc/make.conf
> with DEFAULT_VERSIONS+=ssl=openssl
>
> 2. The /usr/ports/Mk/Uses/ssl.mk" line 77 needs to be changed to
> resolve this bogus error message.
>
> Any thoughts on these solutions?
> ___
> 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"

Just use something that looks like this:


DEFAULT_VERSIONS=  perl5=5.24 python=2.7 python2=2.7 php=56 apache=2.2
mysql=56 ssl=openssl





signature.asc
Description: OpenPGP digital signature

Re: Portmaster error

2017-09-27 Thread DutchDaemon - FreeBSD Forums Administrator 
On 27-9-2017 17:22, Paul Schmehl wrote:
> I'm running a 10.3-RELEASE instance. I ran portmaster -ad in screen yesterday 
> to get all the ports up to date. Today I ran it again, to make sure 
> everything was updated. > > When I did, I got this error: > > portmaster -ad 
> > ===>>> Gathering
distinfo list for installed ports > > ===>>> Starting check of installed
ports for available updates > make: "/usr/ports/Mk/bsd.port.mk" line
1462: Cannot open /usr/ports/Mk/Uses/execinfo.mk > make: Fatal errors
encountered -- cannot continue > ===>>> All ports are up to date
I recommend you take a look at an earlier thread:

https://docs.freebsd.org/cgi/getmsg.cgi?fetch=24689+0+current/freebsd-ports

If all else fails, I advise you to:

rm /var/db/portsnap/tag
portsnap fetch extract




signature.asc
Description: OpenPGP digital signature

Re: Apache24 unable to find libphp5.so

2017-09-26 Thread DutchDaemon - FreeBSD Forums Administrator 
On 26-9-2017 15:31, Carmel NY wrote:
> I just did a clean installation of FreeBSD-11.1. I have gotten everything up
> and running except, I cannot find the "libphp5.so" module. Apache24 complains
> that it is not present and quits.
>
> What port installs that module? I cannot seem to locate it.
>
> Thanks :)
>
E.g. www/mod_php56 (or any other PHP version you need)





signature.asc
Description: OpenPGP digital signature

Re: FreeBSD Port: MailScanner-5.0.3

2017-07-28 Thread DutchDaemon - FreeBSD Forums Administrator 
On 28-7-2017 22:48, Chris Rees wrote:
> I've committed a fix using @sample for the config files, and fixed the
> regexes for paths.  @sample keyword was made for ports like this...
> 
> The port will no longer destroy your configuration.
> 
> Cheers,
> 
> Chris 

Good news, Chris. Thanks for your efforts!




signature.asc
Description: OpenPGP digital signature

Re: firefox is pretty useless ...

2017-07-11 Thread DutchDaemon - FreeBSD Forums Administrator 
On 5-7-2017 08:07, DTD wrote:
> if you use xfce. By definition it is not a problem that:
>
>   1) install a new copy of FreeBSD 10.3
>   2) pkg install xorg
>   3) pkg install xfce
>   4) pkg install firefox
>
> installs a firefox package that does not run. The project seems to do
> a bit
> better than this on Windows, but they (I think) have to in that
> environment. The
> official answer to the above is:
>
> --- Comment #1 from Jan Beich  ---
> Partial upgrades i.e., mixing dependencies from different svn
> checkouts, dates
> of "pkg install" or locking dependencies, are not supported. firefox will
> refuse to build unless you upgrade sqlite3. Some version requirement are
> specified in the port's Makefile
>
>   $ fgrep sqlite www/firefox/Makefile
>   sqlite3>=3.17.0:databases/sqlite3 \
>   ${PYTHON_PKGNAMEPREFIX}sqlite3>0:databases/py-sqlite3 \
>
> "pkg upgrade" may help you resolve this.
>
> The only problem with this 'solution' is that upgrading sqlite requires a
> cascading series of updates that breaks parts of xfce. Other than that no
> problem here. So if you use twm firefox is your browser.
>
> The next time I build a system I will try installing firefox first. I
> got here because I wanted to ungrade thunar (xfce's file manager).
> That upgrade broke
> the version of firefox that was running (47.somethine). Chasing and
> fixing that chain eventually required a reinstall. Happily (for me)
> chrome works.

Might this be 10.3-specific?

I'm running Firefox 54.0.1_1,1 on xorg-server 1.18.4_3,1 and xfce
4.12_1, on 11.0-REL-p9 amd64. No problems.

Built on Poudriere, but I ran the same stuff from the offical repo for a
while as well.




signature.asc
Description: OpenPGP digital signature

Re: FreeBSD Port: MailScanner-5.0.3

2017-06-19 Thread DutchDaemon - FreeBSD Forums Administrator 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
 
On 19-6-2017 07:18, Jeff Sickel wrote:
> The MailScanner-5.0.3 update didn’t keep the /usr/local and other FreeBSD 
> standard namespace in place.  I spent quite a bit of time correcting the perl 
> scripts to pick up the /usr/local install locations after the upgrade.  The 
> configuration files and other core pieces of MailScanner seem to keep more 
> standard Linux namespaces with this release.  An upgrade from earlier 
> versions is not recommended on FreeBSD until the correct file locations are 
> handled by default.
Yeah .. https://forums.freebsd.org/threads/61298/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
 
iQEcBAEBCAAGBQJZR772AAoJEA9a9BMWOKcx4u4IALFdgmHYH78bvPlL8ALqZiLw
4Ma9mS73sP98XuSWcKUWzI3c+6piT0Qk1RAn/+OGEK2hj99TNTDWQjOt9Ttlr4TN
iOiA3e9+gsKW3M9TrCzoOTGYj7sDagdzLgU3mH/xfTeHWKyM7J3KFEdqIpV267g6
3Ft69e6A3aUIrqMEtGx6qFl/F2NegoEZrmwMdDGiHceZlPn8wRoc0GPRCZUOZS2B
DvEZuU7tARQ8PaH0H84NL9r7t9e3N84328sPwqll2YyAsymU1Cjvi0MjKppqtFgz
KfwCrIi6AM/h6dkz1vR0eB4HoM/MfC1in0gQSR8nlCStT9iLvFePyOiRmjs0svc=
=HMeS
-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: sysutils/tmux - strange behaviour with new version 2.4

2017-05-15 Thread DutchDaemon - FreeBSD Forums Administrator 
On 15-5-2017 19:18, Miroslav Lachman wrote:
> I noticed some strange behaviours with Tmux 2.4.
> If I run "cat /path/to/somefile.txt" sometimes part of file is missing
> in the output (no special characters in this text file, it is log of
> "pkg upgrade")
>
> And I thing some key presses are interpreted differently. (in Vim)
>
> I know that nobody can solve this without more details... so I am just
> asking if I am alone or somebody else have this problem too?
>
> Miroslav Lachman

You're ringing a bell. I wanted to mail someone the content of a shell
script, which I printed in tmux using `cat`. When I pasted the output in
my mail program it seemed to be missing a block of text, which was
commented out in the script. So there may be some unwanted interaction
going on with lines starting with #, perhaps?



signature.asc
Description: OpenPGP digital signature

Re: www/chromium build failure on 12-CURRENT

2017-01-11 Thread DutchDaemon - FreeBSD Forums Administrator 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 11-1-2017 21:43, Dimitry Andric wrote:

>> http://chopapp.com/#372r5yj
> 
> Ok, the actual error was just a few lines above:
> 
> ../../third_party/angle/src/libANGLE/renderer/gl/glx/FunctionsGLX.cpp:
15:10:
>
>
>
> 
fatal error: 'GL/glx.h' file not found #include  ^ 1
> error generated.
> 
> So for some reason it cannot find your glx.h file.  Do you have the
> libGL port installed?  I didn't see it being installed in the 
> build-depends stage.

It is installed on the laptop for which this jail is building. If it
is not pulled in by the www/chromium build in a (logically clean,
because always newly created) Poudriere build jail, there might be
something in the port that doesn't pull it in, or there might be
something that looks for it in the wrong location.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJYdpqyAAoJEA9a9BMWOKcxnMQIAIv82PSwB3L3FSpqzpnJ6/sI
yhLdB9A7JeDlxrlbq5sTPkN+Rt+QB7YMJty3AaZdQDSkhTl9cBJVl1n4QljzRwdj
gXGCpIcCSO3q6OrWmgOdJu7gDVhwBL7LsYe6oRQbqa+wNC03pacY9HlrmNpHygsf
T5jsTt8+n8aXd7amp2/29S1JHjZongTY8SpWM7SR/qYbXtr0jNZO+kjcLf0AQRZP
gVZAZoWgeT6WZbwv1J7RaLuvGTFeQehjjbvMfYvlHf1VSypxrg4kRlRYADGOT/qi
dMCBg5QAtn4HsKlV5DeqGhAP1Dv/b4SnJckOtgqsoorebXULiMKopg2pnqxUQ8c=
=XTTG
-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: www/chromium build failure on 12-CURRENT

2017-01-11 Thread DutchDaemon - FreeBSD Forums Administrator 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 11-1-2017 20:54, Dimitry Andric wrote:
> On 11 Jan 2017, at 19:50, DutchDaemon - FreeBSD Forums
> Administrator <dutchdae...@freebsd.org> wrote:

> This must be a different issue, but I don't see the missing header
> you referred to in those log messages?  Do you have a full log
> posted somewhere?

'Missing header' is actually what Poudriere reports on its summary.

chromium-54.0.2840.100_1www/chromiumbuild   0   missing_header

Full Poudriere output:

http://chopapp.com/#372r5yj


-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJYdpRYAAoJEA9a9BMWOKcxnzAH/2vMWX6jsxSudrHfodVXCFDZ
HjLa6TLs9IEYS41sZNgUwGCkocLG3sn5/qTDMMLNxnKFZ7u30PxbCLvgkeRc8LU9
KU1neEjQBF7vQwe/zFPqpDw8hHlDR8WQAjongAUU1y4YQbl/AfL3W1ZV9zNDGI/r
PjmkL/GDdVb4v1PU/FgfdnNgbY0Oi2Lggq9WLxYHnGHi6tI3Jr+tuolQSo/8xXt6
uMSVVeP0qjOyf3dCe7iCCWazi9p2AD8WzEv5iAljbDr/t5+MwDshvSDoRH9dIAnb
QtmfBezs+iKAbVuPS1Jw1v0TbMx/6WOYlrrkZMeVI8UREWrQCr1QD7aT6klPRg4=
=XcD2
-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: www/chromium build failure on 12-CURRENT

2017-01-11 Thread DutchDaemon - FreeBSD Forums Administrator 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
 
On 11-1-2017 17:28, Steve Kargl wrote:
> On Wed, Jan 11, 2017 at 11:01:21AM -0500, Shawn Webb wrote: >> Hey All, >> >> 
> It looks like www/chromium fails to build on
12-CURRENT. Has anyone else >> run into this? >> > > Yep.  It is due to
chasing bleeding edge clang. > >> >> clang++39 >> > >
/c++/v1/__config:58:2: error: "_LIBCPP_TRIVIAL_PAIR_COPY_CTOR" is no >
longer supported.  use
_LIBCPP_DEPRECATED_ABI_DISABLE_PAIR_TRIVIAL_COPY_CTOR > instead > #error
"_LIBCPP_TRIVIAL_PAIR_COPY_CTOR" is no longer supported. \ > ^ > 1 error
generated. > > https://reviews.llvm.org/D27277 >
I can't build it on 11 (latest patch level) either. It keeps throwing a
'missing header'. (Poudriere).

clang++39 -MMD -MF obj/third_party/angle/libANGLE/formatutilsgl.o.d
-DLIBANGLE_IMPLEMENTATION -DV8_DEPRECATION_WARNINGS -DENABLE_MDNS=1
-DENABLE_NOTIFICATIONS -DENABLE_PEPPER_CDMS -DENABLE_PLUGINS=1
-DENABLE_PDF=1 -DENABLE_PRINTING=1 -DENABLE_BASIC_PRINTING=1
-DENABLE_PRINT_PREVIEW=1 -DENABLE_SPELLCHECK=1
-DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 -DUSE_PANGO=1 -DUSE_CAIRO=1
-DUSE_CLIPBOARD_AURAX11=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_GLIB=1
-DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DENABLE_WEBRTC=1
-DDISABLE_NACL -DENABLE_EXTENSIONS=1 -DENABLE_TASK_MANAGER=1
-DENABLE_THEMES=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1
-DENABLE_SESSION_SERVICE=1 -DENABLE_SUPERVISED_USERS=1
-DENABLE_SERVICE_DISCOVERY=1 -DUSE_PROPRIETARY_CODECS
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
-DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED
-DCR_CLANG_REVISION=278861-1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
-D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0
-DANGLE_ENABLE_OPENGL -DANGLE_USE_X11 -DGL_GLEXT_PROTOTYPES
-DEGL_EGLEXT_PROTOTYPES
-DGL_APICALL=__attribute__\(\(visibility\(\"default\"\)\)\)
-DEGLAPI=__attribute__\(\(visibility\(\"default\"\)\)\)
-DANGLE_TRANSLATOR_STATIC
-I../../third_party/angle/src/third_party/khronos -I/usr/local/include
-Igen/angle -I../../third_party/angle/include
-I../../third_party/angle/src
-I../../third_party/angle/src/common/third_party/numerics
-I../../third_party/angle/include -I../../third_party/angle/src
-I../../third_party/angle/include -fno-strict-aliasing
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe
-fcolor-diagnostics
-fdebug-prefix-map=/wrkdirs/usr/ports/www/chromium/work/chromium-54.0.2840.100=.
-pthread -m64 -march=x86-64 -Wall -Wextra
-Wno-missing-field-initializers -Wno-unused-parameter
-Wno-c++11-narrowing -Wno-covered-switch-default
-Wno-deprecated-register -Wno-unneeded-internal-declaration
-Wno-inconsistent-missing-override -Wno-shift-negative-value
-Wno-undefined-var-template -Wno-nonportable-include-path -O2 -fno-ident
-fdata-sections -ffunction-sections -g0 -fvisibility=hidden
-Wheader-hygiene -Wstring-conversion -D_THREAD_SAFE
-fno-threadsafe-statics -fvisibility-inlines-hidden -std=gnu++11
-fno-rtti -fno-exceptions -c
../../third_party/angle/src/libANGLE/renderer/gl/formatutilsgl.cpp -o
obj/third_party/angle/libANGLE/formatutilsgl.o
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/chromium
>> Cleaning up wrkdir
===>  Cleaning for chromium-54.0.2840.100_1
build of www/chromium ended at Wed Jan 11 04:26:05 CET 2017
build time: 00:10:22
!!! build failure encountered !!!

-BEGIN PGP SIGNATURE-
Version: GnuPG v2
 
iQEcBAEBCAAGBQJYdn6NAAoJEA9a9BMWOKcxm2IH/A3Jf5Id7EnNvm7XtNpP/Cx6
/lYjEDl99c3Pfr1URAErAz76jcIhUU5TSzSEMMgNcThfwODskqJf7kVhSlND/nNj
lyKurvymgSmIkRnGdP2McBBKP4sHz54VKYJSvOlK5yeeZ9B3nCM1UC4hsRmMLFx8
qVl29NCNAYBgkRo/uoHX6EC7llqUqXjc6Zwhu3Y6qhrsxKEiaq7a0eHXnK5YIARo
eLUkC0mdRlKPU0IDSuW4IGJMTBzHMK4m3NJqfbfACt16/9nigHH7MEvijKMOB6g1
kz9DP8UMIpI27ObOyillG6V1omcGtZZN7n84PQc5nE1pex1b5/dcKO8szigE2ic=
=Inai
-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"

LogZilla looking for FreeBSD port development

2016-08-22 Thread DutchDaemon - FreeBSD Forums Administrator 
After some contact with LogZilla for use in my own company, we had a
conversation about the advantages of having an out-of-the-box LogZilla
installation for FreeBSD (either a port or a binary package). They asked
me to forward this:

LogZilla would like to speak to any FreeBSD experts who are interested
in working with them to create and document an installation package in
order to allow FreeBSD to be compatible with their network management
software. Please send an email to Pete Willis ( p w i l l i s [ a t ] l
o g z i l l a . n e t ) for discussion.



signature.asc
Description: OpenPGP digital signature