qca-ossl and bacula-client fail during compile
Hi, last weekend I ran a portmaster-update on my FreeBSD 8-STABLE Box (amd64). I thought it was a safe time to do so. Well, a few Ports failed (due to the OpenSSL-Update to 1.0.0?). I watched and searched this ports ML but didn't find these, so probably I did something wrong during the Update? Also, I didn't notice any Head-Up -- did I miss something? One is security/qca-ossl (qca-ossl-2.0.0-beta3), the other bacula-client (bacula-client-5.0.0). For the qca-ossl-Problem I found a Patch that with slight Modifications (due to a Patch applied by the Port) I was able to apply here: http://bugs.gentoo.org/show_bug.cgi?format=multipleid=313571 and compile qca-ossl. For the bacula-Problem I found a Thread initiated by Kern Sibbald re. these Problems: http://www.mail-archive.com/openssl-...@openssl.org/msg27223.html and there seems to be a more recent Version to be compatible with OpenSSL 1.0. Did I do something completely wrong? Or is this all still WIP? Or should I create Bug-Tickets for these problems (and maybe attach the patched patch for qca-ossl)? Cheers, _ralf_ Good, your configure finished. Now run /usr/local/bin/gmake. === Building for qca-ossl-2.0.0.b3_3 /usr/local/bin/moc-qt4 -DOSSL_097 -DQT_NO_DEBUG -DQT_PLUGIN -DQT_CORE_LIB -DQT_SHARED -I/usr/local/share/qt4/mkspecs/freebsd-g++ -I. -I/usr/local/include/qt4/QtCore -I/usr/local/include/qt4 -I/usr/local/include -I/usr/local/include/QtCrypto -I. -I/usr/local/include qca-ossl.cpp -o qca-ossl.moc g++ -c -pipe -O2 -Wall -W -fPIC -DOSSL_097 -DQT_NO_DEBUG -DQT_PLUGIN -DQT_CORE_LIB -DQT_SHARED -I/usr/local/share/qt4/mkspecs/freebsd-g++ -I. -I/usr/local/include/qt4/QtCore -I/usr/local/include/qt4 -I/usr/local/include -I/usr/local/include/QtCrypto -I. -I/usr/local/include -o qca-ossl.o qca-ossl.cpp qca-ossl.cpp: In function 'X509_EXTENSION* opensslQCAPlugin::new_subject_key_id(X509*)': qca-ossl.cpp:330: warning: deprecated conversion from string constant to 'char*' qca-ossl.cpp: In member function 'virtual void opensslQCAPlugin::RSAKey::startSign(QCA::SignatureAlgorithm, QCA::SignatureFormat)': qca-ossl.cpp:1775: error: 'EVP_md2' was not declared in this scope qca-ossl.cpp: In member function 'virtual void opensslQCAPlugin::RSAKey::startVerify(QCA::SignatureAlgorithm, QCA::SignatureFormat)': qca-ossl.cpp:1793: error: 'EVP_md2' was not declared in this scope qca-ossl.cpp: In member function 'virtual QCA::Provider::Context* opensslProvider::createContext(const QString)': qca-ossl.cpp:6794: error: 'EVP_md2' was not declared in this scope qca-ossl.cpp:6824: error: 'EVP_md2' was not declared in this scope *** Error code 1 Stop in /usr/ports/security/qca-ossl/work/qca-ossl-2.0.0-beta3. *** Error code 1 Stop in /usr/ports/security/qca-ossl. ==Entering directory /usr/ports/sysutils/bacula-client/work/bacula-5.0.0/src/lib Compiling attr.c Compiling base64.c Compiling berrno.c Compiling bsys.c Compiling bget_msg.c Compiling bnet.c Compiling bnet_server.c Compiling runscript.c Compiling bsock.c Compiling bpipe.c Compiling bsnprintf.c Compiling btime.c Compiling cram-md5.c Compiling crc32.c Compiling crypto.c crypto.c: In function 'ASN1_OCTET_STRING* openssl_cert_keyid(X509*)': crypto.c:333: error: invalid conversion from 'const X509V3_EXT_METHOD*' to 'X509V3_EXT_METHOD*' crypto.c: In function 'CRYPTO_SESSION* crypto_session_new(crypto_cipher_t, alist*)': crypto.c:1102: error: cannot convert 'unsigned char*' to 'EVP_PKEY_CTX*' for argument '1' to 'int EVP_PKEY_encrypt(EVP_PKEY_CTX*, unsigned char*, size_t*, const unsigned char*, size_t)' crypto.c: In function 'crypto_error_t crypto_session_decode(const u_int8_t*, u_int32_t, alist*, CRYPTO_SESSION**)': crypto.c:1226: error: cannot convert 'unsigned char*' to 'EVP_PKEY_CTX*' for argument '1' to 'int EVP_PKEY_decrypt(EVP_PKEY_CTX*, unsigned char*, size_t*, const unsigned char*, size_t)' *** Error code 1 Stop in /usr/ports/sysutils/bacula-client/work/bacula-5.0.0/src/lib. == Error in /usr/ports/sysutils/bacula-client/work/bacula-5.0.0/src/lib == *** Error code 1 Stop in /usr/ports/sysutils/bacula-client/work/bacula-5.0.0. *** Error code 1 Stop in /usr/ports/sysutils/bacula-client. *** Error code 1 Stop in /usr/ports/sysutils/bacula-client. ___ 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: New FreeBSD ports system - bachelors work
On Fri, 30 Apr 2010 10:10:44 +0100, Anton Shterenlikht me...@bristol.ac.uk wrote: On Thu, Apr 29, 2010 at 08:08:26PM +0300, Aldis Berjoza wrote: Hello! Some time ago I've read, that FreeBSD might be interested to move ports tree to database (sqlite?). This would require rewriting of all existing and writing some new tools related to ports. I'm IT student and next year I have to write bachelor work. As active FreeBSD user, I am very interested in supporting FreeBSD, and, if FreeBSD developers, think that such ports reimplementation would benefit FreeBSD community, I'd be willing to develop new system. If you have other ideas, how to improve FreeBSD ports please let me know. Currently this is just an idea, but I'm also open to other suggestions/ideas. Aldis, I've a much more interesting, ambitious and challenging proposal - FreeBSD ia64! The FreeBSD ia64 port has the potential to be the FreeBSD HPC solution. But we are not there yet. Despite being able to run the latest -current with zfs, SMP and other latest features and successfully building 17559 ports, FreeBSD ia64 desperately needs motivated and skilled programmers to work on: - kernel debugging: the port suffers from spontaneous reboots under heavy load - building llvm on ia64: http://llvm-ia64.svn.sourceforge.net/viewvc/llvm-ia64/ - building gcc44 and 45 on ia64: these ports don't build at present, and there are lots of other very useful ports which depend on gcc44 (or 45). - optimisation: very little work has been done on this on ia64 so far. Work is needed on compiler flags, optimisation of low level (assembly) routines, SMP and zfs performance. See also this list of things to do: http://www.freebsd.org/platforms/ia64/todo.html YOu can check which ports need work here: http://pointyhat.freebsd.org/errorlogs/packagestats.html In particular, this page lists ports which failed to build: http://pointyhat.freebsd.org/errorlogs/ia64-8-latest/ If you look at Aff. (affected) field, you can pick ports which affect lots of other ports. Then, of course, there are ports which we aren't even building on ia64 portcluster: http://pointyhat.freebsd.org/errorlogs/ia64-8-latest/duds.verbose Any work on these is very helpful. yours anton Unfortunately I don't have any ia64 pc's to work with. Running QEMU on my P4 would take ages -- BSDroot.lv -- coming soon ___ 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: New FreeBSD ports system - bachelors work
On Fri, 30 Apr 2010 10:36:24 +0100, Anton Shterenlikht me...@bristol.ac.uk wrote: On Fri, Apr 30, 2010 at 12:29:55PM +0300, Aldis Berjoza wrote: Unfortunately I don't have any ia64 pc's to work with. Running QEMU on my P4 would take ages This can be arranged. I can provide you with a remote access to HP rx2600 or rx2620, both running 9.0 -current. anton Thanks for suggestion/idea, I'll think about it P.S. Sorry, I'm not really used to mailing list and sometimes forget to add freebsd-ports@ to Cc -- BSDroot.lv -- coming soon ___ 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 Port: ja-lynx-2.8.7.dev9
___ 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: www/moinmoin: fix a bug while pkg_delete
On Fri, Apr 30, 2010 at 09:34:43AM +0800, khsing wrote: I have submitted a patch to fix a bug while pkg_delete. Please take it in. http://www.freebsd.org/cgi/query-pr.cgi?pr=146142 I will be committing this shortly. Thanks for addressing the problem. In the future, you only need to mail this list if a PR sits with no forward progress for a significant part of time. Usually significant is defined as 2 weeks. There are cases where it is less than that though. -- WXS ___ 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: portupgrading lang/gawk fails
Torfinn Ingolfsen wrote on 2010-04-28: Hi, On Mon, Apr 26, 2010 at 8:29 PM, Doug Barton do...@freebsd.org wrote: On 04/26/10 11:15, Torfinn Ingolfsen wrote: Hi, When trying 'portupgrade -R gawk' I get this: There is a problem with the port that if you do: install gawk ; build gawk ; deinstall gawk ; install gawk it will fail. See http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/146005 Aha. Hopefully the problem will be fixed soon. I have committed a fix, with krion's consent (but mirrors or portsnap servers may still need to pick it up before you can have it, which is outside my control). Details on the issue and the fix in http://www.freebsd.org/cgi/query-pr.cgi?pr=146152 -- Matthias Andree ___ 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 Port: xmonad-0.9.1_1
Dear xmonad maintainers, I just noticed that with the latest port tree upgrade (as of today), even when force-rebuilding all the ports dependent on libgmp (after its recent update detailed in /usr/ports/UPDATING), xmonad crashes on startup with the following error message: /libexec/ld-elf.so.1: Shared object libgmp.so.8 not found, required by xmonad -x86_64-freebsd which seems to indicate that the xmonad dependency on libgmp was not updated in the port's files to follow the recent libgmp bump. I was able to make it work anyway with: ln -s /usr/local/lib/libgmp.so.10 /usr/local/lib/libgmp.so.8 but I wanted to signal the issue. very best, giuseppe PS: I am running FreeBSD 8.0-RELEASE-p2 / amd64 ___ 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 Port: mysql-server-5.1.45
Hello, Ale! When you make the port of mysql-server-5.1.46 and mysql-client .46 version ? -- WBR mailto:ad...@yeh.ru ___ 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: FreeBSD Port: xmonad-0.9.1_1
On 2010-04-30 19:39:44, Giuseppe Pagnoni wrote: xmonad crashes on startup with the following error message: /libexec/ld-elf.so.1: Shared object libgmp.so.8 not found, required by xmonad -x86_64-freebsd This might have something to do with the way that xmonad recompiles itself and saves a copy of the binary in your $HOME. Have a look in ~/.xmonad, I think... M ___ 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
[HEADS UP] Xorg 7.5 merge comming tomorrow.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy Guys, First of all I apologize for the long waiting time for Xorg 7.5 Now the facts. Xorg 7.5 is completely finished last issues were fixed by fluffy@, and the exp-run was also fine, I expect the merge of xorg 7.5 tomorrow evening UTC. I think the KDE team and the GNOME team will their ports after the Xorg update. So i think you should monitor the CVS commits, ports and x11 mailing list to make sure you don't report a duplicat problems (if we get some). - - Martin - -- \ || / ( * * ) +-oOO--(_)--OOo-+ | PGP: 0xB1E6FCE9 | | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkvbIukACgkQdLJIhLHm/OnRugCfYBFzjFjEEPbuFNJLMrr/SXRZ RtwAoKr8acvoGoZpH2K3dmICjR8MSnQY =jhDN -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: [HEADS UP] Xorg 7.5 merge comming tomorrow.
2010/4/30 Martin Wilke m...@freebsd.org: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy Guys, First of all I apologize for the long waiting time for Xorg 7.5 Now the facts. Xorg 7.5 is completely finished last issues were fixed by fluffy@, and the exp-run was also fine, I expect the merge of xorg 7.5 tomorrow evening UTC. I think the KDE team and the GNOME team will their ports after the Xorg update. So i think you should monitor the CVS commits, ports and x11 mailing list to make sure you don't report a duplicat problems (if we get some). - - Martin - -- \ || / ( * * ) +-oOO--(_)--OOo-+ | PGP : 0xB1E6FCE9 | | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkvbIukACgkQdLJIhLHm/OnRugCfYBFzjFjEEPbuFNJLMrr/SXRZ RtwAoKr8acvoGoZpH2K3dmICjR8MSnQY =jhDN -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 Congratulations! -- Regards, Sylvio Cesar || FreeBSD Committer || Team multime...@freebsd.org syl...@freebsd.org || http://people.freebsd.org/~sylvio || http://www.scjamorim.org || http://www.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
Attn.: users of devel/distorm and devel/py-distorm -- update to distorm3?
I was planning to update the devel/distorm and devel/py-distorm ports to the new distorm3: https://code.google.com/p/distorm/ The new version has added functionality, and is said to be backwards-compatible with the older version, but the new version is licensed under GPLv3, rather than BSD. Does anyone have any objections to such an update? If not, I'll go ahead and update soon. Otherwise, depending upon the nature of the feedback, I'll consider making a separate port for the newer version. Regards, b. ___ 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: FreeBSD Port: xmonad-0.9.1_1
On 04/30/10 19:39, Giuseppe Pagnoni wrote: xmonad crashes on startup with the following error message: /libexec/ld-elf.so.1: Shared object libgmp.so.8 not found, required by xmonad -x86_64-freebsd [..] the xmonad dependency on libgmp was not updated in the port's files to follow the recent libgmp bump. It was updated, just check it out at the right place [1]. On 04/30/10 20:29, freebsd-po...@coreland.ath.cx wrote: This might have something to do with the way that xmonad recompiles itself and saves a copy of the binary in your $HOME. Have a look in ~/.xmonad, I think... Yes, that makes sense I think. What happens if you simply remove the xmonad binary in ~/.xmonad? Cheers, :g [1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-wm/xmonad/Makefile.diff?r1=1.14;r2=1.15 ___ 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: [HEADS UP] Xorg 7.5 merge comming tomorrow.
On Fri, Apr 30, 2010 at 8:35 PM, Martin Wilke m...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy Guys, First of all I apologize for the long waiting time for Xorg 7.5 Now the facts. Xorg 7.5 is completely finished last issues were fixed by fluffy@, and the exp-run was also fine, I expect the merge of xorg 7.5 tomorrow evening UTC. I think the KDE team and the GNOME team will their ports after the Xorg update. So i think you should monitor the CVS commits, ports and x11 mailing list to make sure you don't report a duplicat problems (if we get some). Awesome work, all of you involved! Can't wait for it to hit the tree. //Niclas ___ 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
python can't make package.
Hi freebsd-ports, This morning I wasn't able to make package in lang/python26 port. === Building package for python26-2.6.4 Creating package /usr/ports/packages/All/python26-2.6.4.tbz Registering depends:. Creating bzip'd tar ball in '/usr/ports/packages/All/python26-2.6.4.tbz' tar: lib/python2.6/lib-dynload/_multiprocessing.so: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 *** Error code 1 Stop in /usr/ports/lang/python26. *** Error code 1 Stop in /usr/ports/lang/python26. Is it a broken PLIST issue? 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: python can't make package.
On Fri, Apr 30, 2010 at 3:08 PM, David DEMELIER demelier.da...@gmail.com wrote: Hi freebsd-ports, This morning I wasn't able to make package in lang/python26 port. === Building package for python26-2.6.4 Creating package /usr/ports/packages/All/python26-2.6.4.tbz Registering depends:. Creating bzip'd tar ball in '/usr/ports/packages/All/python26-2.6.4.tbz' tar: lib/python2.6/lib-dynload/_multiprocessing.so: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 *** Error code 1 Stop in /usr/ports/lang/python26. *** Error code 1 Stop in /usr/ports/lang/python26. Is it a broken PLIST issue? It's a known issue I (and others) informed miwi@ about (I provided him with a patch). It's because you're not disabling the threads functionality in python. HTH, -Garrett ___ 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: ports and PBIs
On Sunday, April 11, 2010, Tim Kientzle kient...@freebsd.org wrote: Garrett Cooper wrote: If I'm understanding you correctly you're saying it's an issue when I do: pkg_add A B C # 1 year passes pkg_add D # D depends on A, B, C, of different revisions. pkg_add barfs because it can't find the applications, etc. This is something that's been hashed over a number of times (a few of which I've participated in in #bsdports). There needs to be a simple update command which will handle the action of upgrading packages, because there isn't a proper command that will do so today. I'm not convinced that the simple update command you mention is actually feasible, much less desirable. (If I want to try out the new Firefox, why does that imply that my year-old Gimp has to be upgraded?) As for feasibility, here's the easy problem: A2.7 requires B3.6 ... one year passes ... A4.8 now requires B7.2 But A4.8 is incompatible with B3.6 and A2.7 is incompatible with B7.2. So neither A nor B can be updated separately without breaking the system. Here's the hard problem: A2.7 requires B3.6 ... one year passes ... I want to install C1.0 which requires B7.2 but there hasn't been a new release of A that works with B7.2. So I now simply cannot have both C1.0 and A2.7 installed at the same time because they require different versions of B. PBI avoids both of these problems. It may be unsuitable for embedded systems[1], but I see no reason we should not extend the existing ports/packages system with additional tools that target certain use cases, and PBI seems a good fit for the desktop case. Tim Genuine (possibly stupid) question -in PBI land, what happens if package B is, say, CUPS? Does one need versioned rc.d scripts to start one or the other? Which one gets to claim port 631? -James Butler [1] Actually, PBI might work just fine even for embedded if we address the disk bloat issue. One approach would be to make /Package/Bar/libfoo-2.8.7.so a symlink or hardlink to /Package/Shared/libfoo-2.8.7.so-MD5-hash This gives easy sharing of identical files. It's even easy to handle at install time: * Installer writes libfoo-2.8.7.so to /Package/Shared/libfoo-2.8.7.so-temp-PID of installer * Installer computes hash of file as it's written * Installer renames file (delete if rename fails with EEXIST) * Installer writes symlink or hardlink into /Package/Bar ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-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
OpenSSL 1.0.0 Gotcha - Certificate Hashes are Different
I just spent quite a while trying to figure out what broke SSL certificate verification in my irc client after taking some brave pills and updating ports on my notebook. It turns out that OpenSSL 1.0.0 hashes certificates differently to earlier versions. That meant that applications looking in my /usr/local/openssl/certs directory couldn't find hashes for CA certificates because the hash links had been created with OpenSSL 0.9.8. From the CHANGES file in the root of the OpenSSL 1.0.0 distribution: Enhance the hash format used for certificate directory links. The new form uses the canonical encoding (meaning equivalent names will work even if they aren't identical) and uses SHA1 instead of MD5. This form is incompatible with the older format and as a result c_rehash should be used to rebuild symbolic links. [Steve Henson] So, that's good to know but here's the really fun bit. Just running c_rehash won't fix it if you have openssl in the base system - because it picks up /usr/bin/openssl (old version, old hashes). The /usr/local/bin/c_rehash script relies on an environment variable to point it at anything other than the base openssl. So, if I set OPENSSL=/usr/local/bin/openssl in the environment and then run c_rehash, I get the new hashes and stuff works again. -- John Marshall pgpk7DyiGMLzY.pgp Description: PGP signature
