pkg regression 1.1.4_10 -> 1_2.1: ia64 segfault

[Anton Shterenlikht]

http://eis.bris.ac.uk/~mexas/pkg-1.2_1.log

Anton
___
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"

install tcpdump 4.5.1 and libpcap 1.5.1 to filter in/out trafic

[Rodrigo Osorio]

Hi all,

In order to take advantage of the new '-P' switch in
tcpdump to filter in/out trafic from an interface, I
need to move from tcpdump 4.4.0 to 4.5.1.

http://www.tcpdump.org/tcpdump_man.html

I did a set of minimal patches to upgrade tcpdump and
its companion libpcap in ports to the latest versions.

In our tests (FreeBSD-i386-9.1-RELEASE and i386-10.0-BETA1)
tcpdump 4.5.1 works fine and capture the desired trafic.

I didn't perform any test to check if the deinstall/package
works, this will come with a future PR.

regards
 -rodrigo


http://files.bebik.net/patches/tcpdump-4.5.1/tcpdump-patch
http://files.bebik.net/patches/tcpdump-4.5.1/pcap-patch
 
___
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"

(bsd)patch vs ports

[Andriy Gapon]

When building ports on head I sometimes see messages like the following during a
patch phase:

===>  Applying FreeBSD patches for firefox-25.0_1,1
No such line 262 in input file, ignoring
===>  Applying NSS patches
No such line 194 in input file, ignoring
No such line 658 in input file, ignoring
No such line 52 in input file, ignoring
No such line 45 in input file, ignoring

Is this a cause for concern?
Do those messages mean that potentially important patches are not actually 
applied?

-- 
Andriy Gapon
___
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"

something messed up with latest pkg update?

[Ruslan Makhmatkhanov]

portsnap fetch update
pkg version -vl "<"
portmaster pkg-1.1.4_10

Got some warnings:
pkg-static: PACKAGESITE in pkg.conf is deprecated. Please create a 
repository configuration file
pkg-static: Warning: expecting a boolean for the 'enabled' key of the 
'FreeBSD' repo,  the value has been correctly converted, please consider 
fixing

pkg-static: unable to open vulnxml file, try running 'pkg audit -F' first

Fixed 1st and 3rd. What it is supposed to do with 2nd one?

Then, trying to update some ports:

portmaster ruby19-gems-1.8.25 gnuchess-6.1.0 libssh-0.5.2_1 
libunibreak-1.0,1 libxml2-2.8.0_2 nmap-6.40 pciids-20131119


"""
===>>> Working on:
ruby19-gems-1.8.25
gnuchess-6.1.0
libssh-0.5.2_1
libunibreak-1.0,1
libxml2-2.8.0_2
nmap-6.40
pciids-20131119

===>>> Gathering distinfo list for installed ports

===>>> No ORIGIN in /var/db/pkg/ruby19-gems-1.8.25/+CONTENTS


===>>> ruby19-gems-1.8.25 1/7
===>>> No ORIGIN in /var/db/pkg/ruby19-gems-1.8.25/+CONTENTS


===>>> Cannot continue
===>>> Aborting update

===>>> Update for ruby19-gems-1.8.25 failed
===>>> Aborting update

===>>> Killing background jobs
Terminated
===>>> Exiting
"""

Got this "No ORIGIN"  messages for every port that I try to update. Is 
this known issue? How to handle that?


--
Regards,
Ruslan

T.O.S. Of Reality
___
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: something messed up with latest pkg update?

[Łukasz Wąsikowski]

W dniu 2013-11-27 10:55, Ruslan Makhmatkhanov pisze:

> Got some warnings:
> pkg-static: PACKAGESITE in pkg.conf is deprecated. Please create a
> repository configuration file
> pkg-static: Warning: expecting a boolean for the 'enabled' key of the
> 'FreeBSD' repo,  the value has been correctly converted, please consider
> fixing
> pkg-static: unable to open vulnxml file, try running 'pkg audit -F' first
> 
> Fixed 1st and 3rd. What it is supposed to do with 2nd one?

Try enabled: yes (without quotes) in pkg.conf.

-- 
best regards,
Lukasz Wasikowski
___
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: something messed up with latest pkg update?

[Sergey V. Dyatko]

On Wed, 27 Nov 2013 13:55:52 +0400
Ruslan Makhmatkhanov  wrote:

> portsnap fetch update
> pkg version -vl "<"
> portmaster pkg-1.1.4_10
> 
> Got some warnings:
> pkg-static: PACKAGESITE in pkg.conf is deprecated. Please create a 
> repository configuration file
> pkg-static: Warning: expecting a boolean for the 'enabled' key of the 
> 'FreeBSD' repo,  the value has been correctly converted, please
> consider fixing
> pkg-static: unable to open vulnxml file, try running 'pkg audit -F'
> first
> 
> Fixed 1st and 3rd. What it is supposed to do with 2nd one?
> 

should be 'enabled: yes' instead 'enabled: "yes"'

> Then, trying to update some ports:
> 
> portmaster ruby19-gems-1.8.25 gnuchess-6.1.0 libssh-0.5.2_1 
> libunibreak-1.0,1 libxml2-2.8.0_2 nmap-6.40 pciids-20131119
> 
> """
> ===>>> Working on:
>   ruby19-gems-1.8.25
>   gnuchess-6.1.0
>   libssh-0.5.2_1
>   libunibreak-1.0,1
>   libxml2-2.8.0_2
>   nmap-6.40
>   pciids-20131119
> 
> ===>>> Gathering distinfo list for installed ports
> 
>   ===>>> No ORIGIN in /var/db/pkg/ruby19-gems-1.8.25/+CONTENTS
> 
> 
> ===>>> ruby19-gems-1.8.25 1/7
>   ===>>> No ORIGIN in /var/db/pkg/ruby19-gems-1.8.25/+CONTENTS
> 
> 
> ===>>> Cannot continue
> ===>>> Aborting update
> 
> ===>>> Update for ruby19-gems-1.8.25 failed
> ===>>> Aborting update
> 
> ===>>> Killing background jobs
> Terminated
> ===>>> Exiting
> """
> 
> Got this "No ORIGIN"  messages for every port that I try to update.
> Is this known issue? How to handle that?
> 



-- 
wbr, tiger
___
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: something messed up with latest pkg update?

[Johan Hendriks]

Ruslan Makhmatkhanov schreef:

portsnap fetch update
pkg version -vl "<"
portmaster pkg-1.1.4_10

Got some warnings:
pkg-static: PACKAGESITE in pkg.conf is deprecated. Please create a 
repository configuration file
pkg-static: Warning: expecting a boolean for the 'enabled' key of the 
'FreeBSD' repo,  the value has been correctly converted, please 
consider fixing

pkg-static: unable to open vulnxml file, try running 'pkg audit -F' first

Fixed 1st and 3rd. What it is supposed to do with 2nd one?

Then, trying to update some ports:

portmaster ruby19-gems-1.8.25 gnuchess-6.1.0 libssh-0.5.2_1 
libunibreak-1.0,1 libxml2-2.8.0_2 nmap-6.40 pciids-20131119


"""
===>>> Working on:
ruby19-gems-1.8.25
gnuchess-6.1.0
libssh-0.5.2_1
libunibreak-1.0,1
libxml2-2.8.0_2
nmap-6.40
pciids-20131119

===>>> Gathering distinfo list for installed ports

===>>> No ORIGIN in /var/db/pkg/ruby19-gems-1.8.25/+CONTENTS


===>>> ruby19-gems-1.8.25 1/7
===>>> No ORIGIN in /var/db/pkg/ruby19-gems-1.8.25/+CONTENTS


===>>> Cannot continue
===>>> Aborting update

===>>> Update for ruby19-gems-1.8.25 failed
===>>> Aborting update

===>>> Killing background jobs
Terminated
===>>> Exiting
"""

Got this "No ORIGIN"  messages for every port that I try to update. Is 
this known issue? How to handle that?



The second one in my case was the line  enabled in /etc/pkg/FreeBSD.conf

FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest";,
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: "yes"
}

I had to change enabled: "yes"  to enbled: yes
Remove the " .

I can not help you with the rest of the errors.. Sorry

regards
Johan
___
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: something messed up with latest pkg update?

[Ruslan Makhmatkhanov]

Johan Hendriks wrote on 27.11.2013 14:00:

Got this "No ORIGIN"  messages for every port that I try to update. Is
this known issue? How to handle that?


The second one in my case was the line  enabled in /etc/pkg/FreeBSD.conf

FreeBSD: {
   url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest";,
   mirror_type: "srv",
   signature_type: "fingerprints",
   fingerprints: "/usr/share/keys/pkg",
   enabled: "yes"
}

I had to change enabled: "yes"  to enbled: yes
Remove the " .


Thank you, this worked to me.



I can not help you with the rest of the errors.. Sorry

regards
Johan


The rest of the problems were solved by copying 
/usr/local/etc/pkg.conf.sample to /usr/local/etc/pkg.conf


--
Regards,
Ruslan

T.O.S. Of Reality
___
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: install tcpdump 4.5.1 and libpcap 1.5.1 to filter in/out trafic

[Jason Hellenthal]

Never thought if catch myself saying this butt . . . 

Push it in please!

> On Nov 27, 2013, at 4:13, Rodrigo Osorio  wrote:
> 
> Hi all,
> 
> In order to take advantage of the new '-P' switch in
> tcpdump to filter in/out trafic from an interface, I
> need to move from tcpdump 4.4.0 to 4.5.1.
> 
> http://www.tcpdump.org/tcpdump_man.html
> 
> I did a set of minimal patches to upgrade tcpdump and
> its companion libpcap in ports to the latest versions.
> 
> In our tests (FreeBSD-i386-9.1-RELEASE and i386-10.0-BETA1)
> tcpdump 4.5.1 works fine and capture the desired trafic.
> 
> I didn't perform any test to check if the deinstall/package
> works, this will come with a future PR.
> 
> regards
> -rodrigo
> 
> 
> http://files.bebik.net/patches/tcpdump-4.5.1/tcpdump-patch
> http://files.bebik.net/patches/tcpdump-4.5.1/pcap-patch
> 
> ___
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


smime.p7s
Description: S/MIME cryptographic signature

Re: install tcpdump 4.5.1 and libpcap 1.5.1 to filter in/out trafic

[Rodrigo Osorio]

As soon as I test the port rigorously.
- rodrigo


On 27/11/13 05:10 -0500, Jason Hellenthal wrote:
> Never thought if catch myself saying this butt . . . 
> 
> Push it in please!
> 
> > On Nov 27, 2013, at 4:13, Rodrigo Osorio  wrote:
> > 
> > Hi all,
> > 
> > In order to take advantage of the new '-P' switch in
> > tcpdump to filter in/out trafic from an interface, I
> > need to move from tcpdump 4.4.0 to 4.5.1.
> > 
> > http://www.tcpdump.org/tcpdump_man.html
> > 
> > I did a set of minimal patches to upgrade tcpdump and
> > its companion libpcap in ports to the latest versions.
> > 
> > In our tests (FreeBSD-i386-9.1-RELEASE and i386-10.0-BETA1)
> > tcpdump 4.5.1 works fine and capture the desired trafic.
> > 
> > I didn't perform any test to check if the deinstall/package
> > works, this will come with a future PR.
> > 
> > regards
> > -rodrigo
> > 
> > 
> > http://files.bebik.net/patches/tcpdump-4.5.1/tcpdump-patch
> > http://files.bebik.net/patches/tcpdump-4.5.1/pcap-patch
> > 
> > ___
> > freebsd-...@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-net
> > To unsubscribe, send any mail to "freebsd-net-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"

Please check in the new port for Bitmessage

[Yuri]

This is a new near-instant messenger replacing traditional mail and IM 
clients. It allows to deeply encrypt the messages, therefore avoiding 
message snooping.


http://www.freebsd.org/cgi/query-pr.cgi?pr=184322
http://en.wikipedia.org/wiki/Bitmessage

Thank you,
Yuri

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

Re: FreeBSD Port: py27-pytz-2013.8,1

[Helmut Schneider]

Hi,

From: "Nicola Vitale" 

# cat /etc/make.conf
# easy_install-2.7 --version
# (cd /usr/ports/devel/py-boto && make -n)


[helmut@BSDHelmut ~]$ cat /etc/make.conf
WITHOUT_X11=YES

APACHE_PORT=www/apache22

amavisd-new_SET+=BDB SNMP POF RAR UNRAR UNARJ NOMARCH UNZOO TNEF
apache22_SET+=AUTHNZ_LDAP LDAP PROXY PROXY_AJP PROXY_BALANCER PROXY_CONNECT 
PROXY_FTP PROXY_HTTP

apr_SET+=LDAP
dcc-dccd_UNSET+=SENDMAIL
fping_SET+=IPV6
nagios-plugins_SET+=LDAP MYSQL NETSNMP
net-snmp_SET+=MFD_REWRITES
p5-Mail-SpamAssassin_SET+=DCC DKIM RAZOR SPF_QUERY
p5-Mail-SpamAssassin_UNSET+=SSL
pear-Mail_SET+=PEAR_NET_SMTP
perl_SET+=THREADS
php5_SET+=APACHE SUHOSIN
php54_SET+=APACHE SUHOSIN
postfix_SET+=PCRE SASL2 TLS
scponly_SET+=SCPONLY_CHROOT SCPONLY_SCP SCPONLY_SFTP_LOGGING SCPONLY_WINSCP
sudo_SET+=LDAP
squid31_SET+=SQUID_LDAP_AUTH SQUID_SSL SQUID_REFERER_LOG SQUID_USERAGENT_LOG 
SQUID_LARGEFILE

squid32_SET+=AUTH_KERB AUTH_LDAP LARGEFILE SNMP SSL
vsftpd_SET=+=RC_NG
[helmut@BSDHelmut ~]$ easy_install-2.7 --version
usage: easy_install-2.7 [options] requirement_or_url ...
  or: easy_install-2.7 --help

error: option --version not recognized
[helmut@BSDHelmut ~]$ (cd /usr/ports/devel/py-boto && make -n)
if [ -e /usr/ports/devel/py-boto/work/.build_done.boto._usr_local ]; then 
true;  else  cd /usr/ports/devel/py-boto && make 
/usr/ports/devel/py-boto/work/.build_done.boto._usr_local;  fi
[helmut@BSDHelmut ~]$ cd /usr/ports/devel/py-boto && sudo make deinstall 
install

===>  Deinstalling for devel/py-boto
===>   Deinstalling py27-boto-2.14.0
pkg_delete: package 'py27-boto-2.14.0' is required by these other packages
and may not be deinstalled (but I'll delete it anyway):
duplicity-0.6.22_1
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/__init__.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/ec2/connection.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/ec2/connection.pyo' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/exception.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/glacier/job.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/gs/resumable_upload_handler.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/jsonresponse.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/mturk/question.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/mws/response.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/provider.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/s3/website.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/sdb/db/manager/sdbmanager.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/sdb/db/manager/sdbmanager.pyo' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/ses/connection.pyc' 
fails original MD5 checksum - deleted anyway.
pkg_delete: 
'/usr/local/lib/python2.7/site-packages/boto-2.14.0-py2.7.egg/boto/utils.pyc' 
fails original MD5 checksum - deleted anyway.

===>  Staging for py27-boto-2.16.0
===>   py27-boto-2.16.0 depends on file: /usr/local/bin/easy_install-2.7 - 
found

===>   py27-boto-2.16.0 depends on file: /usr/local/bin/python2.7 - found
===>   py27-boto-2.16.0 depends on executable: python - found
===>   py27-boto-2.16.0 depends on executable: python2 - found
===>   Generating temporary packing list
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
  or: setup.py --help [cmd1 cmd2 ...]
  or: setup.py --help-commands
  or: setup.py cmd --help

error: option --user not recognized
*** [do-install] Error code 1

Stop in /usr/ports/devel/py-boto.
[helmut@BSDHelmut /usr/ports/devel/py-boto]$


What options/command do you use to run portupgrade?


-a 



---
Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz 
ist aktiv.
http://www.avast.com

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

Need advice on porting an Erlang application (Zotonic CMS)

[Marc van Woerkom]

Note: I posted this first in the google group, but it seems a post there
won't reach the mailing list

Hello,

I am trying to port Zotonic, a CMS and web framework written in Erlang.

  https://github.com/mvw/freebsd-ports-www-zotonic


So far it is mainly used on Linux systems, where one unpacks a zip archive
with a release or clone the git repo of the project in some working
directory.

One then runs a GNU make in that directory which calls rebar, a build
system written in Erlang which strives to organize the application
according to the rules of the Erlang/OTP platform.

One ends up with that aforementioned working directory, populated by
scripts, resource data, Erlang sources and beam files (compiled Erlang).

The application is then managed (start/stop/status..) by using a control
script.


To make this work under FreeBSD, I need to find a healthy compromise
beetween the FreeBSD standards (as written down in the FreeBSD Porter's
Handbook and the hier(7) man page) and the directory layout assumed by
Erlang/OTP and rebar, modulo some differences between the Linux and FreeBSD
operating systems.

The present state of the port does well with the fetch, extract, patch and
make targets. I am now grappling with the stage and install targets.


It is possible to run Zotonic from the www/zotonic/work directory, because
that fits the directory layout assumptions of the original rebar based
system, which does everything (configure/build/run) in the unpack work
directory.

I now plan to pick up all relevant files and sort them into the directories
according to hier(7) and then make things run there, which is likely to
need some patches, because some sub directory trees are moved relatively to
the the unpack work directory.

This approach seems to lead to a large Makefile:


https://github.com/mvw/freebsd-ports-www-zotonic/blob/master/zotonic/Makefile

I end up manually mapping the directory tree into NSTALL_DATA,
INSTALL_SCRIPT,
INSTALL_PROGRAM statements in the Makefile.
I am tempted to write a helper script for this, as this involves a large
set of files. It will also result in a long pkg-plist.

This is ugly work and with the next zotonic release, I can do it all over
again.

Do I need to go this road, or do you folks know a better approach?

For example I was tempted to simply copy the stuff from work/zotonic to
usr/local/lib/erlang/lib/
zotonic-x.y during the make install target and then start the rebar stuff
in the post-install phase, which would lead to Erlang compilations after
the make phase (bah!), but would probably make my life easier. But doing
this with a plan ${CP} would not fix the messy permission bits and
ownerships from the original zip archive.

Glad for any comment,
Marc
___
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: Need advice on porting an Erlang application (Zotonic CMS)

[Matthew Seaman]

On 11/27/13 14:17, Marc van Woerkom wrote:
> To make this work under FreeBSD, I need to find a healthy compromise
> beetween the FreeBSD standards (as written down in the FreeBSD Porter's
> Handbook and the hier(7) man page) and the directory layout assumed by
> Erlang/OTP and rebar, modulo some differences between the Linux and FreeBSD
> operating systems.

Take a look at net-im/ejabberd which is another erlang application in
the ports.  That installs most of the .beam and other working files
under /usr/local/lib/erlang/lib/ -- AFAIK, the layout under there is
pretty much standard for erlang apps.

Cheers,

Matthew




signature.asc
Description: OpenPGP digital signature

Re: lang/gcc not build

[Alexander Panyushkin]

Thanks.

It works


.if ${.CURDIR:N*/ports/lang/gcc*} == ""
CFLAGS= -O2 -march=athlon64-sse3 -mtune=athlon64-sse3 -pipe -Wformat
CPPFLAGS+= -D_FORTIFY_SOURCE=2
CC=gcc46
CXX=g++46
CPP=cpp46
.endif




On 26.11.2013 23:56, Dimitry Andric wrote:

On 26 Nov 2013, at 22:43, Alexander Panyushkin  wrote:
...

configure:4209: checking for C compiler default output file name
configure:4231: gcc46 -Oz -march=athlon64-sse3 -mtune=athlon64-sse3 -pipe 
-Qunused-arguments -Qunused-parameter -Wformat -Wformat-security -O2 
-march=athlon64-sse3 -mtune=athlon64-sse3 -pipe -Wformat -I/usr/local/include 
-Wl,-rpath=/usr/local/lib/gcc46 -fno-strict-aliasing -D_FORTIFY_SOURCE=2 
-D_FORTIFY_SOURCE=2 -Wl,-rpath=/usr/local/lib/gcc46 conftest.c  >&5
gcc46: error: unrecognized option '-Qunused-arguments'
gcc46: error: unrecognized option '-Qunused-parameter'
configure:4235: $? = 1

Apparently the COMPILER_TYPE logic in bsd.compiler.mk does not detect
you are using gcc, most likely because you are using USE_GCC= in
make.conf.  (This setting should normally be used in port Makefiles, not
in make.conf, AFAIK.)

Try one of the following:
* Add COMPILER_TYPE=gcc in make.conf (in the part where you put USE_GCC)
* Alternatively, remove USE_GCC and just set CC=gcc46, CXX=g++46 and
   CPP=cpp46.

-Dimitry




--
Alexander

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

Need advice on porting an Erlang application (Zotonic CMS)

[Marc van Woerkom]

Hi Matthew,

thanks for the advice.

I already looked into some of the other erlang ports, to see how the
other guys did it and got some insight, probably not enough. :-)

ejabberd seems to be an easier case, but it does interesting things in
its pkg-plist file, which I need to look at and understand.

So far I think I end up with something similar to database/riak.

Regards,
Marc



On 11/27/13 14:17, Marc van Woerkom wrote:
>* To make this work under FreeBSD, I need to find a healthy compromise
*>* beetween the FreeBSD standards (as written down in the FreeBSD Porter's
*>* Handbook and the hier(7) man page) and the directory layout assumed by
*>* Erlang/OTP and rebar, modulo some differences between the Linux and FreeBSD
*>* operating systems.
*
Take a look at net-im/ejabberd which is another erlang application in
the ports.  That installs most of the .beam and other working files
under /usr/local/lib/erlang/lib/ -- AFAIK, the layout under there is
pretty much standard for erlang apps.

Cheers,

Matthew
___
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: warning

[Tom Evans]

On Wed, Nov 27, 2013 at 4:55 PM, Ajtim  wrote:
> OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov  3 19:43:01 UTC 2013 
> r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
>
> When I boot a computer I got one warning:
>
> /etc/rc: WARNING: $tcsd_enable is not set properly


This is part of a port, security/trousers. Reinstall it?

Cheers

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

Re: FreeBSD Port: py27-pytz-2013.8,1

[Michael Gmelin]

On Wed, 27 Nov 2013 13:43:42 +0100
"Helmut Schneider"  wrote:

Does it work when NO_STAGE=yes?
(e.g. NO_STAGE=yes portupgrade packagename)


-- 
Michael Gmelin
___
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"

AW: FreeBSD Port: py27-pytz-2013.8,1

[jumpe...@gmx.de]

Yes, works.

- Reply message -
Von: "Michael Gmelin" 
An: "Helmut Schneider" 
Cc: "Nicola Vitale" , "freebsd-ports" 

Betreff: FreeBSD Port: py27-pytz-2013.8,1
Datum: Mi., Nov. 27, 2013 18:19


On Wed, 27 Nov 2013 13:43:42 +0100
"Helmut Schneider"  wrote:

Does it work when NO_STAGE=yes?
(e.g. NO_STAGE=yes portupgrade packagename)


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

Re: portmaster refuses to use pkgng with local packages

[Axel Rau]

Am 26.11.2013 um 23:05 schrieb olli hauer :

> - upgrade pkg on your Pd box to 1.2_1
Indeed, it works now!

Thanks a lot, Axel
---
PGP-Key:29E99DD6  ☀ +49 151 2300 9283  ☀ computing @ chaos claudius

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

Stageifying various textproc/docbook* ports

[Kimmo Paasiala]

I made a quick stage conversion for textproc/docbook-sk because of a report on 
the FreeBSD forums that the port failed to install because the xml catalog 
entries were being added twice. The patch if you want to see it is on paste bin:

http://pastebin.com/24QGWh8x

Is there anyone else working on converting these docbook ports to stage? If not 
I would like to try my hand with a few more of them because they look like to 
be quite easy to convert.

One thing I’d like to ask is the handling of the ${PREFIX}share/xml and 
${PREFIX}share/xml directories. Which port should own these directories and 
should the docbook-ports try to delete these directories like the docbook-sk 
port now tries to do? In my patch I replaced the '@unexec /bin/rmdir’s with 
just '@dirrmtry share/xml/docbook'

-Kimmo


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Stageifying various textproc/docbook* ports

[Kimmo Paasiala]

On 27.11.2013, at 21.16, Kimmo Paasiala  wrote:

> 
> One thing I’d like to ask is the handling of the ${PREFIX}share/xml and 
> ${PREFIX}share/xml directories.


${PREFIX}/share/xml and ${PREFIX}/share/xml/docbook directories *

 


signature.asc
Description: Message signed with OpenPGP using GPGMail

/usr/ports/sysutils/syslinux up to 6.02

[??????????????????]

/usr/ports/sysutils/syslinux up to 6.02
___
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: warning

[Cb]

> On Nov 27, 2013, at 11:07 AM, Tom Evans  wrote:
> 
>> On Wed, Nov 27, 2013 at 4:55 PM, Ajtim  wrote:
>> OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov  3 19:43:01 UTC 2013 
>> r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
>> 
>> When I boot a computer I got one warning:
>> 
>> /etc/rc: WARNING: $tcsd_enable is not set properly
> 
> 
> This is part of a port, security/trousers. Reinstall it?
> 
> Cheers
> 
> Tom

There are more than a few ports in the tree right now that are causing warnings 
just like that one to be emitted. (I didn't check security/trousers to see if 
what I describe below is actually it's crime. It is likely that this is 
applicable in your particular case with trousers.)

It gets emitted by rc(.subr) when a port has an rc.d file (that is, one that 
leverages rc.subr,) but it fails to supply it's own default for that variable 
(which should almost invariably be a "NO").

Somewhere in the rc.d file for foo, before calling load_rc_config, is supposed 
to be a line similar to this:

: ${foo_enable:="NO"}

At least, that's how I've been doing it and how I understood things. Please 
correct me if there's a more orthodox way.

samba_enable and dbus_enable warnings pop into mind, among others, (though I'm 
speaking off the top of my head, I've not verified those currenty, and they may 
have been fixed in the last couple weeks).

These warning emissions should ideally all be cleaned up throughout the tree. I 
guess porters more typically test their ports enabled and forget to notice that 
things are getting a little noisier when they are being left dormant.

There is a reason that rc.subr complains about an undefined master on/off 
switch for a port instead of quietly assuming "NO". In theory, it is up to the 
port-roller since there is an atypical possibility that by just having a 
package installed, it might indeed be a good idea to default to its complete or 
partial activation during startup _without_ the end-user explicitly enabling 
it. Someone pipe up if their port exhibits such behavior and they feel it 
justified because I'd like to know, not to attack the choice, rather to expand 
my view. I can think of no such instance, but I understand the theory behind 
the liberty and thus why rc.subr wants to enforce the responsibility of 
defining the default.

When wearing my user hat, I've typically ignored such errors to no ill effect, 
as the lack of a variable obviously implies checkyesno will exit 1 (i.e. return 
"NO"). I, for one, have a lot more ports installed than are enabled on most of 
my systems because developers like when things are just ready to go for them. I 
also subscribe to the philosophy that one ought to be able to install a 
thousand packages and have nothing else magical happen until one implicitly 
enables what they want to use. (Yet I appreciate, rather than fear, a little 
magic where applicable. Muahaha! Thus why I'm open to hearing anyone's thoughts 
if they default a port of theirs to do anything at all during startup without 
an explicit enable, even though my imagination currently offers me no such 
picture.)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: py27-pytz-2013.8,1

[Helmut Schneider]

From: Michael Gmelin


Does it work when NO_STAGE=yes?
(e.g. NO_STAGE=yes portupgrade packagename)


Yes, builds fine. What does that mean? Do I need to change something or does 
the port?
I'm asking because I raised ports/184293 and would like to update it 
accordingly.


Thanks, Helmut 


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

Re: FreeBSD Port: py27-pytz-2013.8,1

[Michael Gmelin]

On Wed, 27 Nov 2013 22:22:12 +0100
"Helmut Schneider"  wrote:

> From: Michael Gmelin
> 
> > Does it work when NO_STAGE=yes?
> > (e.g. NO_STAGE=yes portupgrade packagename)
> 
> Yes, builds fine. What does that mean? Do I need to change something
> or does the port?
> I'm asking because I raised ports/184293 and would like to update it 
> accordingly.
> 
> Thanks, Helmut 
> 

I had a similar issue on a 9.1 system using portmaster (NO_STAGE fixed
it) last week, while portupgrade on a freshly installed system had no
issues (no matter which packaging system pkgng/oldschool packages etc.).

I can only speculate about the exact reasons, maybe it's related to the
recent switch from py-distribute to py-setuptools in combination with
staging support or only to upgrading from a specific version. I
couldn't reproduce the problem, since I didn't keep the original
package. Maybe it's not worthwhile chasing this one.

In regards to your PR: I don't think this is related to py-boto
specifically, but more to recent ports infrastructure changes, so I
would suggest to close the PR and either open another one for the ports
infrastructure (if you have enough details), keep trying to get
attention on ports@ or simply forget about it ;)

-- 
Michael Gmelin
___
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: Why can't lang/gcc4X compilers build kernel modules?

[Gerald Pfeifer]

On Fri, 10 May 2013, Dimitry Andric wrote:
> On May 10, 2013, at 18:59, Mikhail T.  wrote:
>> Would it be too much work to extend the port-installed compilers the 
>> same way gcc-4.2.1 in the base is extended? May be not for gcc4[89], 
>> which are complete rewrites, but for 4.[4-7]? If not too difficult, 
>> should it be done?
> 
> In my opinion, this is a fruitless direction.  Neither upstream gcc, nor
> upstream clang will ever accept an option called "-fformat-extensions",
> which enables FreeBSD kernel-specific format extensions (which might
> also change in the future, so you do not really gain anything).
> 
> I think the best solution is to get rid of all non-standard printf
> format specifiers in the kernel, and use custom formatters for our
> specialized needs.  For replacing the %b specifier, for example, we
> could use NetBSD's snprintb() (see
> ).
> 
> Getting rid of non-standard extensions in general is really the way to
> go.  This would enable compiling with any standards-compliant compiler,
> even commercial ones.

Amen.

Gerald
___
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 Port: nss-pam-ldapd-sasl-0.8.13_1

[Scott Loga]

Greetings,

Today, I went to www.freebsd.org to search for the "nss-pam-ldapd" port, but 
when I performed a search for "nss-pam" 
(http://www.freebsd.org/ports/index.html) it only returns the 
nss-pam-ldapd-sasl port and not the nss-pam-ldapd port.  I'm not sure why a 
search only returns the port with the sasl options, but I thought you might 
want to know.  By the way, when I performed a search on www.freshports.org for 
"nss-pam", both ports were returned.  I also attempted the search with multiple 
browsers with the same result.

Thanks for your time.

Scott Loga



___
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: Fwd: [thunderbird-24.1.0] FreeBSD 10-i386 jail at 11-amd64 host: Error while running startup cache precompilation

[Cy Schubert]

Cy Schubert writes:
> In message <5272af33.7030...@smeets.im>, Florian Smeets writes:
> > This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> > --LjCOVwNOW3aPxiaJSC0KaksgOOBQirtv3
> > Content-Type: text/plain; charset=UTF-8
> > Content-Transfer-Encoding: quoted-printable
> > 
> > On 31/10/13 16:13, Boris Samorodov wrote:
> > >=20
> > > Hi All,
> > >=20
> > > I get the following error using 10-i386 jail at 11-amd64 host:
> > > -
> > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > hase: install>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > =3D=3D=3D>  Installing for thunderbird-24.1.0
> > > ...
> > > Executing
> > > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> > eebsd10.0/mozilla/dist/bin/xpcshell
> > > -g
> > > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> > eebsd10.0/mozilla/dist/bin/
> > > -a
> > > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> > eebsd10.0/mozilla/dist/bin/
> > > -f
> > > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/moz=
> > apps/installer/precompile_cache.js
> > > -e precompile_startupcache("resource://gre/");
> > > Traceback (most recent call last):
> > >   File
> > > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> > zapps/installer/packager.py",
> > > line 375, in 
> > > main()
> > >   File
> > > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> > zapps/installer/packager.py",
> > > line 367, in main
> > > args.source, gre_path, base)
> > >   File
> > > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> > zapps/installer/packager.py",
> > > line 148, in precompile_cache
> > > errors.fatal('Error while running startup cache precompilation')
> > >   File
> > > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/python/moz=
> > build/mozpack/errors.py",
> > > line 101, in fatal
> > > self._handle(self.FATAL, msg)
> > >   File
> > > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/python/moz=
> > build/mozpack/errors.py",
> > > line 96, in _handle
> > > raise ErrorMessage(msg)
> > > mozpack.errors.ErrorMessage: Error: Error while running startup cache
> > > precompilation
> > > gmake[3]: *** [stage-package] Error 1
> > > -
> > >=20
> > > And there is a line at /var/log/messages:
> > > -
> > > Oct 31 17:54:33 bb052 kernel: pid 20298 (xpcshell), uid 0: exited on
> > > signal 11 (core dumped)
> > > -
> > >=20
> > > Full log is here:
> > > http://gw.wart.ru/bulk/10-i386-default/2013-10-31_13h42m43s/logs/errors=
> > /thunderbird-24.1.0.log
> > >=20
> > 
> > Yeah, I'm also seeing this, I missed that 2 builds failed, seamonkey is
> > also affected on 10.0/i386. No Idea what it is, yet. I hope to have some
> > time during the weekend to look at it.
> 
> I'm seeing the same problem on my i386 systems (except for one). It 
> installs nicely on amd64.
> 
> On my one i386 system that thunderbird and seamonkey install, the system is 
> a FreeBSD-11 system using ports built on a 9.X system a year ago and 
> upgraded piecemeal (not recommended for the faint of heart). I'm betting 
> there's an upgraded port somewhere that may contribute to this. (This 
> particular

I've discovered a circumvention.

make CC=cc CXX=c++ CPP=cpp install


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  http://www.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"

Adding CFLAGS+= which will ignore -Woverload-virtual

[Joe Nosay]

This is still on building traverso with the following error and warning:

In file included from
/usr/home/raspycat/traverso/work/traverso-0.49.2/src/engine/AudioDevice.cpp:27:
/usr/home/raspycat/traverso/work/traverso-0.49.2/src/engine/AlsaDriver.h:62:6:
warning: 'AlsaDriver::setup' hides overloaded virtual function
[-Woverloaded-virtual]
int setup(bool capture=true, bool playback=true, const
QString& pcmName="hw:0", const QString& dither="None");
^
/usr/home/raspycat/traverso/work/traverso-0.49.2/src/engine/Driver.h:49:14:
note: hidden overloaded virtual function 'Driver::setup' declared
here: different number of parameters (3 vs 4)
virtual int setup(bool capture=true, bool playback=true, const
QString& cardDevice="none");
^
In file included from
/usr/home/raspycat/traverso/work/traverso-0.49.2/src/engine/AudioDevice.cpp:52:
/usr/home/raspycat/traverso/work/traverso-0.49.2/src/common/Tsar.h:66:9:
error: field has incomplete type 'void *[]'
void*   _a[];
^
1 warning and 1 error generated.
*** Error code 1

A suggestion comes from
http://stackoverflow.com/questions/18515183/c-overloaded-virtual-function-warning-by-clang;
yet, my question is, "Is the pragma referred to added to the header
and
other files, or do I add a a flag which ignore the error?"
___
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"

Replacing files forbidden because that would break *CVS* ?

[Matthew Seaman]

Prompted by bsam, I'm attempting to re-connect the www/rt42 port with
its history, buy 'svn rm'-ing the current www/rt42 contents, 'svn cp
www/rt40 www/rt42' and then reapply the changes to the files.

Except I get this:

lucid-nonsense:~...ports/www/rt42:% /usr/ports/Tools/scripts/psvn commit
===> Do not replace files as this will break the CVS exporter: "."

Uh... do we still care about exporting to CVS?  I though CVS was long gone.

Any ideas on how I can achieve my aim of fixing the history for rt42
gratefully received.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature