security/libgcrypt Following UPDATING 20090107 Build failure
uname -a FreeBSD dns1.vizion2000.net 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Thu Aug 20 12:54:34 BST 2009 da...@dns1.vizion2000.net:/usr/obj/usr/src/sys/GENERIC amd64 [Intel quad core system] 20090107: AFFECTS: users of security/libgcrypt AUTHOR: ra...@freebsd.org libgcrypt has been upgraded to 1.4.3 which has a shared library version bump. You need to reinstall all ports depending on it. Use something like this: portupgrade -rf libgcrypt Multiple ports fail to upgrade following the failure of this build. Thanks in advance for any advice David Script records: dns1# portupgrade -rf libgcrypt ---> Reinstalling 'libgcrypt-1.4.4' (security/libgcrypt) ---> Building '/usr/ports/security/libgcrypt' ===> Cleaning for libgcrypt-1.4.4 ===> Extracting for libgcrypt-1.4.4 => MD5 Checksum OK for libgcrypt-1.4.4.tar.bz2. => SHA256 Checksum OK for libgcrypt-1.4.4.tar.bz2. ===> Patching for libgcrypt-1.4.4 ===> Applying FreeBSD patches for libgcrypt-1.4.4 ===> libgcrypt-1.4.4 depends on package: libtool>=2.2 - found ===> libgcrypt-1.4.4 depends on shared library: gpg-error.0 - found ===> Configuring for libgcrypt-1.4.4 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 make sets $(MAKE)... yes checking build system type... amd64-portbld-freebsd7.2 checking host system type... amd64-portbld-freebsd7.2 checking whether to enable maintainer-specific portions of Makefiles... no checking whether make sets $(MAKE)... (cached) yes checking for gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... 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 for style of include used by make... GNU checking dependency style of cc... gcc3 checking how to run the C preprocessor... cc -E checking whether cc understands -c and -o together... yes checking dependency style of cc... gcc3 checking for library containing strerror... none required checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for gawk... (cached) gawk checking for windres... no 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 ld used by cc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all 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 dlfcn.h us
security/libgcrypt Following UPDATING 20090107 Build failure
uname -a FreeBSD dns1.vizion2000.net 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Thu Aug 20 12:54:34 BST 2009 da...@dns1.vizion2000.net:/usr/obj/usr/src/sys/GENERIC amd64 [Intel quad core system] 20090107: AFFECTS: users of security/libgcrypt AUTHOR: ra...@freebsd.org libgcrypt has been upgraded to 1.4.3 which has a shared library version bump. You need to reinstall all ports depending on it. Use something like this: portupgrade -rf libgcrypt Multiple ports fail to upgrade following the failure of this build. Thanks in advance for any advice David Script records: dns1# portupgrade -rf libgcrypt ---> Reinstalling 'libgcrypt-1.4.4' (security/libgcrypt) ---> Building '/usr/ports/security/libgcrypt' ===> Cleaning for libgcrypt-1.4.4 ===> Extracting for libgcrypt-1.4.4 => MD5 Checksum OK for libgcrypt-1.4.4.tar.bz2. => SHA256 Checksum OK for libgcrypt-1.4.4.tar.bz2. ===> Patching for libgcrypt-1.4.4 ===> Applying FreeBSD patches for libgcrypt-1.4.4 ===> libgcrypt-1.4.4 depends on package: libtool>=2.2 - found ===> libgcrypt-1.4.4 depends on shared library: gpg-error.0 - found ===> Configuring for libgcrypt-1.4.4 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 make sets $(MAKE)... yes checking build system type... amd64-portbld-freebsd7.2 checking host system type... amd64-portbld-freebsd7.2 checking whether to enable maintainer-specific portions of Makefiles... no checking whether make sets $(MAKE)... (cached) yes checking for gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... 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 for style of include used by make... GNU checking dependency style of cc... gcc3 checking how to run the C preprocessor... cc -E checking whether cc understands -c and -o together... yes checking dependency style of cc... gcc3 checking for library containing strerror... none required checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for gawk... (cached) gawk checking for windres... no 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 ld used by cc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all 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 dlfcn.h us
security/libgcrypt Following UPDATING 20090107 Build failure
uname -a FreeBSD dns1.vizion2000.net 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Thu Aug 20 12:54:34 BST 2009 da...@dns1.vizion2000.net:/usr/obj/usr/src/sys/GENERIC amd64 [Intel quad core system] 20090107: AFFECTS: users of security/libgcrypt AUTHOR: ra...@freebsd.org libgcrypt has been upgraded to 1.4.3 which has a shared library version bump. You need to reinstall all ports depending on it. Use something like this: portupgrade -rf libgcrypt Multiple ports fail to upgrade following the failure of this build. Thanks in advance for any advice David Script records: dns1# portupgrade -rf libgcrypt ---> Reinstalling 'libgcrypt-1.4.4' (security/libgcrypt) ---> Building '/usr/ports/security/libgcrypt' ===> Cleaning for libgcrypt-1.4.4 ===> Extracting for libgcrypt-1.4.4 => MD5 Checksum OK for libgcrypt-1.4.4.tar.bz2. => SHA256 Checksum OK for libgcrypt-1.4.4.tar.bz2. ===> Patching for libgcrypt-1.4.4 ===> Applying FreeBSD patches for libgcrypt-1.4.4 ===> libgcrypt-1.4.4 depends on package: libtool>=2.2 - found ===> libgcrypt-1.4.4 depends on shared library: gpg-error.0 - found ===> Configuring for libgcrypt-1.4.4 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 make sets $(MAKE)... yes checking build system type... amd64-portbld-freebsd7.2 checking host system type... amd64-portbld-freebsd7.2 checking whether to enable maintainer-specific portions of Makefiles... no checking whether make sets $(MAKE)... (cached) yes checking for gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... 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 for style of include used by make... GNU checking dependency style of cc... gcc3 checking how to run the C preprocessor... cc -E checking whether cc understands -c and -o together... yes checking dependency style of cc... gcc3 checking for library containing strerror... none required checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for gawk... (cached) gawk checking for windres... no 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 ld used by cc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all 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 dlfcn.h us
Re: security/libgcrypt Following UPDATING 20090107 Build failure
On Wed, Sep 23, 2009 at 12:00:01PM +0100, David Southwell wrote: > ../src/gcrypt.h:29:23: error: gpg-error.h: No such file or directory > > > In file included from ../src/visibility.h:243, > > > from ../src/g10lib.h:39, > > > from ../src/mpi.h:37, > > > from mpi-internal.h:52, > > > from mpi-add.c:31: > > something wrong with your libgpg-error installation. Try reinstalling it. Regards, Rong-En Fan ___ 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: security/libgcrypt Following UPDATING 20090107 Build failure
> On Wed, Sep 23, 2009 at 12:00:01PM +0100, David Southwell wrote: > > ../src/gcrypt.h:29:23: error: gpg-error.h: No such file or directory > > In file included from ../src/visibility.h:243, > > from ../src/g10lib.h:39, > > from ../src/mpi.h:37, > > from mpi-internal.h:52, > > from mpi-add.c:31: > > something wrong with your libgpg-error installation. Try reinstalling > it. > > Regards, > Rong-En Fan > > Thank Rong-En Right on the button It looks to me as though libpg-error could be a dependency of libgcrypt 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: security/libgcrypt Following UPDATING 20090107 Build failure
On Wed, Sep 23, 2009 at 05:41:34PM +0100, David Southwell wrote: > > On Wed, Sep 23, 2009 at 12:00:01PM +0100, David Southwell wrote: > > > ../src/gcrypt.h:29:23: error: gpg-error.h: No such file or directory > > > In file included from ../src/visibility.h:243, > > > from ../src/g10lib.h:39, > > > from ../src/mpi.h:37, > > > from mpi-internal.h:52, > > > from mpi-add.c:31: > > > > something wrong with your libgpg-error installation. Try reinstalling > > it. > > > > Regards, > > Rong-En Fan > > > > Thank Rong-En > Right on the button > It looks to me as though libpg-error could be a dependency of libgcrypt Errr, but it is, and it has been ever since May 2004... G'luck, Peter -- Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 I am the thought you are now thinking. pgpnGz1x51D4s.pgp Description: PGP signature
