Re: Problems with out libgcc_s.so in base

2016-08-17 Thread Steve Kargl 
On Wed, Aug 17, 2016 at 06:12:51PM -0400, Diane Bruce wrote:
> On Wed, Aug 17, 2016 at 02:17:10PM -0700, Steve Kargl wrote:
> > On Sun, Aug 14, 2016 at 07:34:30PM -0400, Diane Bruce wrote:
> > > On Sun, Aug 14, 2016 at 04:03:51PM -0700, Steve Kargl wrote:
> > > > 
> > > > Freebsd-ports could also use a wrapper:
> > > 
> > > Yes. I have also suggested we use a wrapper to the ports guys.
> > > 
> > 
> > I thought about this a bit, and cleaner solution might be
> > to add the program suffix to libgcc_s.so.1.  For example,
> > 
> > % cat foo.f90
> > program foo
> >print *, 'Hello'
> > end program
> > % gfortran6 -o z foo.f90 && ./z
> > /lib/libgcc_s.so.1: version GCC_4.6.0 required by \
> > /usr/local/lib/gcc6/libgfortran.so.3 not found
> > % ldconfig -r | grep libgcc
> > 6:-lgcc_s.1 => /lib/libgcc_s.so.1
> > 735:-lgcc_s.1 => /usr/local/lib/gcc6/libgcc_s.so.1
> > 
> > Clearly, ldd is looking for 735 but finds 6.  If the lang/gcc6 could
> > be convinced to build, install, and use libgcc_s6.so.1, then the
> > problem is solved without a wrapper.
> 
> I like this solution. 
> 

I have asked on g...@gcc.gnu.org if it is possible to configure
gcc as above.  I know that one can bump the shared lib number,
but that won't solve the problem.

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

Re: Problems with out libgcc_s.so in base

2016-08-17 Thread Diane Bruce 
On Wed, Aug 17, 2016 at 02:17:10PM -0700, Steve Kargl wrote:
> On Sun, Aug 14, 2016 at 07:34:30PM -0400, Diane Bruce wrote:
> > On Sun, Aug 14, 2016 at 04:03:51PM -0700, Steve Kargl wrote:
> > > 
> > > Freebsd-ports could also use a wrapper:
> > > % cat ~/bin/gfc7
> > > #! /bin/sh
> > > DIR=`id -P sgk | sed 's/\:/\ /g' | awk '{print $9}'`
> > > export DIR
> > > 
> > > LD_LIBRARY_PATH=$DIR/work/7/lib
> > > export LD_LIBRARY_PATH
> > > 
> > > LD_RUN_PATH=$DIR/work/7/lib
> > > export LD_RUN_PATH
> > > 
> > > $DIR/work/7/bin/gfortran -fno-backtrace $@
> > 
> > Yes. I have also suggested we use a wrapper to the ports guys.
> > 
> 
> I thought about this a bit, and cleaner solution might be
> to add the program suffix to libgcc_s.so.1.  For example,
> 
> % cat foo.f90
> program foo
>print *, 'Hello'
> end program
> % gfortran6 -o z foo.f90 && ./z
> /lib/libgcc_s.so.1: version GCC_4.6.0 required by \
> /usr/local/lib/gcc6/libgfortran.so.3 not found
> % ldconfig -r | grep libgcc
> 6:-lgcc_s.1 => /lib/libgcc_s.so.1
> 735:-lgcc_s.1 => /usr/local/lib/gcc6/libgcc_s.so.1
> 
> Clearly, ldd is looking for 735 but finds 6.  If the lang/gcc6 could
> be convinced to build, install, and use libgcc_s6.so.1, then the
> problem is solved without a wrapper.

I like this solution. 

> 
> -- 
> Steve
> 

Diane
-- 
- d...@freebsd.org d...@db.net http://www.db.net/~db
___
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: HEADS UP: ports r420340 breaks installation and packaging of empty directories

2016-08-17 Thread Dimitry Andric 
On 17 Aug 2016, at 22:12, Mathieu Arnold  wrote:
> 
> +--On 17 août 2016 22:56:36 +0200 Dimitry Andric  wrote:
> | I just got bitten by a nasty side effect of r420340 [1] ("Move USE_BDB
> | and PLIST_DIRSTRY to the unsupported section, all the ports have been
> | converted").
...
> Fixed.

Thanks for the quick fix.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Problems with out libgcc_s.so in base

2016-08-17 Thread Steve Kargl 
On Sun, Aug 14, 2016 at 07:34:30PM -0400, Diane Bruce wrote:
> On Sun, Aug 14, 2016 at 04:03:51PM -0700, Steve Kargl wrote:
> > 
> > Freebsd-ports could also use a wrapper:
> > % cat ~/bin/gfc7
> > #! /bin/sh
> > DIR=`id -P sgk | sed 's/\:/\ /g' | awk '{print $9}'`
> > export DIR
> > 
> > LD_LIBRARY_PATH=$DIR/work/7/lib
> > export LD_LIBRARY_PATH
> > 
> > LD_RUN_PATH=$DIR/work/7/lib
> > export LD_RUN_PATH
> > 
> > $DIR/work/7/bin/gfortran -fno-backtrace $@
> 
> Yes. I have also suggested we use a wrapper to the ports guys.
> 

I thought about this a bit, and cleaner solution might be
to add the program suffix to libgcc_s.so.1.  For example,

% cat foo.f90
program foo
   print *, 'Hello'
end program
% gfortran6 -o z foo.f90 && ./z
/lib/libgcc_s.so.1: version GCC_4.6.0 required by \
/usr/local/lib/gcc6/libgfortran.so.3 not found
% ldconfig -r | grep libgcc
6:-lgcc_s.1 => /lib/libgcc_s.so.1
735:-lgcc_s.1 => /usr/local/lib/gcc6/libgcc_s.so.1

Clearly, ldd is looking for 735 but finds 6.  If the lang/gcc6 could
be convinced to build, install, and use libgcc_s6.so.1, then the
problem is solved without a wrapper.

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

Re: HEADS UP: ports r420340 breaks installation and packaging of empty directories

2016-08-17 Thread Mathieu Arnold 


+--On 17 août 2016 22:56:36 +0200 Dimitry Andric  wrote:
| Hi,
| 
| I just got bitten by a nasty side effect of r420340 [1] ("Move USE_BDB
| and PLIST_DIRSTRY to the unsupported section, all the ports have been
| converted").
| 
| The effect is that empty directories don't get installed or packaged
| anymore, and this can lead to all kinds of interesting errors.  In my
| case, for example, xmlcatmgr failed to install correctly, because it
| couldn't find /usr/local/share/xml.
| 
| Please revert this commit locally, or don't update to r420340 for now,
| until this problem gets fixed.  I submitted bug 211953 [2] in the mean
| time.
| 
| -Dimitry
| 
| [1] https://svnweb.freebsd.org/changeset/ports/420340
| [2] https://bugs.freebsd.org/211953

Fixed.

-- 
Mathieu Arnold

pgp6jUe7iKYdX.pgp
Description: PGP signature

HEADS UP: ports r420340 breaks installation and packaging of empty directories

2016-08-17 Thread Dimitry Andric 
Hi,

I just got bitten by a nasty side effect of r420340 [1] ("Move USE_BDB
and PLIST_DIRSTRY to the unsupported section, all the ports have been
converted").

The effect is that empty directories don't get installed or packaged
anymore, and this can lead to all kinds of interesting errors.  In my
case, for example, xmlcatmgr failed to install correctly, because it
couldn't find /usr/local/share/xml.

Please revert this commit locally, or don't update to r420340 for now,
until this problem gets fixed.  I submitted bug 211953 [2] in the mean
time.

-Dimitry

[1] https://svnweb.freebsd.org/changeset/ports/420340
[2] https://bugs.freebsd.org/211953



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: parcimonie (0.8.4-1)

2016-08-17 Thread Kurt Jaeger 
Hi!

> There isn't a port for "parcimonie (0.8.4-1)"
> https://packages.debian.org/jessie/parcimonie that I can find.

I found 

https://gaffer.ptitcanardnoir.org/intrigeri/code/parcimonie/

as the upstream for this, but the website does not respond.

> Is anyone working on this

I've searched 

https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=parcimonie_id=130490

and

https://wiki.freebsd.org/WantedPorts

and found nothing, so: Nobody is working on this.

> or have a suggestion for a similar application
> that works under FreeBSD?

https://github.com/EtiennePerot/parcimonie.sh

looks like a simple bash script -- would this work for you ?

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

parcimonie (0.8.4-1)

2016-08-17 Thread Gerard Seibert 
There isn't a port for "parcimonie (0.8.4-1)"
https://packages.debian.org/jessie/parcimonie that I can find. Is
anyone working on this or have a suggestion for a similar application
that works under FreeBSD?

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

Re: Gimp and PostScript

2016-08-17 Thread BERTRAND Joël 

Wojciech Puchar a écrit :

1) wrong list - should be freebsd-ports


Sorry for the mistake. I believe I have posted on freebsd-ports.


2) please give some more info about error message.


	There is no error message. Gimp cannot open or save Postscript files. 
Postscript doesn't not appear in known format files.


Best regards,

JKB

___
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 FreeBSD rxtx port require Linux

2016-08-17 Thread Howard Su 
I noticed that you enable USE_LINUX in this port. As far as I can tell,
rxtx supports *BSD. why this require LINUX emulation? The change is
introduced via
https://svnweb.freebsd.org/ports?view=revision=390725 and it is
not mentioned in the revision description.

-Howard
-- 
-Howard
___
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: Gimp and PostScript

2016-08-17 Thread Wojciech Puchar 

1) wrong list - should be freebsd-ports
2) please give some more info about error message.



On Sat, 13 Aug 2016, BERTRAND Joël wrote:


Hello,

	I'm trying to use Gimp with Ghostscript to import and export eps 
files. I have installed gimp (and all dependencies) and ghostscript 9. Of 
course, gs runs as expected (in /usr/local/bin) but I'm unable to work on eps 
files in gimp.


	Both gimp and ghostscript come from binary ports (for FreeBSD 10.3) 
and I don't understand my mistake. Help is welcome to fix this issue.


Best regards,

JB
___
freebsd-hack...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-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: net/qt5-network failing on stable/10

2016-08-17 Thread Russell L. Carter 



On 08/17/16 00:59, Sascha Holzleiter wrote:

On 2016-08-17 00:51, Russell L. Carter wrote:

Hi,
For about a week now I have been having some build failures
that cause a lot of dependent port builds in poudriere
to get skipped.

Focusing on one of the first ones, net/qt5-network fails
in 'build'.


Have a look at
 for a patch.


Thanks very much for the pointer.  After reading through the reports,
I have to conclude that libressl is not ready for primetime.  Back
to (shudder) openssl.

Russell





poudriere tells me it saved the wrkdir to:

/ssd1/poudriere/data/wrkdirs/10-stable-amd64-default/default/qt5-network-5.5.1.tbz


Which I untarred and poked around a bit, but I don't see any
obvious problems.  What's the best way to debug this?  The
problems seem to have started around the libressl update, and
I have the following /usr/local/etc/poudriere.d/make.conf:

# Build ports against security/libressl
WITH_OPENSSL_PORT=  yes
OPENSSL_PORT=   security/libressl
# See ~ports/Mk/bsd.default-versions.mk
DEFAULT_VERSIONS=pgsql=9.5 ssl=libressl
#  Set this to the list of ports you wish to rebuild every time the
#  kernel is built.
PORTS_MODULES=nvidia-driver-340  nvidia-driver

Also failing: stunnel, xca, calibre, ssvnc.

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"

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

PR looking for committer

2016-08-17 Thread Fernando Apesteguía 
Hi,

Can a committer have a look at this simple update?

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

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

FreeBSD ports you maintain which are out of date

2016-08-17 Thread portscout 
Dear port maintainer,

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

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

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


Port| Current version | New version
+-+
games/uhexen2   | 1.5.7   | 1.5.8
+-+
science/psychopy| 1.83.04 | 1.84.0
+-+


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

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

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