Re: Passing target to source Makefile

2016-07-21 Thread Russell Haley 
On Thu, Jul 21, 2016 at 2:55 AM, olli hauer  wrote:
> On 2016-07-21 08:03, Russell Haley wrote:
>> Hi there,
>>
>> I've been able to hack up the Makefile for an update of lua53 but the
>> one thing still missing is the ability to pass a target for the source
>> Makefile (i.e. lua's Makefile, not the ports Makefile). I need to pass
>> in "freebsd" as per the build instructions for lua.
>>
>> Also, I can't seem to get make makeplist to work, but I think that's
>> because the lua makefile is defaulting to install the files (due to
>> the lack of target) and overriding the makeplist output?
>>
>> Thanks,
>>
>> Russell
>
> Hi Russel,
>
> it is not clear if you try to hack the lag/lua53 port or a different one.
>
> There are perhaps two ways, during configure or as make arg
> CONFIGURE_ARGS+= target=freebsd
> or
> MAKE_ARGS+= target=freebsd

Thanks again for this suggestion but I can't for the life of me make
it work. I would normally use ports through svn and try to provide a
patch but I have limited time and tools currently (on vacation) so the
best I can do is provide an archive of my updated port files:

https://drive.google.com/open?id=0B1RmC6WWKtYITWplVElaR0Y0QU0

For a quick look, I have posted the raw Makefile in pastebin (yes,
it's a mess but it's a work in progress):

http://pastebin.com/9KhvEL4R

If I can't make the above variables work then I'll perhaps fall back
to Carstens suggestion, but my preference is for the standard ports
variables.

Again, all help is appreciated.

Thanks,

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

Anyone interested in devel/bitkeeper?

2016-07-21 Thread Pedro Giffuni 

Hello;

Upstream has cleaned up basic parts of bitkeeper for packaging so I 
started a port:


https://people.freebsd.org/~pfg/ports/bitkeeper.tgz

It basically works, I think, but is not very clean. It installs in
/usr/local/bitkeeper (I said it's not very clean) and still needs
some symlinking that I find too boring to spend time on.

Someone feel free to finish and claim all the glory :).

Pedro.
___
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: Passing target to source Makefile

2016-07-21 Thread Russell Haley 
On Thu, Jul 21, 2016 at 2:55 AM, olli hauer  wrote:
> On 2016-07-21 08:03, Russell Haley wrote:
>> Hi there,
>>
>> I've been able to hack up the Makefile for an update of lua53 but the
>> one thing still missing is the ability to pass a target for the source
>> Makefile (i.e. lua's Makefile, not the ports Makefile). I need to pass
>> in "freebsd" as per the build instructions for lua.
>>
>> Also, I can't seem to get make makeplist to work, but I think that's
>> because the lua makefile is defaulting to install the files (due to
>> the lack of target) and overriding the makeplist output?
>>
>> Thanks,
>>
>> Russell
>
> Hi Russel,
>
> it is not clear if you try to hack the lag/lua53 port or a different one.
>
> There are perhaps two ways, during configure or as make arg
> CONFIGURE_ARGS+= target=freebsd
> or
> MAKE_ARGS+= target=freebsd
>
> Perhaps you can give the list some more information?
 Yes, of course.

TLDR; I think the Lua port needs some love so I'm trying to update it
to the most recent version.

I am trying to develop a cross platform Lua application that will run
in both FreeBSD and Debian. I have had to abandon the FreeBSD lua53
port for the following reasons:

1) It does not use the recommended "freebsd" target. While the port
overlays many of the same options, the system doesn't seem to respect
the targets and also performs the installation without specifically
calling the "install" target. This is from memory and *could* be
incorrect, but this is my anecdotal experience. In the end, we will
lose the benefit of any changes made upstream (more on that in a bit).
2) There seems to be lost of "stuff" going on in the port file that
seems unnecessary as the Lua Makefile takes care of most of the
extras.
3) By forcing all Lua installation to use luaXX naming conventions, it
forces the user to have to create work arounds or links to get the
standard interpreter to work by calling "lua" (which is the expected
use case in my opinion). The current supported version of Lua is 5.3.
While I can see the need to install past versions using explicit
naming, it is my opinion that the current version should be installed
as Lua, not luaXX.
4) The current Makefile applies -fPIC to some of the platforms, but
not armv6. I require that switch for all platforms and it seems to
work fine on my ARM board (Solid-Run Hummingboard, iMX6/cortex A9).
While it's an easy patch, it adds to the list of reasons to build Lua
myself.

So with that in mind, I have been building and running Lua from git
with no patches. While I can continue in this manner, I thought I
would try to give back to the community if there is interest. Lua is
now on version 5.3.3. I have been able to hack up the ports Makefile
to run "successfully" but it still only calls the default target that
assumes an installation. So, my goals in terms of a ports upgrade are
as follows:

- Update to the latest Lua revision
- Get ports to call the correct targets (the makeargs above looks promising)
- Remove the Lua53 naming convention. Once Lua move to a new major
version, this can be re-implemented and the new Lua version can become
the standard interpreter.
- Add -fPIC to all platforms in FreeBSD
- Use clang and bmake instead of forcing gcc/gmake.

The last item I think is the most difficult as it will require others
to test. However, I have successfully built and run Lua 5.3.2 (testing
5.3.3) using clang and bmake (as well as other libraries such as
luasys and luaxml).

All input is welcome. Again, if this is not where the community wants
to go, it's no big deal.

Please also note that I have made an upstream request to the Lua
community to consider applying a patch to the freebsd target in their
source/Makefile. The patch can be found here:
http://pastebin.com/cUCtWb1w. I don't expect this to happen quickly
however.


Most Sincerely,

Russell
___
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: committer for multimedia/zoneminder

2016-07-21 Thread abi 

Hello,

how it's going ? :)  I fixed qa warnings, so I think it could be commited.

On 14.07.2016 10:57, Torsten Zuehlsdorff wrote:

Hello,


can anybody commit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210939 ?

It status was changed, but assignee is not, I suspect no one is aware
about this particular PR.


I will have a look at it.

Greetings,
Torsten
___
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"

Re: Maintaining mono/.net

2016-07-21 Thread Carsten Larsen 

Hi,

On 09-07-2016 kl. 13:10 Romain Tartière wrote:

Dear all,

I finally could manage to sync my local mess into some "shipable form"
and updated the bsd-sharp github repository with current WIP:

https://github.com/smortex/bsd-sharp

My main issue is devel/newtonsoft-json which fails to build.  I could
not manage to get more time to search for the root cause of the build
failure during the last couple of weeks :-(  If someone has insights or
a workaround, thank you for sharing !


I dont know know if any others are looking at his issue ? fyi. I could 
build lang/mono from the repository without any changes. I will take a 
look devel/newtonsoft-json and see if I can fix it.




Regards,
Romain




Carsten
___
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: Passing target to source Makefile

2016-07-21 Thread Carsten Larsen 

Hi Russell,

> I've been able to hack up the Makefile for an update of lua53 but the

one thing still missing is the ability to pass a target for the source
Makefile (i.e. lua's Makefile, not the ports Makefile). I need to pass
in "freebsd" as per the build instructions for lua.



Assuming gnu make is used, do this:

do-build:
${GMAKE} -C ${WRKSRC} TARGET=insert-here


Also, I can't seem to get make makeplist to work, but I think that's
because the lua makefile is defaulting to install the files (due to
the lack of target) and overriding the makeplist output?

Thanks,

Russell




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

python34 fails to install on stable/11

2016-07-21 Thread tech-lists 
Hi,

$ svnlite info
Path: .
Working Copy Root Path: /usr/ports
URL: https://svn0.eu.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn0.eu.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 418866
Node Kind: directory
Schedule: normal
Last Changed Author: matthew
Last Changed Rev: 418866
Last Changed Date: 2016-07-21 08:30:41 +0100 (Thu, 21 Jul 2016)

FreeBSD 11.0-BETA1 #0 r302999: Tue Jul 19 11:22:39 BST 2016

output of "make" from /usr/ports/lang/python3 :

running install_scripts
copying build/scripts-3.4/idle3.4 ->
/usr/ports/lang/python34/work/stage/usr/local/bin
copying build/scripts-3.4/pyvenv-3.4 ->
/usr/ports/lang/python34/work/stage/usr/local/bin
copying build/scripts-3.4/pydoc3.4 ->
/usr/ports/lang/python34/work/stage/usr/local/bin
copying build/scripts-3.4/2to3-3.4 ->
/usr/ports/lang/python34/work/stage/usr/local/bin
changing mode of
/usr/ports/lang/python34/work/stage/usr/local/bin/idle3.4 to 755
changing mode of
/usr/ports/lang/python34/work/stage/usr/local/bin/pyvenv-3.4 to 755
changing mode of
/usr/ports/lang/python34/work/stage/usr/local/bin/pydoc3.4 to 755
changing mode of
/usr/ports/lang/python34/work/stage/usr/local/bin/2to3-3.4 to 755
rm
/usr/ports/lang/python34/work/stage/usr/local/lib/python3.4/lib-dynload/_sysconfigdata.py
rm -r
/usr/ports/lang/python34/work/stage/usr/local/lib/python3.4/lib-dynload/__pycache__
install  -m 0644 ./Misc/python.man
/usr/ports/lang/python34/work/stage/usr/local/man/man1/python3.4.1
if test "xno" != "xno"  ; then  case no in  upgrade)
ensurepip="--altinstall --upgrade" ;;  install|*)
ensurepip="--altinstall" ;;  esac;
LD_LIBRARY_PATH=/usr/ports/lang/python34/work/Python-3.4.5 ./python -E
-m ensurepip  $ensurepip --root=/usr/ports/lang/python34/work/stage/ ;  fi
/bin/rm -f
/usr/ports/lang/python34/work/stage/usr/local/lib/libpython3.so
 # Upstream Issue: http://bugs.python.org/issue17975
for i in
/usr/ports/lang/python34/work/stage/usr/local/lib/python3.4/lib-dynload/*.so;
do  /usr/bin/strip $i; done
  # Strip shared extensions
> Compressing man pages (compress-man)
===>  Installing for python34-3.4.5
===>  Checking if python34 already installed
===>   Registering installation for python34-3.4.5 as automatic
pkg-static: Unable to access file
/usr/ports/lang/python34/work/stage/usr/local/lib/python3.4/lib-dynload/_lzma.so:
No such file or directory
*** Error code 74

Stop.
make[2]: stopped in /usr/ports/lang/python34
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/lang/python34
*** Error code 1

Stop.
make: stopped in /usr/ports/lang/python3

-- 
J.
___
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: Is there still broken lang/ruby23 ?

2016-07-21 Thread Hajimu UMEMOTO 
Hi,

> On Thu, 21 Jul 2016 12:39:14 +0200
> "Herbert J. Skuhra"  said:

herbert> Any update on this issue?

herbert> With this patch build works for me on FreeBSD 11.0-BETA1 amd64
herbert> (r303012).

Okay, I've just committed it as r418883.

Sincerely,

--
Hajimu UMEMOTO
u...@mahoroba.org  u...@freebsd.org
http://www.mahoroba.org/~ume/
___
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: stunnel fails to build

2016-07-21 Thread tech-lists 
On 21/07/2016 17:48, Walter Schwarzenfeld wrote:
> I think you should file a PR.

will do, thanks for your suggestion anyway

-- 
J.
___
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: stunnel fails to build

2016-07-21 Thread Walter Schwarzenfeld 

I think you should file a PR. The try with the Makefile was a "weak" one.
I think it is the same problem as appears in other ports with libressl.
e.g. (this patch is from 2014 and only an example )
"HAVE_RAND_EGD -.thing"
https://github.com/sabotage-linux/sabotage/commit/9b47cbbf3ce903dee042c45c8197db066e8e0053

I can't provide a patch, cause I can't test it.
___
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"

Is there a way to silence this warning? (Failed for virtualbox-ose...)

2016-07-21 Thread Alfred Perlstein 

Hey folks,

I've been getting a bunch of these warnings (see below).  Would it make 
sense to either disable the build or mute warnings between major OS 
revisions for this?


I believe this is due to structure size changes between 10 and 11.  I 
tested building on a 11.x host and it's fine.


Ideas?

I can just ignore the emails as well.



 Forwarded Message 
Subject: 	[package - 101i386-default][emulators/virtualbox-ose-lite] 
Failed for virtualbox-ose-lite-4.3.38_1 in build

Date:   Thu, 21 Jul 2016 06:15:57 GMT
From:   pkg-fall...@freebsd.org
To: alf...@freebsd.org
CC: pkg-fall...@freebsd.org



You are receiving this mail as a port that you maintain
is failing to build on the FreeBSD package build server.
Please investigate the failure and submit a PR to fix
build.

Maintainer: alf...@freebsd.org
Last committer: alf...@freebsd.org
Ident:  $FreeBSD: head/emulators/virtualbox-ose-lite/Makefile 418067 
2016-07-05 08:06:10Z alfred $
Log URL:
http://beefy5.nyi.freebsd.org/data/101i386-default/418859/logs/virtualbox-ose-lite-4.3.38_1.log
Build URL:  
http://beefy5.nyi.freebsd.org/build.html?mastername=101i386-default=418859
Log:

>> Building emulators/virtualbox-ose-lite
build started at Thu Jul 21 05:49:56 UTC 2016
port directory: /usr/ports/emulators/virtualbox-ose-lite
building for: FreeBSD 101i386-default-job-16 10.1-RELEASE-p36 FreeBSD 
10.1-RELEASE-p36 i386
maintained by: alf...@freebsd.org
Makefile ident:  $FreeBSD: head/emulators/virtualbox-ose-lite/Makefile 
418067 2016-07-05 08:06:10Z alfred $
Poudriere version: 3.1.14
Host OSVERSION: 1100116
Jail OSVERSION: 1001000

---Begin Environment---
SHELL=/bin/csh
UNAME_p=i386
UNAME_m=i386
UNAME_v=FreeBSD 10.1-RELEASE-p36
UNAME_r=10.1-RELEASE-p36
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
OPSYS=FreeBSD
ARCH=i386
LINUX_OSRELEASE=2.6.32
SAVED_TERM=
MASTERMNT=/usr/local/poudriere/data/.m/101i386-default/ref
UID=0
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
_JAVA_VERSION_LIST_REGEXP=1.6\|1.7\|1.8\|1.6+\|1.7+\|1.8+
POUDRIERE_BUILD_TYPE=bulk
PKGNAME=virtualbox-ose-lite-4.3.38_1
OSREL=10.1
_OSRELEASE=10.1-RELEASE-p36
PYTHONBASE=/usr/local
OLDPWD=/
_SMP_CPUS=24
PWD=/usr/local/poudriere/data/.m/101i386-default/ref/.p/pool
MASTERNAME=101i386-default
SCRIPTPREFIX=/usr/local/share/poudriere
_JAVA_VENDOR_LIST_REGEXP=openjdk\|oracle\|sun
USER=root
HOME=/root
POUDRIERE_VERSION=3.1.14
SCRIPTPATH=/usr/local/share/poudriere/bulk.sh
CONFIGURE_MAX_CMD_LEN=262144
LIBEXECPREFIX=/usr/local/libexec/poudriere
LOCALBASE=/usr/local
PACKAGE_BUILDING=yes
_JAVA_OS_LIST_REGEXP=native\|linux
OSVERSION=1001000
---End Environment---

---Begin OPTIONS List---
===> The following configuration options are available for 
virtualbox-ose-lite-4.3.38_1:
 DBUS=off: D-Bus IPC system support
 DEBUG=off: Debug symbols, additional logs and assertions
 GUESTADDITIONS=off: Build with Guest Additions
 MANUAL=off: Build with user manual
 NLS=off: Native Language Support
 PULSEAUDIO=off: PulseAudio sound server support
 PYTHON=off: Python bindings or support
 QT4=off: Build with QT4 Frontend
 R0LOGGING=off: Enable R0 logging
 UDPTUNNEL=on: Build with UDP tunnel support
 VDE=off: Build with VDE support
 VNC=on: Build with VNC support
 VPX=off: Use vpx for video capturing
 WEBSERVICE=off: Build Webservice
 X11=off: X11 (graphics) support
===> Use 'make config' to modify these settings
---End OPTIONS List---

--CONFIGURE_ARGS--
--disable-java --passive-mesa --with-gcc="cc" --with-g++="c++" --disable-dbus 
--disable-docs --disable-pulse --disable-python --disable-qt4 --enable-vnc --disable-libvpx 
--build-headless
--End CONFIGURE_ARGS--

--CONFIGURE_ENV--
PKG_CONFIG=pkgconf PYTHON="/usr/local/bin/python2.7" 
XDG_DATA_HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-lite/work  
XDG_CONFIG_HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-lite/work  
HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-lite/work TMPDIR="/tmp" SHELL=/bin/sh 
CONFIG_SHELL=/bin/sh
--End CONFIGURE_ENV--

--MAKE_ENV--
OPENSSLBASE=/usr OPENSSLDIR=/etc/ssl OPENSSLINC=/usr/include OPENSSLLIB=/usr/lib XDG_DATA_HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-lite/work  XDG_CONFIG_HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-lite/work  
HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-lite/work TMPDIR="/tmp" NO_PIE=yes WITHOUT_DEBUG_FILES=yes WITHOUT_KERNEL_SYMBOLS=yes SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local  LOCALBASE=/usr/local  LIBDIR="/usr/lib" 
 CC="cc" CFLAGS="-O2 -pipe  -DLIBICONV_PLUG -DNO_IDEA -fstack-protector -fno-strict-aliasing"  CPP="cpp" CPPFLAGS="-DLIBICONV_PLUG"  LDFLAGS="  -fstack-protector" LIBS=""  
CXX="c++" CXXFLAGS="-O2 -pipe -DLIBICONV_PLUG -DNO_IDEA -fstack-protector -fno-strict-aliasing  -DLIBICONV_PLUG"  MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install  -s -m 555"  
BSD_INSTALL_LIB="install  -s -m 444"  BSD_INSTALL_SCRIPT="install  -m 555"

Re: stunnel fails to build

2016-07-21 Thread tech-lists 
On 07/21/16 11:29, Dewayne Geraghty wrote:
> After reading about your issue, I updated all of my ports, via svnlite, and
> successfully built on yesterday's fresh FreeBSD 10.3 Stable for i386 using
> openssl.  Unfortunately on the amd64, which uses libressl, I receive:
> ===>  stunnel-5.35,1 may not be packaged: The stunnel license restricts
> distribution when linked to non-OpenSSL non-base SSL-libraries.  (A recent
> enhancement)
> 
> My customisations are:
> i386 uses make.conf entry:  ssl=openssl
> amd64 uses make.conf:  ssl=libressl
> This may be significant to your situation?
> 
> If there is a problem with the Makefile, please log a PR so everyone can
> benefit.  ;)

I dunno if there's a problem with the makefile or with the software as
suggested amendments had no effect. The "stunnel may not be packaged"
message is one related to distribution and is not a problem with
compilation per se.

thanks,

-- 
J.
___
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: stunnel fails to build

2016-07-21 Thread tech-lists 
On 07/21/16 11:09, Walter Schwarzenfeld wrote:
> Try:
> remove  --with-ssl="${OPENSSLBASE}"
> from the Makefile
> and add
> to USES= ssl

Unfortunately, this didn't work. Here's my amended Makefile:

# Created by: Martti Kuparinen 
# $FreeBSD: head/security/stunnel/Makefile 418695 2016-07-18 11:38:46Z zi $

PORTNAME=   stunnel
PORTVERSION=5.35
PORTEPOCH=  1
CATEGORIES= security
MASTER_SITES=   https://www.stunnel.org/downloads/%SUBDIR%/ \
https://www.stunnel.org/downloads/beta/ \
http://mirrors.zerg.biz/stunnel/%SUBDIR%/ \
http://mirrors.go-part.com/stunnel/%SUBDIR%/ \
http://ftp.nluug.nl/pub/networking/stunnel/%SUBDIR%/ \
ftp://ftp.nluug.nl/pub/networking/stunnel/%SUBDIR%/ \
http://ftp.nluug.nl/pub/networking/stunnel/%SUBDIR%/ \
ftp://ftp.surfnet.nl/pub/networking/stunnel/%SUBDIR%/ \
http://ftp.surfnet.nl/pub/networking/stunnel/%SUBDIR%/ \
ftp://stunnel.mirt.net/stunnel/%SUBDIR%/ \
http://www.namesdir.com/mirrors/stunnel/%SUBDIR%/ \
http://stunnel.cybermirror.org/%SUBDIR%/ \
http://mirrors.zerg.biz/stunnel/%SUBDIR%/ \
http://mirrors.rit.edu/zi/

MAINTAINER= z...@freebsd.org
COMMENT=SSL encryption wrapper for standard network daemons

# FIXME: IMHO, there really ought to be a GPL-2+ option or some such.
LICENSE=GPLv2 GPLv3
LICENSE_COMB=   dual

USES=   cpe libtool perl5 shebangfix ssl
USE_PERL5=  build
USE_LDCONFIG=   yes
USE_OPENSSL=yes
USE_RC_SUBR=stunnel

GNU_CONFIGURE=  yes
CONFIGURE_ARGS= --localstatedir=/var/tmp --enable-static --disable-systemd
SHEBANG_FILES=  src/stunnel3.in

OPTIONS_DEFINE= DOCS EXAMPLES FIPS IPV6 LIBWRAP
OPTIONS_SINGLE= THREAD
OPTIONS_SINGLE_THREAD=  FORK PTHREAD UCONTEXT

OPTIONS_DEFAULT=PTHREAD

FIPS_CONFIGURE_ENABLE=  fips
IPV6_CONFIGURE_ENABLE=  ipv6
LIBWRAP_CONFIGURE_ENABLE=   libwrap

FIPS_DESC=  Enable OpenSSL FIPS mode
FORK_DESC=  Use the fork(3) threading model
PTHREAD_DESC=   Use the pthread(3) threading model
UCONTEXT_DESC=  Use the ucontext(3) threading model

STUNNEL_USER?=  stunnel
STUNNEL_GROUP?= stunnel

USERS=  ${STUNNEL_USER}
GROUPS= ${STUNNEL_GROUP}

.include 

.if ${PORT_OPTIONS:MLIBWRAP}
LDFLAGS+=   -lwrap
.endif

.if ${PORT_OPTIONS:MUCONTEXT}
CONFIGURE_ARGS+=--with-threads=ucontext
LDFLAGS+=   -lpthread
.elif ${PORT_OPTIONS:MFORK}
CONFIGURE_ARGS+=--with-threads=fork
.else
CONFIGURE_ARGS+=--with-threads=pthread
LDFLAGS+=   -lpthread
.endif

.include 

.if ${PORT_OPTIONS:MFIPS} && ${SSL_DEFAULT} == libressl
IGNORE= LibreSSL does not support FIPS standard
.endif

.if ${SSL_DEFAULT} == libressl
NO_PACKAGE= The stunnel license restricts distribution when linked
to non-OpenSSL non-base SSL-libraries
.endif

post-patch:
# place files under /var/tmp so that this can be run by an unprivileged
# user stunnel and group stunnel
@${REINPLACE_CMD} -E -e
's|\@prefix\@/var/lib/stunnel/|/var/tmp/stunnel|; \
s|nobody|stunnel|;s|nogroup|stunnel|' \
${WRKSRC}/tools/stunnel.conf-sample.in
@${REINPLACE_CMD} -E -e
's|\$$\(prefix\)/var/run/stunnel/stunnel.pid|$$(localstatedir)/stunnel.pid|'
\
${WRKSRC}/src/Makefile.in
@${FIND} ${WRKSRC} -type f -name Makefile.in | ${XARGS}
${REINPLACE_CMD} -E -e 's,@(ACLOCAL|AUTO(MAKE|CONF|HEADER))@,/usr/bin/true,'
@${REINPLACE_CMD} -E -e 's|install-confDATA
install-data-local|install-confDATA|g' \
${WRKSRC}/tools/Makefile.in
.if empty(PORT_OPTIONS:MDOCS)
@${REINPLACE_CMD} -E -e 's/ install-docDATA/ /'
${WRKSRC}/Makefile.in
@${REINPLACE_CMD} -E -e '/install-data-am/s,install-docDATA,,'
${WRKSRC}/doc/Makefile.in
.endif
.if empty(PORT_OPTIONS:MEXAMPLES)
@${REINPLACE_CMD} -E -e 's/([^n])install-examplesDATA/\1/' \
${WRKSRC}/tools/Makefile.in
.else
@${REINPLACE_CMD} -E -e
's|\$$\(docdir\)/examples|${EXAMPLESDIR}|g' ${WRKSRC}/tools/Makefile.in
.endif

post-build:
@${STRIP_CMD} ${WRKSRC}/src/.libs/libstunnel.so

cert:
@${ECHO} ""
@${ECHO}
"**"
@${ECHO} "The new certificate will be saved into
${ETCDIR}/stunnel.pem"
@${ECHO}
"**"
@${ECHO} ""
@(cd ${WRKSRC}/tools/; make install-data-local)

.include 

-- 
J.
___
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: portmaster --check-port-dbdir is broken for me

2016-07-21 Thread Walter Schwarzenfeld 
Thorsten, after the remove of the  patch portmaster find the right files 
which are not installed, and nothing other.

It seems is was the patch.
___
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: portmaster --check-port-dbdir is broken for me

2016-07-21 Thread Torsten Zuehlsdorff 

Hello,


As it wants to literally remove all of the installed OPTIONS (xxx does not
seem to be installed).

What could have happened here? It went bad between 7-19 July. The system in
question was offline.


There was a patch included on 16 July. I could not figure out why it 
wants to remove everything at your computer. Can you remove the patch, 
rebuild portmaster and check if everything is fine again?


I set se@ into CC, because he wrote the patch.

Greetings,
Torsten

___
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: portmaster --check-port-dbdir is broken for me

2016-07-21 Thread Jakub Lach 
I blame recent portmaster update.



--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/portmaster-check-port-dbdir-is-broken-for-me-tp6115992p6116599.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
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: Is there still broken lang/ruby23 ?

2016-07-21 Thread Herbert J. Skuhra 
Kurt Jaeger skrev:
> 
> Hi!
>> Kazuhiko> Is there still broken lang/ruby23[1]. Or can build in latest
>> Kazuhiko> 11.0-* ? 
>> 
>> Kazuhiko> [1] 
>> http://permalink.gmane.org/gmane.os.freebsd.devel.pkg-fallout/294364
>> 
>> swills> Yes, I haven't looked at it yet, but if you want to take a look, I'd
>> swills> welcome patches.
>> 
>> Could you put the attached two patches into lang/ruby23/files and give
>> it a try?
> 
> Testbuild on 11a (r302198M) on a loaded host was OK, but make check-plist 
> found
> 
> bin/erb
> 
> missing. I'll now test poudriere.

Any update on this issue?

With this patch build works for me on FreeBSD 11.0-BETA1 amd64
(r303012).

# make check-plist
> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
===> Checking for items in pkg-plist which are not in STAGEDIR
===> No pkg-plist issues found (check-plist)

Thanks.

--
Herbert
___
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: stunnel fails to build

2016-07-21 Thread Dewayne Geraghty 
On 21 July 2016 at 18:15, tech-lists  wrote:

> Hi,
>
> ports: r418866
> stable/11: r302999
>
> I have the following defined in /etc/make.conf - could this be the issue?
>
> DEFAULT_VERSIONS+=  ssl=libressl-devel
>
> ###
>
> build fails like this:
>
> /usr/ports/security/stunnel # make MAKE_JOBS_UNSAFE=yes
> ===>  Building for stunnel-5.35,1
> Making all in src
> /usr/bin/make  all-am
>   CCLD libstunnel.la
>   CC   stunnel-tls.o
> In file included from tls.c:39:
> ./prototypes.h:656:9: error: unknown type name 'CRYPTO_RWLOCK'
> typedef CRYPTO_RWLOCK *STUNNEL_RWLOCK;
> ^
> tls.c:56:30: warning: incompatible pointer types passing 'void *(size_t,
> const char *, int)' (aka 'void *(unsigned long, const char *, int)') to
> parameter of type 'void *(*)(size_t)' (aka 'void *(*)(unsigned long)')
> [-Wincompatible-pointer-types]
> CRYPTO_set_mem_functions(str_alloc_detached_debug,
>  ^~~~
> /usr/local/include/openssl/crypto.h:412:38: note: passing argument to
> parameter 'm' here
> int CRYPTO_set_mem_functions(void *(*m)(size_t), void *(*r)(void *,
> size_t), void (*f)(void *));
>  ^
> tls.c:57:9: warning: incompatible pointer types passing 'void *(void *,
> size_t, const char *, int)' (aka 'void *(void *, unsigned long, const
> char *, int)') to parameter of type 'void *(*)(void *, size_t)' (aka
> 'void *(*)(void *, unsigned long)') [-Wincompatible-pointer-types]
> str_realloc_debug, str_free_debug);
> ^
> /usr/local/include/openssl/crypto.h:412:58: note: passing argument to
> parameter 'r' here
> int CRYPTO_set_mem_functions(void *(*m)(size_t), void *(*r)(void *,
> size_t), void (*f)(void *));
>  ^
> tls.c:57:28: warning: incompatible pointer types passing 'void (void *,
> const char *, int)' to parameter of type 'void (*)(void *)'
> [-Wincompatible-pointer-types]
> str_realloc_debug, str_free_debug);
>^~
> /usr/local/include/openssl/crypto.h:412:85: note: passing argument to
> parameter 'f' here
> int CRYPTO_set_mem_functions(void *(*m)(size_t), void *(*r)(void *,
> size_t), void (*f)(void *));
>
>^
> 3 warnings and 1 error generated.
> *** Error code 1
>
> Stop.
> make[4]: stopped in /usr/ports/security/stunnel/work/stunnel-5.35/src
> *** Error code 1
>
> Stop.
> make[3]: stopped in /usr/ports/security/stunnel/work/stunnel-5.35/src
> *** Error code 1
>
> Stop.
> make[2]: stopped in /usr/ports/security/stunnel/work/stunnel-5.35
> *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/ports/security/stunnel
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/security/stunnel
>
> ===
>
> same issues on -current
>
> thanks,
> --
> J.
> ___
> 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"
>

After reading about your issue, I updated all of my ports, via svnlite, and
successfully built on yesterday's fresh FreeBSD 10.3 Stable for i386 using
openssl.  Unfortunately on the amd64, which uses libressl, I receive:
===>  stunnel-5.35,1 may not be packaged: The stunnel license restricts
distribution when linked to non-OpenSSL non-base SSL-libraries.  (A recent
enhancement)

My customisations are:
i386 uses make.conf entry:  ssl=openssl
amd64 uses make.conf:  ssl=libressl
This may be significant to your situation?

If there is a problem with the Makefile, please log a PR so everyone can
benefit.  ;)
___
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: stunnel fails to build

2016-07-21 Thread Walter Schwarzenfeld 

Try:
remove  --with-ssl="${OPENSSLBASE}"
from the Makefile
and add
to USES= ssl

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

Why doesn't graphics/gd build with webp?

2016-07-21 Thread Christian Ullrich 

Hello all,

the latest update to graphics/gd added a BROKEN flag if webp support is 
enabled, for reasons of "circular dependencies". I've looked through all 
options I can find, but there is no sign of any direct or indirect 
dependency of graphics/webp on graphics/gd.


What's going on?

Thanks,

--
Christian

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

stunnel fails to build

2016-07-21 Thread tech-lists 
Hi,

ports: r418866
stable/11: r302999

I have the following defined in /etc/make.conf - could this be the issue?

DEFAULT_VERSIONS+=  ssl=libressl-devel

###

build fails like this:

/usr/ports/security/stunnel # make MAKE_JOBS_UNSAFE=yes
===>  Building for stunnel-5.35,1
Making all in src
/usr/bin/make  all-am
  CCLD libstunnel.la
  CC   stunnel-tls.o
In file included from tls.c:39:
./prototypes.h:656:9: error: unknown type name 'CRYPTO_RWLOCK'
typedef CRYPTO_RWLOCK *STUNNEL_RWLOCK;
^
tls.c:56:30: warning: incompatible pointer types passing 'void *(size_t,
const char *, int)' (aka 'void *(unsigned long, const char *, int)') to
parameter of type 'void *(*)(size_t)' (aka 'void *(*)(unsigned long)')
[-Wincompatible-pointer-types]
CRYPTO_set_mem_functions(str_alloc_detached_debug,
 ^~~~
/usr/local/include/openssl/crypto.h:412:38: note: passing argument to
parameter 'm' here
int CRYPTO_set_mem_functions(void *(*m)(size_t), void *(*r)(void *,
size_t), void (*f)(void *));
 ^
tls.c:57:9: warning: incompatible pointer types passing 'void *(void *,
size_t, const char *, int)' (aka 'void *(void *, unsigned long, const
char *, int)') to parameter of type 'void *(*)(void *, size_t)' (aka
'void *(*)(void *, unsigned long)') [-Wincompatible-pointer-types]
str_realloc_debug, str_free_debug);
^
/usr/local/include/openssl/crypto.h:412:58: note: passing argument to
parameter 'r' here
int CRYPTO_set_mem_functions(void *(*m)(size_t), void *(*r)(void *,
size_t), void (*f)(void *));
 ^
tls.c:57:28: warning: incompatible pointer types passing 'void (void *,
const char *, int)' to parameter of type 'void (*)(void *)'
[-Wincompatible-pointer-types]
str_realloc_debug, str_free_debug);
   ^~
/usr/local/include/openssl/crypto.h:412:85: note: passing argument to
parameter 'f' here
int CRYPTO_set_mem_functions(void *(*m)(size_t), void *(*r)(void *,
size_t), void (*f)(void *));

   ^
3 warnings and 1 error generated.
*** Error code 1

Stop.
make[4]: stopped in /usr/ports/security/stunnel/work/stunnel-5.35/src
*** Error code 1

Stop.
make[3]: stopped in /usr/ports/security/stunnel/work/stunnel-5.35/src
*** Error code 1

Stop.
make[2]: stopped in /usr/ports/security/stunnel/work/stunnel-5.35
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/security/stunnel
*** Error code 1

Stop.
make: stopped in /usr/ports/security/stunnel

===

same issues on -current

thanks,
-- 
J.
___
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"

Passing target to source Makefile

2016-07-21 Thread Russell Haley 
Hi there,

I've been able to hack up the Makefile for an update of lua53 but the
one thing still missing is the ability to pass a target for the source
Makefile (i.e. lua's Makefile, not the ports Makefile). I need to pass
in "freebsd" as per the build instructions for lua.

Also, I can't seem to get make makeplist to work, but I think that's
because the lua makefile is defaulting to install the files (due to
the lack of target) and overriding the makeplist output?

Thanks,

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