Evince fails upgrade
Hello Port readers I am unable to upgrade to latest evince due to following failure. Evince now calls for www/yelp which calls for www/libxul which has vulnerabilities. [robert@dell64] /usr/ports/x11/yelp% sudo make install clean yelp is using libxul for gecko support, but you can change that by defining WITH_GECKO to the following values: libxul ===> License check disabled, port has not defined LICENSE ===> Extracting for yelp-2.30.2_2 => SHA256 Checksum OK for gnome2/yelp-2.30.2.tar.bz2. /bin/rm -f /usr/ports/x11/yelp/work/yelp-2.30.2/data/yelp.schemas ===> Patching for yelp-2.30.2_2 ===> Applying FreeBSD patches for yelp-2.30.2_2 ===> yelp-2.30.2_2 depends on file: /usr/local/lib/libxul/libxul.so - not found ===>Verifying install for /usr/local/lib/libxul/libxul.so in /usr/ports/www/libxul ===> libxul-1.9.2.28 has known vulnerabilities: Affected package: libxul-1.9.2.28 Type of problem: mozilla -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/380e8c56-8e32-11e1-9580-4061862b8c22.html => Please update your ports tree and try again. *** Error code 1 Stop in /usr/ports/www/libxul. *** Error code 1 Stop in /usr/ports/www/libxul. *** Error code 1 Stop in /usr/ports/x11/yelp. I have tried to comment out the WITH_GECKO line but that fails also. The Makefile already has WITH_GECKO= libxul What do I need to change it to? TIA Robert ___ 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: graphics/gdal 1.9.0 does not build on CURRENT
On 22.05.2012 22:45 (UTC+1), Rainer Hurling wrote: On 22.05.2012 20:15 (UTC+1), coder.tuxfamily wrote: I have rewrote the patch. Maybe with this new patch... Thanks, but again it gives me the same failure: libtool: compile: cc -DNDEBUG -O2 -pipe -O2 -fno-strict-aliasing -pipe -msse3 -O2 -pipe -O2 -fno-strict-aliasing -pipe -msse3 -Wall -Wdeclaration-after-statement -DOGR_ENABLED -I/usr/local/include -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr -I/usr/include -fPIC -I../../port -I../../gcore -I../../alg -I../../ogr/ -I/usr/local/include/python2.7 -I/usr/local/lib/python2.7/site-packages/numpy/core/include -I/usr/ports/graphics/gdal/work/gdal-1.9.0/include -c extensions/gdal_wrap.cpp -fPIC -DPIC -o build/temp.freebsd-10.0-CURRENT-amd64-2.7/extensions/.libs/gdal_wrap.o cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++ extensions/gdal_wrap.cpp: In function 'PyObject* _wrap_VSIFTruncateL(PyObject*, PyObject*)': extensions/gdal_wrap.cpp:6845: error: 'VSIFTruncateL' was not declared in this scope extensions/gdal_wrap.cpp: In function 'PyObject* _wrap_MajorObject_SetMetadata__SWIG_0(PyObject*, PyObject*)': extensions/gdal_wrap.cpp:7220: warning: deprecated conversion from string constant to 'char*' error: command '/bin/sh' failed with exit status 1 gmake[2]: *** [build] Fehler 1 gmake[2]: Leaving directory `/usr/ports/graphics/gdal/work/gdal-1.9.0/swig/python' gmake[1]: *** [build] Fehler 2 gmake[1]: Leaving directory `/usr/ports/graphics/gdal/work/gdal-1.9.0/swig' gmake: *** [swig-modules] Fehler 2 *** [do-build] Error code 1 Stop in /usr/ports/graphics/gdal. I don't think there is a problem with finding libtool or some python scripts. I will rebuild all my py27- ports and swig, just to be sure. OK, I think I get it. This failure does not happen, if swig is not installed. Then it builds and installs fine. Do you have any idea what is going wrong with swig here? ___ 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: graphics/gdal 1.9.0 does not build on CURRENT
OK, I think I get it. This failure does not happen, if swig is not installed. Then it builds and installs fine. Do you have any idea what is going wrong with swig here? ___ 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" OK. Maybe inclue the swig dependancy into the Makefile. I try to port gdal 1.9.1 ___ 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: graphics/gdal 1.9.0 does not build on CURRENT
On 23.05.2012 18:22 (UTC+1), coder.tuxfamily wrote: OK, I think I get it. This failure does not happen, if swig is not installed. Then it builds and installs fine. Do you have any idea what is going wrong with swig here? OK. Maybe inclue the swig dependancy into the Makefile. I just tested three cases: (1) No swig installed -> gdal 1.9.0 builds and installs fine (2) swig 1.3.40 installed -> the build breaks, see older mails (3) swig 2.0.4 installed -> gdal 1.9.0 builds and installs fine So we only have to take care that swig 1.3.40 is not installed. With swig installed, the pkg-plist of gdal is incomplete, 'make deinstall' shows pkg_delete: unable to completely remove directory '/usr/local/share/gdal' pkg_delete: unable to completely remove directory '/usr/local/lib/python2.7/site-packages/GDAL-1.9.0-py2.7-freebsd-10.0-CURRENT-amd64.egg/osgeo' pkg_delete: unable to completely remove directory '/usr/local/lib/python2.7/site-packages/GDAL-1.9.0-py2.7-freebsd-10.0-CURRENT-amd64.egg' pkg_delete: couldn't entirely delete package `gdal-1.9.0' (perhaps the packing list is incorrectly specified?) I try to port gdal 1.9.1 That would be nice! ___ 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: Evince fails upgrade
On Wed, May 23, 2012 at 7:34 AM, Robert wrote: > > Hello Port readers > > I am unable to upgrade to latest evince due to following failure. > Evince now calls for www/yelp which calls for www/libxul which has > vulnerabilities. > > [robert@dell64] /usr/ports/x11/yelp% sudo make install clean > > yelp is using libxul for gecko support, but you can > change that by defining WITH_GECKO to the following values: > > libxul > > ===> License check disabled, port has not defined LICENSE > ===> Extracting for yelp-2.30.2_2 > => SHA256 Checksum OK for gnome2/yelp-2.30.2.tar.bz2. > /bin/rm -f /usr/ports/x11/yelp/work/yelp-2.30.2/data/yelp.schemas > ===> Patching for yelp-2.30.2_2 > ===> Applying FreeBSD patches for yelp-2.30.2_2 > ===> yelp-2.30.2_2 depends on file: /usr/local/lib/libxul/libxul.so - > not found ===> Verifying install for /usr/local/lib/libxul/libxul.so > in /usr/ports/www/libxul ===> libxul-1.9.2.28 has known > vulnerabilities: Affected package: libxul-1.9.2.28 > Type of problem: mozilla -- multiple vulnerabilities. > Reference: > http://portaudit.FreeBSD.org/380e8c56-8e32-11e1-9580-4061862b8c22.html > => Please update your ports tree and try again. *** Error code 1 > > Stop in /usr/ports/www/libxul. > *** Error code 1 > > Stop in /usr/ports/www/libxul. > *** Error code 1 > > Stop in /usr/ports/x11/yelp. > > I have tried to comment out the WITH_GECKO line but that fails also. > The Makefile already has > > WITH_GECKO= libxul > > What do I need to change it to? There is nothing to change it to, as far as I know. There used to other options, but libxul is the only one left. Unfortunately, it has a vulnerability, so won't build. You can either force it by setting DISABLE_VULNERABILITIES and live with the vulnerability or wait until libxul is fixed, assuming that it is. Other ports that use GECKO have the same problem. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.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"
Re: WITH_GCC
on 21/05/2012 05:54 Gerald Pfeifer said the following:
> On Wed, 16 May 2012, Andriy Gapon wrote:
+CFLAGS+= ${CFLAGS.${CC}}
+CXXFLAGS+=${CXXFLAGS.${CC}}
>>>
>>> Similarly here. Where does this come from, why is it related to
>>> the WITH_GCC versus USE_GCC patch? Can and should this be split
>>> out? How is it used and where? Where is it defined?
>>
>> This should be split out. The use case is to make it possible to set
>> something like the following in make.conf:
>>
>> CFLAGS.gcc46+= -fearlier-gcc-fails-with-this-flag-but-I-want-it-with-gcc46
>
> I see! The only question I have is whether, given there is also clang,
> this is really best suited for Mk/bsd.gcc.mk, or this should rather
> become part of the general Mk/bsd.port.mk?
I think so. My patch was intended to handle only different GCC versions, I made
it for my personal use :-)
Mark's patch on the other hand does a job of supporting different compilers too.
> To me it looks more like the latter, Mk/bsd.port.mk, but if not for
> some reason, please add a comment to the top of the file Mk/bsd.gcc.mk
> and commit this part.
No, no, thank you :-)
--
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"
