FreeBSD ports you maintain which are out of date
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 +-+ databases/p5-DBIx-SQLite-Simple | 0.34| 0.35 +-+ lang/execline | 1.08| 2.0.1.0 +-+ textproc/py-jaxml | 3.02| 18.00 +-+ 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 http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: npviewer.bin: exec format error
From miche...@sorbs.net Tue Jan 6 17:04:09 2015 Anton Shterenlikht wrote: After upgrading to 10.1-release and updating all ports via pkg, I get this error on amd64: Saw something similar (not using pkg or 10.x) on my hosts the other day... Was when I accidentally installed amd64 binaries over a i386 kernel (the reverse is also true) ... did you install amd64 on a host over an existing i386? If so pkg might not realise you changed the arch. no, definitely not. This was always an amd64 box, updated via freebsd-update only. 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
Re: devel/ccache
On 1/4/2015 6:27 AM, Kurt Jaeger wrote: Hi! Is there a plan to update the devel/ccache port? The new version has improved clang support. If you can provide a patch that updates this, this certainly would speed it up 8-} Mailing the maintainer usually helps. -- Regards, Bryan Drewery ___ 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: multimedia/libva fails in configure stage, missing file?
I ran automake -v in the WRKSRC directory (/usr/ports/multimedia/libva-1.5.0) and failed on error configure.ac:166: error: required file './ltmain.sh' not found You asked for the log from failed build of libva-1.5.0, here it is: ]0;portmaster: multimedia/libva === Port directory: /usr/ports/multimedia/libva === Gathering distinfo list for installed ports === Launching 'make checksum' for multimedia/libva in background === Gathering dependency list for multimedia/libva from ports === Initial dependency check complete for multimedia/libva ]0;portmaster: multimedia/libva === Starting build for multimedia/libva === === All dependencies are up to date === Cleaning for libva-1.5.0 === License MIT accepted by the user === Found saved configuration for libva-1.3.1_3 === libva-1.5.0 depends on file: /usr/local/sbin/pkg - found === Fetching all distfiles required by libva-1.5.0 for building === Extracting for libva-1.5.0 = SHA256 Checksum OK for libva-1.5.0.tar.bz2. === Patching for libva-1.5.0 === Applying FreeBSD patches for libva-1.5.0 === libva-1.5.0 depends on file: /usr/local/include/linux/videodev2.h - found === libva-1.5.0 depends on executable: autoconf-2.69 - found === libva-1.5.0 depends on executable: autoheader-2.69 - found === libva-1.5.0 depends on executable: autoreconf-2.69 - found === libva-1.5.0 depends on executable: aclocal-1.14 - found === libva-1.5.0 depends on executable: automake-1.14 - found === libva-1.5.0 depends on executable: libtoolize - found === libva-1.5.0 depends on executable: gmake - found === libva-1.5.0 depends on executable: pkgconf - found === libva-1.5.0 depends on file: /usr/local/libdata/pkgconfig/glproto.pc - found === libva-1.5.0 depends on file: /usr/local/libdata/pkgconfig/glproto.pc - found === libva-1.5.0 depends on file: /usr/local/libdata/pkgconfig/dri2proto.pc - found === libva-1.5.0 depends on file: /usr/local/libdata/pkgconfig/pciaccess.pc - found === libva-1.5.0 depends on file: /usr/local/libdata/pkgconfig/xext.pc - found === libva-1.5.0 depends on file: /usr/local/libdata/pkgconfig/xfixes.pc - found === libva-1.5.0 depends on shared library: libdrm.so - found (/usr/local/lib/libdrm.so.2.4.0) === libva-1.5.0 depends on shared library: libGL.so - found (/usr/local/lib/libGL.so) === Configuring for libva-1.5.0 aclocal-1.14: warning: couldn't open directory 'm4': No such file or directory aclocal-1.14: warning: couldn't open directory 'm4': No such file or directory configure.ac:166: installing './compile' configure.ac:166: installing './config.guess' configure.ac:166: installing './config.sub' configure.ac:87: installing './install-sh' configure.ac:166: error: required file './ltmain.sh' not found configure.ac:87: installing './missing' dummy_drv_video/Makefile.am: installing './depcomp' automake-1.14: warning: redefinition of 'info' ... /usr/local/share/automake-1.14/am/program.am: ... 'info$(EXEEXT)' previously defined here test/vainfo/Makefile.am:23: while processing program 'info' va/wayland/Makefile.am:33: warning: source file '$(top_srcdir)/va/drm/va_drm_utils.c' is in a subdirectory, va/wayland/Makefile.am:33: but option 'subdir-objects' is disabled automake-1.14: warning: possible forward-incompatibility. automake-1.14: At least a source file is in a subdirectory, but the 'subdir-objects' automake-1.14: automake option hasn't been enabled. For now, the corresponding output automake-1.14: object file(s) will be placed in the top-level directory. However, automake-1.14: this behaviour will change in future Automake versions: they will automake-1.14: unconditionally cause object files to be placed in the same subdirectory automake-1.14: of the corresponding sources. automake-1.14: You are advised to start using 'subdir-objects' option throughout your automake-1.14: project, to avoid future incompatibilities. autoreconf-2.69: automake failed with exit status: 1 *** Error code 1 Stop. make[1]: stopped in /usr/ports/multimedia/libva *** Error code 1 Stop. make: stopped in /usr/ports/multimedia/libva === make build failed for multimedia/libva === Aborting update === You can restart from the point of failure with this command line: portmaster flags multimedia/libva Email is on other computer, running NetBSD where FreeBSD fails to connect via Ethernet, hence lack of email headers such as References: and lack of quoting. 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: Combining GitHub and regular MASTER_SITES for multiple DISTFILES
On 1/4/2015 8:49 AM, Ben Woods wrote:
I am trying to create a new port, where the main source code should be
retrieved from GitHub, and a secondary piece of source code should be
retrieved from an FTP site.
The USE_GITHUB port magic does not work for the primary source code if the
MASTER_SITES and DISTFILES variables are also specified in the Makefile for
the secondary source code. The result is that only the secondary code is
downloaded and extracted. Using += for the MASTER_SITES and DISTFILES
assignment does not fix the issue.
Is there a way that these can be used together for this propose?
Regards,
Ben
See ports-mgmt/poudriere Makefile.
Use 'GH' in MASTER_SITES for the USE_GITHUB source:
MASTER_SITES= LOCAL/bdrewery/${PORTNAME}/ \
http://mirror.shatow.net/freebsd/${PORTNAME}/ \
GH
You can use whatever order you wish.
--
Regards,
Bryan Drewery
___
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: devel/ccache
On 1/6/2015 5:59 PM, Bryan Drewery wrote: On 1/4/2015 6:27 AM, Kurt Jaeger wrote: Hi! Is there a plan to update the devel/ccache port? The new version has improved clang support. If you can provide a patch that updates this, this certainly would speed it up 8-} Mailing the maintainer usually helps. I've committed the update to 3.2.1 now. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: How does the Additional FreeBSD Contributors page work?
On Thu, Jan 01, 2015 at 06:05:38PM -0800, Chris H wrote: Greetings, and Happy New Year! I was reading through the Porters Handbook today, and while reading 3.6. Submitting the New Port, I noticed the link at the end to 8. Additional FreeBSD Contributors (https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/contrib-additional.html). Being a maintainer of ~35 ports (https://www.freebsd.org/cgi/ports.cgi?query=portmaster@stype=maintainer) (tho ~5 are still waiting to be committed), I thought I'd see if I was listed. But discovered I wasn't. Given that maintainers of 1 port, and as little as 1mos. tenure are listed. I assumed that I must have misunderstood what the page represents. Would anyone be willing to clarify? Or am I simply blacklisted? ;) Thanks, and again, Happy New Year, to all! --Chris Chris, I added you to the list. Thanks a lot for your contributions. Lars pgppu7SiNXZrW.pgp Description: PGP signature
Re: Help with porting FreeCAD
On Tue, 06 Jan 2015 23:12:48 +0100 Andrea Venturoli m...@netfence.it wrote Hello. A while ago I dirty-ported FreeCAD 0.14 and more or less got it working. Now it won't work anymore due to incompatible changes in OpenCASCADE (which is a dependency); so I'm trying 0.15 (which is still a beta). The box I'm using runs 9.3 and I'm facing a problem I'm too inexperienced about the port system to solve: _ g++ 4.9 seems to be needed (previous versions having an unsolved bug), so I put USE_GCC=4.9; _ however, fortran is required and USES=fortran:gcc picks up gfortran48; _ so in the link stage -L/usr/local/lib/gcc48 comes before -L/usr/local/lib/gcc49 and I get unresolved symbols. Is there a way I can tell the port system to pick gfortran49 instead of gfortran48 and forget about -L/usr/local/lib/gcc48? Of course I could try uninstalling gcc-4.8.4, but this is unfortunately a run dependency of several other ports. I think what you're looking for here is BUILD_DEPENDS= and RUN_DEPENDS= --Chris bye Thanks av. ___ 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-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: Help with porting FreeCAD
On Tue, 06 Jan 2015 23:49:41 +0100 Andrea Venturoli m...@netfence.it wrote
On 01/06/15 23:41, Chris H wrote:
On Tue, 06 Jan 2015 23:12:48 +0100 Andrea Venturoli m...@netfence.it wrote
Hello.
A while ago I dirty-ported FreeCAD 0.14 and more or less got it working.
Now it won't work anymore due to incompatible changes in OpenCASCADE
(which is a dependency); so I'm trying 0.15 (which is still a beta).
The box I'm using runs 9.3 and I'm facing a problem I'm too
inexperienced about the port system to solve:
_ g++ 4.9 seems to be needed (previous versions having an unsolved bug),
so I put USE_GCC=4.9;
_ however, fortran is required and USES=fortran:gcc picks up gfortran48;
_ so in the link stage -L/usr/local/lib/gcc48 comes before
-L/usr/local/lib/gcc49 and I get unresolved symbols.
Is there a way I can tell the port system to pick gfortran49 instead of
gfortran48 and forget about -L/usr/local/lib/gcc48?
Of course I could try uninstalling gcc-4.8.4, but this is unfortunately
a run dependency of several other ports.
I think what you're looking for here is
BUILD_DEPENDS=
and
RUN_DEPENDS=
Thanks, but, sorry, I don't quite get your suggestion.
What should I put into those variables?
How would that solve the above problem?
Sure. OK.
Maybe something along the lines of:
BUILD_DEPENDS+= ${PREFIX}/bin/gcc49:${PORTSDIR}/lang/gcc49
Also, regarding your USE_GCC
you would do well to choose:
USE_GCC=4.9+
which says: Must use gcc49, or greater.
All the best.
--Chris
bye Thanks
av.
___
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-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Help with porting FreeCAD
Hello. A while ago I dirty-ported FreeCAD 0.14 and more or less got it working. Now it won't work anymore due to incompatible changes in OpenCASCADE (which is a dependency); so I'm trying 0.15 (which is still a beta). The box I'm using runs 9.3 and I'm facing a problem I'm too inexperienced about the port system to solve: _ g++ 4.9 seems to be needed (previous versions having an unsolved bug), so I put USE_GCC=4.9; _ however, fortran is required and USES=fortran:gcc picks up gfortran48; _ so in the link stage -L/usr/local/lib/gcc48 comes before -L/usr/local/lib/gcc49 and I get unresolved symbols. Is there a way I can tell the port system to pick gfortran49 instead of gfortran48 and forget about -L/usr/local/lib/gcc48? Of course I could try uninstalling gcc-4.8.4, but this is unfortunately a run dependency of several other ports. bye Thanks av. ___ 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: Help with porting FreeCAD
On 01/06/15 23:41, Chris H wrote: On Tue, 06 Jan 2015 23:12:48 +0100 Andrea Venturoli m...@netfence.it wrote Hello. A while ago I dirty-ported FreeCAD 0.14 and more or less got it working. Now it won't work anymore due to incompatible changes in OpenCASCADE (which is a dependency); so I'm trying 0.15 (which is still a beta). The box I'm using runs 9.3 and I'm facing a problem I'm too inexperienced about the port system to solve: _ g++ 4.9 seems to be needed (previous versions having an unsolved bug), so I put USE_GCC=4.9; _ however, fortran is required and USES=fortran:gcc picks up gfortran48; _ so in the link stage -L/usr/local/lib/gcc48 comes before -L/usr/local/lib/gcc49 and I get unresolved symbols. Is there a way I can tell the port system to pick gfortran49 instead of gfortran48 and forget about -L/usr/local/lib/gcc48? Of course I could try uninstalling gcc-4.8.4, but this is unfortunately a run dependency of several other ports. I think what you're looking for here is BUILD_DEPENDS= and RUN_DEPENDS= Thanks, but, sorry, I don't quite get your suggestion. What should I put into those variables? How would that solve the above problem? bye Thanks av. ___ 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: Help with porting FreeCAD
On Tue, Jan 6, 2015 at 4:12 PM, Andrea Venturoli m...@netfence.it wrote:
Hello.
A while ago I dirty-ported FreeCAD 0.14 and more or less got it working.
Now it won't work anymore due to incompatible changes in OpenCASCADE (which
is a dependency); so I'm trying 0.15 (which is still a beta).
The box I'm using runs 9.3 and I'm facing a problem I'm too inexperienced
about the port system to solve:
_ g++ 4.9 seems to be needed (previous versions having an unsolved bug), so
I put USE_GCC=4.9;
_ however, fortran is required and USES=fortran:gcc picks up gfortran48;
_ so in the link stage -L/usr/local/lib/gcc48 comes before
-L/usr/local/lib/gcc49 and I get unresolved symbols.
Is there a way I can tell the port system to pick gfortran49 instead of
gfortran48 and forget about -L/usr/local/lib/gcc48?
Of course I could try uninstalling gcc-4.8.4, but this is unfortunately a
run dependency of several other ports.
I had a look at Mk/Uses/fortran.mk, it picks the version of fortran to
install based on the value found in either Mk/bsd.default-versions.mk
or the value defined in DEFAULT_VERSIONS. Unfortunately, it doesn't
have a clean way to specify a specific version.
It looks like you can override the value by setting GCC_DEFAULT.
USE_GCC= 4.9
GCC_DEFAULT= 4.9
USES= fortran:gcc
or
USE_GCC= 4.9+
GCC_DEFAULT= ${_USE_GCC}
USES= fortran:gcc
Note: _USE_GCC is defined by Mk/bsd.gcc.mk when it finds a version
that satisfies USE_GCC.
--
DISCLAIMER:
No electrons were maimed while sending this message. Only slightly bruised.
___
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
npviewer.bin: exec format error
After upgrading to 10.1-release and updating all ports via pkg, I get this error on amd64: % nspluginwrapper -v -a -i Auto-install plugins from /usr/local/lib/browser_plugins Looking for plugins in /usr/local/lib/browser_plugins Auto-install plugins from /usr/local/lib/browser_plugins/linux-c6-flashplugin Looking for plugins in /usr/local/lib/browser_plugins/linux-c6-flashplugin ELF binary type 0 not known. exec: /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin: Exec format error ELF binary type 0 not known. exec: /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin: Exec format error Auto-install plugins from /usr/local/lib/browser_plugins/symlinks/linux-firefox Looking for plugins in /usr/local/lib/browser_plugins/symlinks/linux-firefox ELF binary type 0 not known. exec: /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin: Exec format error ELF binary type 0 not known. exec: /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin: Exec format error Auto-install plugins from /home/mexas/.mozilla/plugins Looking for plugins in /home/mexas/.mozilla/plugins The flash plugin doesn't work in firefox. % pkg info -xo flash fire nsplug linux-c6-flashplugin-11.2r202.425 www/linux-c6-flashplugin11 firefox-34.0.5_1,1 www/firefox nspluginwrapper-1.4.4_4www/nspluginwrapper % freebsd-version -ku 10.1-RELEASE 10.1-RELEASE-p3 % uname -a hostname 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 Please advise Thanks 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
