[Fink-users] Troubles making ruby18
Dear all, I'm trying to compile ruby18 against on Mac OS X 10.5.6 (9G55) uname -r gives: Darwin macbook-pro-di-alessio-sarti.local 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386 The error I get comes up when trying to make openssl related libs, and is appended below... Am I missing something stupid? Cheers, alessio cc -dynamic -bundle -L/sw/src/fink.build/ruby18-1.8.1-2/ruby-1.8.1 -L/sw/lib -o openssl.bundle openssl_missing.o ossl.o ossl_asn1.o ossl_bio.o ossl_bn.o ossl_cipher.o ossl_config.o ossl_digest.o ossl_engine.o ossl_hmac.o ossl_ns_spki.o ossl_ocsp.o ossl_pkcs12.o ossl_pkcs7.o ossl_pkey.o ossl_pkey_dh.o ossl_pkey_dsa.o ossl_pkey_rsa.o ossl_rand.o ossl_ssl.o ossl_x509.o ossl_x509attr.o ossl_x509cert.o ossl_x509crl.o ossl_x509ext.o ossl_x509name.o ossl_x509req.o ossl_x509revoked.o ossl_x509store.o -lruby -lssl -lcrypto -ldl -lobjc Undefined symbols: _ENGINE_load_chil, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_atalla, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_aep, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_ubsec, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_4758cca, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_nuron, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_sureware, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_cswift, referenced from: _ossl_engine_s_load in ossl_engine.o ld: symbol(s) not found collect2: ld returned 1 exit status make[1]: *** [openssl.bundle] Error 1 make: *** [all] Error 1 ### execution of make failed, exit code 2 Removing runtime build-lock... Removing build-lock package... /sw/bin/dpkg-lockwait -r fink-buildlock-ruby18-1.8.1-2 (Lettura del database ... 90770 file e directory attualmente installati.) Rimozione di fink-buildlock-ruby18-1.8.1-2 ... Failed: phase compiling: ruby18-1.8.1-2 failed -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Troubles making ruby18
Alessio Sarti wrote: Dear all, I'm trying to compile ruby18 against on Mac OS X 10.5.6 (9G55) uname -r gives: Darwin macbook-pro-di-alessio-sarti.local 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386 The error I get comes up when trying to make openssl related libs, and is appended below... Am I missing something stupid? Cheers, alessio cc -dynamic -bundle -L/sw/src/fink.build/ruby18-1.8.1-2/ruby-1.8.1 -L/sw/lib -o openssl.bundle openssl_missing.o ossl.o ossl_asn1.o ossl_bio.o ossl_bn.o ossl_cipher.o ossl_config.o ossl_digest.o ossl_engine.o ossl_hmac.o ossl_ns_spki.o ossl_ocsp.o ossl_pkcs12.o ossl_pkcs7.o ossl_pkey.o ossl_pkey_dh.o ossl_pkey_dsa.o ossl_pkey_rsa.o ossl_rand.o ossl_ssl.o ossl_x509.o ossl_x509attr.o ossl_x509cert.o ossl_x509crl.o ossl_x509ext.o ossl_x509name.o ossl_x509req.o ossl_x509revoked.o ossl_x509store.o -lruby -lssl -lcrypto -ldl -lobjc Undefined symbols: _ENGINE_load_chil, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_atalla, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_aep, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_ubsec, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_4758cca, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_nuron, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_sureware, referenced from: _ossl_engine_s_load in ossl_engine.o _ENGINE_load_cswift, referenced from: _ossl_engine_s_load in ossl_engine.o ld: symbol(s) not found collect2: ld returned 1 exit status make[1]: *** [openssl.bundle] Error 1 make: *** [all] Error 1 ### execution of make failed, exit code 2 Removing runtime build-lock... Removing build-lock package... /sw/bin/dpkg-lockwait -r fink-buildlock-ruby18-1.8.1-2 (Lettura del database ... 90770 file e directory attualmente installati.) Rimozione di fink-buildlock-ruby18-1.8.1-2 ... Failed: phase compiling: ruby18-1.8.1-2 failed You should be able to get this version via the binary distribution: sudo apt-get install ruby18 Or, I get the same error with openssl098-dev installed, so if you have that installed, remove it. I'll cc the maintainer to see about moving the current package from unstable, which doesn't suffer from this issue, or to fix this one up not to have this problem anymore. -- Alexander Hansen Fink User Liaison -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Troubles making ruby18
2009/4/3 Alexander Hansen alexanderk.han...@gmail.com: You should be able to get this version via the binary distribution: sudo apt-get install ruby18 Or, I get the same error with openssl098-dev installed, so if you have that installed, remove it. I'll cc the maintainer to see about moving the current package from unstable, which doesn't suffer from this issue, or to fix this one up not to have this problem anymore. Ruby 1.8.1 is ancient, has security issues, and should be replaced with the ruby from unstable (which iirc somebody promised in the package submission for the ruby security update). It would be quite helpful to update the Ruby in stable to the version in unstable. Thanks Michal -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Troubles making ruby18
Indeed, removing openssl098-dev made the job. Thank you so much for your kind help. alessio Michal Suchanek ha scritto: 2009/4/3 Alexander Hansen alexanderk.han...@gmail.com: You should be able to get this version via the binary distribution: sudo apt-get install ruby18 Or, I get the same error with openssl098-dev installed, so if you have that installed, remove it. I'll cc the maintainer to see about moving the current package from unstable, which doesn't suffer from this issue, or to fix this one up not to have this problem anymore. Ruby 1.8.1 is ancient, has security issues, and should be replaced with the ruby from unstable (which iirc somebody promised in the package submission for the ruby security update). It would be quite helpful to update the Ruby in stable to the version in unstable. Thanks Michal -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Troubles making ruby18
Michal Suchanek wrote: 2009/4/3 Alexander Hansen alexanderk.han...@gmail.com: You should be able to get this version via the binary distribution: sudo apt-get install ruby18 Or, I get the same error with openssl098-dev installed, so if you have that installed, remove it. I'll cc the maintainer to see about moving the current package from unstable, which doesn't suffer from this issue, or to fix this one up not to have this problem anymore. Ruby 1.8.1 is ancient, has security issues, and should be replaced with the ruby from unstable (which iirc somebody promised in the package submission for the ruby security update). It would be quite helpful to update the Ruby in stable to the version in unstable. Thanks Michal I'll make sure that there aren't any missing dependencies or versions of dependencies and do that. -- Alexander Hansen Fink User Liaison -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Troubles making ruby18
On Apr 3, 2009, at 6:47 AM, Michal Suchanek wrote: Ruby 1.8.1 is ancient, has security issues, and should be replaced with the ruby from unstable (which iirc somebody promised in the package submission for the ruby security update). It would be quite helpful to update the Ruby in stable to the version in unstable. Updated, as requested. -- Dave -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
[Fink-users] Problems Running Gnome-chess
Hello, I've installed gnome chess. But when I invoke it (via xterm, mlterm, or gnome-terminal) I get | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | Fontconfig error: Cannot load default config file | | (gnome-chess:11005): GdkPixbuf-CRITICAL **: | gdk_pixbuf_get_width: assertion `GDK_IS_PIXBUF | (pixbuf)' failed and in the scratch gnome-chess wsindow that subsequently opens, the apparent area for the chessboard is blank. Can anyone help? I'm using OsX 10.4.11, PowerPC. TIA, Jonathan -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Problems Running Gnome-chess
drjl...@netonecom.net wrote: Hello, I've installed gnome chess. But when I invoke it (via xterm, mlterm, or gnome-terminal) I get | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | | (gnome-chess:11005): Pango-CRITICAL **: | pango_color_parse: assertion `spec != NULL' failed | Fontconfig error: Cannot load default config file | | (gnome-chess:11005): GdkPixbuf-CRITICAL **: | gdk_pixbuf_get_width: assertion `GDK_IS_PIXBUF | (pixbuf)' failed and in the scratch gnome-chess wsindow that subsequently opens, the apparent area for the chessboard is blank. Can anyone help? I'm using OsX 10.4.11, PowerPC. TIA, Jonathan The Pango-CRITICAL messages look fairly standard. It looks like gnome-chess has to be configured to use a back-end program: fink desc gnome-chess Information about 8427 packages read in 1 seconds. gnome-chess-0.4.0-2: Chess client for the GNOME desktop environment This package contains GNOME Chess, a graphical user interface for playing chess and displaying PGN files. It works with different chess programs and servers. It works best with the chess engine Crafty, but most features should also work with GNU Chess. I don't know how one actually gets a board to show up even after setting that, though -- Alexander Hansen Fink User Liaison -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Troubles making ruby18
2009/4/3 David R. Morrison d...@finkproject.org: On Apr 3, 2009, at 6:47 AM, Michal Suchanek wrote: Ruby 1.8.1 is ancient, has security issues, and should be replaced with the ruby from unstable (which iirc somebody promised in the package submission for the ruby security update). It would be quite helpful to update the Ruby in stable to the version in unstable. Updated, as requested. Thanks Michal -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] fink selfupdate fails on PPC G5 OSX-10.5.6
For the nonce, I've put a current snapshot up at http://akhmac.blogdns.net/~hansen/finksnap.tar.gz Basically that contains all of the .info and .patch files from stable and unstable. The easiest way to use it is to download the tarball, copy it into /sw/fink/10.4, and unpack it. I don't have anything set up as of yet to update this file via a cron job. Robert Black wrote: I tried that also, Alexander, but it didn't work. Robert A. Black Research Meteorologist 4301 Rickenbacker Cswy. NOAA/AOML/HRDMiami, FL 33149-1026 Ph: (305) 361-4314 FAX: (305) 361-4528 (NEW) E-Mail: robert.a.bl...@noaa.gov (Any opinions expressed are mine alone, not NOAA policy) On Apr 3, 2009, at 1:23 PM, Alexander Hansen wrote: Robert Black wrote: Dear Alexander: I tried it with port 80, which our firewall has open for http. The cvs server asked for user name password, didn't accept anything I input, including such gems as none, , and anonymous. I guess I just have to wait for the firewall's SuperUser to come in, but he might be over at the tennis match (The Sony/Ericsson tournament is being held here). Robert A. Black Research Meteorologist 4301 Rickenbacker Cswy. NOAA/AOML/HRDMiami, FL 33149-1026 Ph: (305) 361-4314 FAX: (305) 361-4528 (NEW) E-Mail: robert.a.bl...@noaa.gov (Any opinions expressed are mine alone, not NOAA policy) The user should be 'anonymous', and the password blank; I'm not sure if that'll matter, though. -- Alexander Hansen Fink User Liaison -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
