Re: gvfs-1.6.6' build failure
Deleting xz-5.0.0 and installing lzma-9.12 fixed this problem. Sorry for the noise, but a heads up if anyone else hits this issue. On 11/24/10 13:54, Jimmie James wrote: FreeBSD jimmiejaz.org 8.1-STABLE FreeBSD 8.1-STABLE #0: Mon Nov 15 17:52:21 EST 2010 root@:/usr/obj/usr/src/sys/FORTYTWO i386 Hit this in the middle of the Gnome 2.32, I hit this error, any suggestions? /usr/lib/libarchive.so: undefined reference to `lzma_stream_enco...@xz_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_alone_deco...@xz_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_memus...@xz_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_stream_deco...@xz_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_c...@xz_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_...@xz_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_lzma_pre...@xz_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_alone_enco...@xz_5.0' gmake[4]: *** [gvfsd-archive] Error 1 Stop in /usr/ports/devel/gvfs. *** Error code 1 Stop in /usr/ports/devel/gvfs. ___ 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"
devel/p4d x2 Makefile error.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attached is a patch that fixes up the Makefile if you happen to be using
a different WRKDIRPREFIX than the default of ${.CURDIR}.
Currently the Makefile assumes that pkg-message is in the object
directory which obviously it would not be unless copied. So a cat(1) of
that results in installation being aborted.
Regards,
- --
jhell,v
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJM7gMtAAoJEJBXh4mJ2FR+zTEH/05XY2axBzCeJQPExRxf4lsF
aa13tNIH8GoTs7ZCndaajtVTUx5h31E/LE4LqmwW3eQ6i0cWgUkG6jbrnyhRNUgg
f287i2LdaYrp0DF2aZ6n5FlQLs4ogh3o20PXJAOyhQ8is4efcN/AI71xdAHw/ncg
gRlpuJke/8pe8lFWtYH5Z8gOam07u4su1tDDV3DvTVszE082h/017AX/MLAfufIP
QEE8tFyFjdDxAzyh7Hg3BduXebp3Espx36MurN6rL0jEbDdjKd5QIfPL0EzSHsrD
Z1zXca7CJd6coVwgO5gsyX9CzAZfCMoOEWSiHTPwoOPPpPVEzb/VEpjx3z+UqrY=
=TmfB
-END PGP SIGNATURE-
--- Makefile.orig 2010-11-25 01:23:32.753968347 -0500
+++ Makefile2010-11-25 01:25:11.503421041 -0500
@@ -49,7 +49,7 @@
${INSTALL_PROGRAM} ${_DISTDIR}/p4d ${PREFIX}/sbin/
post-install:
- @${CAT} pkg-message
+ @${CAT} ${.CURDIR}/pkg-message
${MKDIR} ${DESTDIR}${P4ROOT}
${CHOWN} p4admin:p4admin ${DESTDIR}${P4ROOT}
${CHMOD} 750 ${DESTDIR}${P4ROOT}
-BEGIN PGP SIGNATURE-
iQEcBAABAgAGBQJM7gMuAAoJEJBXh4mJ2FR+ev8H/iN/9BUaWAyPcRLV16fnHD61
5NBwElPSYdt+rWHxNTnl+1AZSOVO5VC0lKkHB2230JMvFdMCycaR87AgU6BmLFJd
Pi/xYx4rR5G7OqVNTyT5DChpZdAcoQReYlPXsrkMTSZmDcFnBo8ktV+cj+7B5klo
ebVUAmi6E33Vv1S5APU3/U7S55gmsZSe+4XrdQHiC312gnYX/XLSlbyx3mFkqpyA
dWID1quxIBh2dDf7I6/jLEm/wzhVa3cTsctMp3tdozZGO6zM07myHLMw9Tw/kIuF
JcmMDzZZV4s7dgaMtLQ0LZd2yLFnOaPQ2+Q7604YVOiC7odtyEQIynsT4BaIWZg=
=wOo9
-END PGP SIGNATURE-
___
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: mercurial broken
2010/11/24 Christer Solskogen : > On Wed, Nov 24, 2010 at 9:30 PM, David DEMELIER > wrote: >> Hello >> >> after an upgrade to 1.7.1, I can't use mercurial anymore : >> >> mark...@melon ~/devel/dotfiles $ hg pull >> abort: No module named thread! >> Exception AttributeError: "'httpsrepository' object has no attribute >> 'urlopener'" in > > ignored >> >> what is happening ? >> > > Dont know about you, but it works fine here: > $ hg --version > Mercurial Distributed SCM (version 1.7.1) > (see http://mercurial.selenic.com for more information) > > Copyright (C) 2005-2010 Matt Mackall and others > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > $ uname -a > FreeBSD shine 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #0: Sat Nov 13 > 13:09:55 CET 2010 r...@shine:/usr/obj/usr/src/sys/SHINE amd64 > > I also tried cloning from https (and pulling) - No error. > > -- > chs, > Yes it seems to be python, the port was missing THREADS options. Sorry for the noise. Cheers, -- Demelier David ___ 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: mercurial broken
On Wed, Nov 24, 2010 at 9:30 PM, David DEMELIER wrote: > Hello > > after an upgrade to 1.7.1, I can't use mercurial anymore : > > mark...@melon ~/devel/dotfiles $ hg pull > abort: No module named thread! > Exception AttributeError: "'httpsrepository' object has no attribute > 'urlopener'" in > ignored > > what is happening ? > Dont know about you, but it works fine here: $ hg --version Mercurial Distributed SCM (version 1.7.1) (see http://mercurial.selenic.com for more information) Copyright (C) 2005-2010 Matt Mackall and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ uname -a FreeBSD shine 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #0: Sat Nov 13 13:09:55 CET 2010 r...@shine:/usr/obj/usr/src/sys/SHINE amd64 I also tried cloning from https (and pulling) - No error. -- chs, ___ 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"
mercurial broken
Hello after an upgrade to 1.7.1, I can't use mercurial anymore : mark...@melon ~/devel/dotfiles $ hg pull abort: No module named thread! Exception AttributeError: "'httpsrepository' object has no attribute 'urlopener'" in > ignored what is happening ? Kind regards, -- Demelier David ___ 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"
gvfs-1.6.6' build failure
FreeBSD jimmiejaz.org 8.1-STABLE FreeBSD 8.1-STABLE #0: Mon Nov 15 17:52:21 EST 2010 root@:/usr/obj/usr/src/sys/FORTYTWO i386 Hit this in the middle of the Gnome 2.32, I hit this error, any suggestions? [13:44:20] jim...@jimmiejaz <115> [0] /usr/ports/devel/gvfs#make clean ; rehash ; portupgrade -f devel/gvfs ===> Cleaning for gvfs-1.6.6 ---> Upgrading 'gvfs-1.6.3_1' to 'gvfs-1.6.6' (devel/gvfs) ---> Building '/usr/ports/devel/gvfs' ===> Cleaning for gvfs-1.6.6 ===> License check disabled, port has not defined LICENSE ===> Found saved configuration for gvfs-0.2.3_2 ===> Extracting for gvfs-1.6.6 => SHA256 Checksum OK for gnome2/gvfs-1.6.6.tar.bz2. ===> Patching for gvfs-1.6.6 ===> Applying FreeBSD patches for gvfs-1.6.6 ===> gvfs-1.6.6 depends on executable: gmake - found ===> gvfs-1.6.6 depends on file: /usr/local/bin/intltool-extract - found ===> gvfs-1.6.6 depends on executable: pkg-config - found ===> gvfs-1.6.6 depends on shared library: dbus-1.3 - found ===> gvfs-1.6.6 depends on shared library: hal.1 - found ===> gvfs-1.6.6 depends on shared library: soup-gnome-2.4.1 - found ===> gvfs-1.6.6 depends on shared library: gnome-keyring - found ===> gvfs-1.6.6 depends on shared library: avahi-client.3 - found ===> gvfs-1.6.6 depends on shared library: intl - found ===> gvfs-1.6.6 depends on shared library: atk-1.0.0 - found ===> gvfs-1.6.6 depends on shared library: gconf-2.4 - found ===> gvfs-1.6.6 depends on shared library: glib-2.0.0 - found ===> gvfs-1.6.6 depends on shared library: gtk-x11-2.0.0 - found ===> gvfs-1.6.6 depends on shared library: IDL-2.0 - found ===> gvfs-1.6.6 depends on shared library: xml2.5 - found ===> gvfs-1.6.6 depends on shared library: ORBit-2.0 - found ===> gvfs-1.6.6 depends on shared library: pango-1.0.0 - found ===> Configuring for gvfs-1.6.6 configure: WARNING: unrecognized options: --with-gconf-source checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/local/bin/gmkdir -p checking for gawk... gawk checking whether gmake sets $(MAKE)... yes checking whether build environment is sane... yes checking for style of include used by gmake... GNU checking for gcc... cc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking dependency style of cc... gcc3 checking for an ANSI C-conforming const... yes checking for library containing strerror... none required checking for gcc... (cached) cc checking whether we are using the GNU C compiler... (cached) yes checking whether cc accepts -g... (cached) yes checking for cc option to accept ISO C89... (cached) none needed checking dependency style of cc... (cached) gcc3 checking how to run the C preprocessor... cpp checking whether ln -s works... yes checking whether gmake sets $(MAKE)... (cached) yes checking build system type... i386-portbld-freebsd8.1 checking host system type... i386-portbld-freebsd8.1 checking how to print strings... print: not found printf checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by cc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking the maximum length of command line arguments... (cached) 262144 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... no checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from cc object... ok checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if cc supports -fno-rtti -fno-exceptions... no checking for cc option to produce PIC... -fPIC -DPIC checking if cc PIC flag -fPIC -DPIC works... yes checking if cc static flag -static works... yes checking if cc supports -c -o file.o... yes checking if cc supports -c -o file.o... (cached) yes checking whe
Re: ImageMagick upgrade problem
> I just committed a fix that a) worked for me, and b) I think is fairly > robust, and even a candidate for being the right thing to do. > > Please give it a try, and let us know if it does or does not work for you. > > > Doug Thank you Doug It works for me! ImageMagick plus DougMagick = FreeBSDMagick David Photographic Artist Permanent Installations & Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography & Official Portraiture Combined darkroom & digital creations & Systems Adminstrator for the vizion2000.net network ___ 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: Renaming a shared library in the port-framework to match FreeBSD naming schemes?
On 11/24/10 02:58, Andrew W. Nosenko wrote: On Tue, Nov 23, 2010 at 03:42, O. Hartmann wrote: On 11/23/10 02:14, Andrew W. Nosenko wrote: On Mon, Nov 22, 2010 at 22:20, O. Hartmann wrote: But there lives another problem: Xerces people doesn't expect parallel installation of the "evelopment" part of Xerces-C (headers, pkg-config, etc). At least it seems so by listing the libxerces-c package from Ubuntu. I guess so, but some ports of the FreeBSD ports (i.e. textproc/xalan-c) want xerces-c2 (which is 2.7.0). I try build xalan-c with the new xerces-c3 and see if it can handle the new header and libraries. I see three variants: (1) simple: just mark these ports (c2 and c3) as conflicting, ... in my testcase I did. And, for my personal taste, it is the best option. Be close to upstream as much as possible, IMHO, is the best way. (2) semi-simple: split each xerces-c port at the two: run-time and development. Runtime contains a shered library, development contains anything other. Mark development parts as conflictitng. ... well, in such a case we converge much to the weird Linux mess, I guess. (3) move each port away from each other's way: move headers into own versioned deirectory (e.g. from include/xercesc/ to insclude/xercesc-3.1/xercesc/), drop libxerces-c.so (if any -- I don't know), rename pkg-config (.pc) file, and static library (if any), may be something yet another, like documentation -- need to look at the actual install. All these changes hidden from the users through pkg-config's .pc, therefore only one problem for developers will be changed (non-standard name of the .pc file, i.e. pkg-config's module). ... this would bring up other complications for ports expecting libs and headers at places where the solo installation normally resides. But ATM I see no better way to allow parallel installation of the packages that aren't intended for parallel installation by theirs authors... I tend to install it as a unique port with conflicts activated. Hope there are no further conflicts other than xalan-c. And I have some feelings that either existing xalan-c able to compile against current xerces-c or there is newer version that able. I tried to build xalan-c against xerces-c 3.1.1 and it doesn't work. The Apache website for Xalan explicitely says that Xalan-c 1.X is for Xerces-c 2.7. And I did not figure out where they'he hide a newer version compatible to the new Xerces-C 3.1.1. Also, ports graphics/visionworkbench, graphics/gdal, graphics/osg (Openscene Graph) also depend on Xerces-c 2.7, as far as I see. That leaeves me with the option of having a additional port xerces-c3 separated from the other xerces-c2. This is messy ... ___ 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"
