[Fink-users] Why gettext 0.10?
I'm trying to build a package that requires gettext 0.12. This doesn't seem to be available through Fink, which is odd because 0.10 is so old. What am I missing here? If this weren't such a core library, I'd have just built it from source outside the Fink system. But with this one, I'm worried that I'll just cause conflicts down the road. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Problem with selfupdate
Am 18.06.2005 um 00:34 schrieb Martin Costabel: This is a case where upgrading to Xcode-2.1 might help. Is it already recommended to upgrade to Xcode 2.1? Claus --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] strange fink vs gcc behaviour
On Jun 16, 2005, at 10:15 PM, Kevin Horton wrote:Something very strange is going on here. I tried to use gcc 3.3, but fink refused to comply:% sudo gcc_select 3.3Password:Default compiler has been set to:gcc version 3.3 20030304 (Apple Computer, Inc. build 1809)% fink install diaInformation about 4667 packages read in 2 seconds.The package 'dia' will be built and installed.The following package will be installed or updated:diadpkg-deb -b /sw/src/fink.build/root-fink-buildlock-dia-0.94-4 /sw/src/fink.builddpkg-deb: building package `fink-buildlock-dia-0.94-4' in `/sw/src/fink.build/fink-buildlock-dia-0.94-4_2005.06.16-21.56.13_darwin-powerpc.deb'.Setting build lock...dpkg -i /sw/src/fink.build/fink-buildlock-dia-0.94-4_2005.06.16-21.56.13_darwin-powerpc.debSelecting previously deselected package fink-buildlock-dia-0.94-4.(Reading database ... 61663 files and directories currently installed.)Unpacking fink-buildlock-dia-0.94-4 (from .../fink-buildlock-dia-0.94-4_2005.06.16-21.56.13_darwin-powerpc.deb) ...Setting up fink-buildlock-dia-0.94-4 (2005.06.16-21.56.13) ...Removing build lock...dpkg -r fink-buildlock-dia-0.94-4(Reading database ... 61664 files and directories currently installed.)Removing fink-buildlock-dia-0.94-4 ...Failed: The package dia-0.94-4 must be compiled with gcc 4.0.0,however, you currently have gcc 3.3 selected. To correctthis problem, run the command: sudo gcc_select 4.0===I took a look at dia.info, and it had a line calling for gcc 3.3:GCC: 3.3I commented out the GCC: 3.3 line, and now fink deigns to allow me to select gcc 3.3. Dia built OK, and seems to run properly, once I was able to select gcc 3.3Thanks for the assistance.This certainly needs to be better documented. Here is the story:We would prefer everybody to run fink with gcc_select set to its most current value (which is 3.3 for 10.3 and 4.0 for 10.4). This way, when there are bugs, we don't have to check on which compiler the user was using. Also, having people do this helps achieve one of fink's goals, which is to have packages build the same no matter who builds them.However, the only time we actually try to enforce this is when the ever-changing g++ ABI is involved, because that's one time we are sure that having the wrong compiler selected will lead to disaster. We indicate that the g++ compiler is being used by means of the GCC field, which helps developers keep track of *which* version of g++ is required.The way this works in practice is that if the GCC field appears at all within a fink package, then fink insists that the gcc_select is set to its most current value. Package maintainers are expected to handle cases in which g++ should be different than that by doing things to their package (perhaps with the SetCXX flag).What makes this a bit confusing is that in the 10.4-transitional tree, we want you to set gcc_select to 4.0 but also, behind the scenes, fink is guaranteeing that g++ will be version 3.3 and not version 4.0. This lets us use all the old "GCC: 3.3" packages during a transitional period, while we get ready for the full conversion to g++-4.0.Hope this helps. -- Dave
Re: [Fink-users] Why gettext 0.10?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jun 19, 2005, at 4:17 AM, Warren Young wrote: I'm trying to build a package that requires gettext 0.12. This doesn't seem to be available through Fink, which is odd because 0.10 is so old. What am I missing here? If this weren't such a core library, I'd have just built it from source outside the Fink system. But with this one, I'm worried that I'll just cause conflicts down the road. It's called libgettext3. `fink list gettext' - -chris zubrzycki - - -- PGP public key: http://homepage.mac.com/beren/publickey.txt ID: 0xA2ABC070 Fingerprint: 26B0 BA6B A409 FA83 42B3 1688 FBF9 8232 A2AB C070 I think you've been smoking Cocoa instead of coding with it -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (Darwin) Comment: Please sign reply-http://www.gnupg.org iEYEARECAAYFAkK1myQACgkQ+/mCMqKrwHCDeQCeO79YeR5cBrEVn+R8EH2J0MzV H3MAoKATvYvbUZ4stgESqYQ58kQ1iS8C =6wdU -END PGP SIGNATURE- --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Problem with selfupdate
Claus Atzenbeck wrote: Am 18.06.2005 um 00:34 schrieb Martin Costabel: This is a case where upgrading to Xcode-2.1 might help. Is it already recommended to upgrade to Xcode 2.1? I suppose most developers will have done so. There is still a problem with bootstrapping, because the version of dpkg in the bootstrapping package is not yet updated to work with Xcode-2.1 (whereas we seem to conclude from the present discussion that the non-bootstrap dpkg has issues even with Xcode-2.0). Otherwise I would estimate that the bug population has not increased between 2.0 and 2.1; some have been fixed, some others (not bugs, but new behavior) have appeared. -- Martin --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] libgnome2-2.10.0-1 failed configure step
On Sat, 18 Jun 2005, Daniel Macks wrote: On Sat, Jun 18, 2005 at 11:01:49PM +0100, Viv Kendon wrote: [] appending configuration tag F77 to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for fort77 option to produce PIC... -fno-common checking if fort77 PIC flag -fno-common works... ### execution of export failed, exit code 1 Removing build lock... dpkg -r fink-buildlock-libgnome2-2.10.0-1 (Reading database ... 84131 files and directories currently installed.) Removing fink-buildlock-libgnome2-2.10.0-1 ... Failed: phase compiling: libgnome2-2.10.0-1 failed 1. why did the termination of the build process result in that fork error? There's a bug in ./configure or libtool that causes a fork-bomb with fort77. 2. any advice on how to get libgnome2 to build? I just uploaded a corrected libgnome2.info that allows building libgnome2 in the presence of fort77. Alternately, you can just remove fort77 while building libgnome2. Thanks for this, it came through to the mirrors and I built and installed libgnome2 with fort77 installed without problems. But a few more updates also came through: here is one that seems to require the same fix: appending configuration tag F77 to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for fort77 option to produce PIC... -fno-common checking if fort77 PIC flag -fno-common works... make: *** No targets specified and no makefile found. Stop. ### execution of export failed, exit code 2 Removing build lock... dpkg -r fink-buildlock-libgnomeui2-2.6.1.1-11 (Reading database ... 84132 files and directories currently installed.) Removing fink-buildlock-libgnomeui2-2.6.1.1-11 ... Failed: phase compiling: libgnomeui2-2.6.1.1-11 failed (same fork error). many thanks, -- Viv Dr Viv Kendon [EMAIL PROTECTED] Quantum Information tel: 0113 343 3897 Physics Astronomy University of Leeds http://quantum.leeds.ac.uk/~viv --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] libgnome2-2.10.0-1 failed configure step
On Sun, Jun 19, 2005 at 08:33:46PM +0100, Viv Kendon wrote: On Sat, 18 Jun 2005, Daniel Macks wrote: There's a bug in ./configure or libtool that causes a fork-bomb with fort77. Thanks for this, it came through to the mirrors and I built and installed libgnome2 with fort77 installed without problems. But a few more updates also came through: here is one that seems to require the same fix: Failed: phase compiling: libgnomeui2-2.6.1.1-11 failed (same fork error). I just uploaded new .info for that one. Thanks for catching it (I won't have access to fort77 on my test machine for a few days:( dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Why gettext 0.10?
On Jun 19, 2005, at 10:19 AM, Chris Zubrzycki wrote: It's called libgettext3. fink install libgettext3 says: Information about 1791 packages read in 1 seconds. Failed: no package found for specification 'libgettext3'! I'm using Fink 0.80 on an up-to-date Tiger system. I did a selfupdate and an update-all last night. Do I need to add some other repository to the fink configuration file? `fink list gettext' That says: Information about 1791 packages read in 2 seconds. i gettext 0.10.40-19 Message localization support i gettext-bin 0.10.40-19 Executables for gettext package i gettext-dev 0.10.40-19 Developer files for gettext package i gettext-tools0.10.40-19 Developer executables for gettext package fink apropos gettext says more or less the same thing. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
[Fink-users] gtk+2-2.6.7-2 compile fails
I'm running unstable fink on Tiger, undated a few minutes ago. gtk+2-2.6.7-2 will not compile. It fails as: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -DXDG_PREFIX=_gtk_xdg -no-cpp- precomp -DX_LOCALE -I/sw/include -O3 -funroll-loops -fstrict-aliasing -pipe -Wall -c xdgmime.c -fno-common -DPIC -o .libs/xdgmime.o xdgmimecache.c: In function '_gtk_xdg_cache_new_from_file': xdgmimecache.c:131: error: 'uint16_t' undeclared (first use in this function) xdgmimecache.c:131: error: (Each undeclared identifier is reported only once xdgmimecache.c:131: error: for each function it appears in.) xdgmimecache.c:131: error: parse error before ')' token xdgmimecache.c:132: error: parse error before ')' token xdgmimecache.c: In function 'cache_magic_matchlet_compare_to_data': xdgmimecache.c:159: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:159: error: parse error before ')' token xdgmimecache.c:160: error: parse error before ')' token xdgmimecache.c:161: error: parse error before ')' token xdgmimecache.c:162: error: parse error before ')' token xdgmimecache.c:163: error: parse error before ')' token xdgmimecache.c: In function 'cache_magic_matchlet_compare': xdgmimecache.c:211: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:211: error: parse error before ')' token xdgmimecache.c:212: error: parse error before ')' token xdgmimecache.c: In function 'cache_magic_compare_to_data': xdgmimecache.c:239: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:239: error: parse error before ')' token xdgmimecache.c:240: error: parse error before ')' token xdgmimecache.c:241: error: parse error before ')' token xdgmimecache.c:242: error: parse error before ')' token xdgmimecache.c: In function 'cache_magic_lookup_data': xdgmimecache.c:274: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:274: error: parse error before ')' token xdgmimecache.c:275: error: parse error before ')' token xdgmimecache.c:276: error: parse error before ')' token xdgmimecache.c: In function 'cache_alias_lookup': xdgmimecache.c:298: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:298: error: parse error before ')' token xdgmimecache.c:299: error: parse error before ')' token xdgmimecache.c:308: error: parse error before ')' token xdgmimecache.c:318: error: parse error before ')' token xdgmimecache.c: In function 'cache_glob_lookup_literal': xdgmimecache.c:336: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:336: error: parse error before ')' token xdgmimecache.c:337: error: parse error before ')' token xdgmimecache.c:346: error: parse error before ')' token xdgmimecache.c:356: error: parse error before ')' token xdgmimecache.c: In function 'cache_glob_lookup_fnmatch': xdgmimecache.c:377: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:377: error: parse error before ')' token xdgmimecache.c:378: error: parse error before ')' token xdgmimecache.c:382: error: parse error before ')' token xdgmimecache.c:383: error: parse error before ')' token xdgmimecache.c: In function 'cache_glob_node_lookup_suffix': xdgmimecache.c:421: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:421: error: parse error before ')' token xdgmimecache.c:432: error: parse error before ')' token xdgmimecache.c:438: error: parse error before ')' token xdgmimecache.c:439: error: parse error before ')' token xdgmimecache.c: In function 'cache_glob_lookup_suffix': xdgmimecache.c:463: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:463: error: parse error before ')' token xdgmimecache.c:464: error: parse error before ')' token xdgmimecache.c:465: error: parse error before ')' token xdgmimecache.c: In function 'find_stopchars': xdgmimecache.c:487: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:487: error: parse error before ')' token xdgmimecache.c:488: error: parse error before ')' token xdgmimecache.c:489: error: parse error before ')' token xdgmimecache.c:493: error: parse error before ')' token xdgmimecache.c: In function '_xdg_mime_cache_get_max_buffer_extents': xdgmimecache.c:561: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:561: error: parse error before ')' token xdgmimecache.c:562: error: parse error before ')' token xdgmimecache.c:562: error: parse error before ')' token xdgmimecache.c: In function '_xdg_mime_cache_mime_type_subclass': xdgmimecache.c:724: error: 'uint32_t' undeclared (first use in this function) xdgmimecache.c:724: error: parse error before ')' token xdgmimecache.c:725: error: parse error before ')' token xdgmimecache.c:734: error: parse error before ')' token xdgmimecache.c:742: error: parse error before ')' token xdgmimecache.c:743: error: parse error before ')' token xdgmimecache.c:747: error: parse error before ')' token xdgmimecache.c: In function
