Re: [Fink-devel] New libgettext8 package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/9/09 11:56 AM, Max Horn wrote: > Oh, no need to -- if anything goes wrong, I'll blame it on Ben for not > telling me not to proceed ;-) And I'll point out that you made the change. ;) # fink install finger-pointing Scanning package description files.. Information about 8826 packages read in 9 seconds. No packages to install. - -- Benjamin Reed a.k.a. Ranger Rick a.k.a. Raccoon Fink Fink, KDE, and Mac OS X development Blog: http://www.raccoonfink.com/ Music: http://music.raccoonfink.com/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLH9h7Uu+jZtP2Zf4RAle/AJ0Q2glg5ijBzsvwTMW3JwPcP/3CTwCeOOwH L99MJ65FgqqcrvDKDsppwkg= =Q2+L -END PGP SIGNATURE- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Am 09.12.2009 um 17:51 schrieb Koen van der Drift: > Now duck as fast as you can, Max ;-) Oh, no need to -- if anything goes wrong, I'll blame it on Ben for not telling me not to proceed ;-) Cheers, Max -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Now duck as fast as you can, Max ;-) - Koen. On Wed, Dec 9, 2009 at 11:40 AM, Max Horn wrote: > > Am 09.12.2009 um 17:17 schrieb Benjamin Reed: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 12/9/09 10:55 AM, Max Horn wrote: >> >>> OK. So considering we have >>> >>> SetMAKEFLAGS: -j1 >>> >>> in both libgettext info files, it should be relatively safe to remove >>> the BC and wait what happens, right? >> >> Seems like it should be, yeah. > > Excellent. I'll do that now, then, and also will bump the revision, to > force lots of people to build it. That way, we should soon find out if > there are other hidden issues! > > Cheers, > Max > > -- > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > ___ > Fink-devel mailing list > Fink-devel@lists.sourceforge.net > http://news.gmane.org/gmane.os.apple.fink.devel > Subscription management: > https://lists.sourceforge.net/lists/listinfo/fink-devel > -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Am 09.12.2009 um 17:17 schrieb Benjamin Reed: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 12/9/09 10:55 AM, Max Horn wrote: > >> OK. So considering we have >> >> SetMAKEFLAGS: -j1 >> >> in both libgettext info files, it should be relatively safe to remove >> the BC and wait what happens, right? > > Seems like it should be, yeah. Excellent. I'll do that now, then, and also will bump the revision, to force lots of people to build it. That way, we should soon find out if there are other hidden issues! Cheers, Max -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/9/09 10:55 AM, Max Horn wrote: > OK. So considering we have > > SetMAKEFLAGS: -j1 > > in both libgettext info files, it should be relatively safe to remove > the BC and wait what happens, right? Seems like it should be, yeah. - -- Benjamin Reed a.k.a. Ranger Rick a.k.a. Raccoon Fink Fink, KDE, and Mac OS X development Blog: http://www.raccoonfink.com/ Music: http://music.raccoonfink.com/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLH82sUu+jZtP2Zf4RAqSjAJ43lmAv/mN8/uSA7iZPn46Ngc4NDACgmEG4 1kdg9tdao+nGV/YNn73Bog8= =bZoo -END PGP SIGNATURE- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Am 09.12.2009 um 16:28 schrieb Benjamin Reed: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 12/9/09 10:23 AM, Max Horn wrote: > >> Hm, I see how that would apply to distcc, but how does this explain a >> conflict with ccache? > > Oh, ccache was probably a red herring, since enabling distcc involves > setting a var for ccache, I probably wrote both, but I'm sure it was > distcc's fault. OK. So considering we have SetMAKEFLAGS: -j1 in both libgettext info files, it should be relatively safe to remove the BC and wait what happens, right? Bye, Max -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/9/09 10:23 AM, Max Horn wrote: > Hm, I see how that would apply to distcc, but how does this explain a > conflict with ccache? Oh, ccache was probably a red herring, since enabling distcc involves setting a var for ccache, I probably wrote both, but I'm sure it was distcc's fault. - -- Benjamin Reed a.k.a. Ranger Rick a.k.a. Raccoon Fink Fink, KDE, and Mac OS X development Blog: http://www.raccoonfink.com/ Music: http://music.raccoonfink.com/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLH8IFUu+jZtP2Zf4RAv7HAJ0S8n49FUyCsIRkvDXi+gx8MAivJACdFE3r wLC92h5OmzMAIkrrt1qsga8= =JklU -END PGP SIGNATURE- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/9/09 10:00 AM, Max Horn wrote: > Unfortunately, this message does not really tell me in which way it is > "unfriendly." I haven't been able to find out anything else. Ben, do you > remember what prompted you to make this change? I don't recall, but it's usually a random crash that "make -j1" resolves. That said, I was unaware of the environment way of "conflicting" with ccache, so feel free to change it. - -- Benjamin Reed a.k.a. Ranger Rick a.k.a. Raccoon Fink Fink, KDE, and Mac OS X development Blog: http://www.raccoonfink.com/ Music: http://music.raccoonfink.com/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLH71GUu+jZtP2Zf4RArfTAJ9vECcV/uBtzsLycG99DFoJDr2XbwCferMK 51aG7+xiLQSyQzODNewY6oQ= =44Up -END PGP SIGNATURE- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Am 09.12.2009 um 16:07 schrieb Benjamin Reed: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 12/9/09 10:00 AM, Max Horn wrote: > >> Unfortunately, this message does not really tell me in which way it >> is >> "unfriendly." I haven't been able to find out anything else. Ben, >> do you >> remember what prompted you to make this change? > > I don't recall, but it's usually a random crash that "make -j1" > resolves. Hm, I see how that would apply to distcc, but how does this explain a conflict with ccache? > > That said, I was unaware of the environment way of "conflicting" with > ccache, so feel free to change it. Cheers, Max -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Am 09.12.2009 um 15:14 schrieb Daniel Macks: > Max sez: >> >> So, do we agree that it would be nice to not "build conflict" with >> ccache? >> >> If so, I'd be willing to investigate making it work without the >> "ccache" and "distcc" build conflicts. For starters, though, I'd like >> to know why this BuildConflict is there in the first place, so that I >> can verify whether my changes actually work. In a quick test, simply >> commenting out the BuildConflicts did not cause any particular build >> issues. The .info file also contains no comments that explain this >> build conflict... > > I have no idea what the specific problem was, or if it is still a > problem. You'll have to dig through the cvs commit-messages. But I > agree that BCon should be a last-resort solution for when env vars, > simple patches, etc can't solve the problem (whatever it is). CVS logs tell me that Ben added the BC, to quote: revision 1.8 date: 2007/03/14 19:41:34; author: rangerrick; state: Exp; lines: +1 -0 gettext is ccache/distcc-unfriendly Unfortunately, this message does not really tell me in which way it is "unfriendly." I haven't been able to find out anything else. Ben, do you remember what prompted you to make this change? If nobody can recall what it was, I think we should remove the BC, and wait for bug reports. If we are lucky, there are none. Otherwise, we can document the issue in the .info file and come up with a fix (in the worst case, re-adding the BC, but this time with a comment explaining it). Bye, Max -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Max sez: > > So, do we agree that it would be nice to not "build conflict" with > ccache? > > If so, I'd be willing to investigate making it work without the > "ccache" and "distcc" build conflicts. For starters, though, I'd like > to know why this BuildConflict is there in the first place, so that I > can verify whether my changes actually work. In a quick test, simply > commenting out the BuildConflicts did not cause any particular build > issues. The .info file also contains no comments that explain this > build conflict... I have no idea what the specific problem was, or if it is still a problem. You'll have to dig through the cvs commit-messages. But I agree that BCon should be a last-resort solution for when env vars, simple patches, etc can't solve the problem (whatever it is). dan -- Daniel Macks dma...@netspace.org http://www.netspace.org/~dmacks -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Am 07.12.2009 um 12:02 schrieb Max Horn: > So, do we agree that it would be nice to not "build conflict" with > ccache? > > If so, I'd be willing to investigate making it work without the > "ccache" and "distcc" build conflicts. For starters, though, I'd like > to know why this BuildConflict is there in the first place, so that I > can verify whether my changes actually work. In a quick test, simply > commenting out the BuildConflicts did not cause any particular build > issues. The .info file also contains no comments that explain this > build conflict... Maybe I should just commit a version without the build conflict and wait till I hear somebody shout loud about issues caused by it? :-) Bye, Max -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Am 02.12.2009 um 19:46 schrieb Daniel Macks: > On Wed, Dec 02, 2009 at 06:39:11PM +0100, Max Horn wrote: >> [...] >> >> Exactly. I am unhappy whenever a package forces me to uninstall >> ccache- >> default, even if it is only temporary and and it gets reinstalled >> later on automatically: It affects all my concurrent build >> activities, >> which is negative. Also, I wonder what happens if I try to "fink >> build" two packages *in parallel* (i.e. in different terminals) that >> both conflict with ccache-default , esp. if one finishes earlier than >> the other ? > > The first one's attempt to reinstall (i.e., while the second one is > still building) will fail because a build_lock_ still exists, not just > a fink "remove this before start the process" action. The whole > purpose of the buildlock system is to make it safe to run multiple > fink instances concurrently. Which adds to the poor user experience in > this case because "could not reinstall after building" will cause the > first fink process to fail. So, do we agree that it would be nice to not "build conflict" with ccache? If so, I'd be willing to investigate making it work without the "ccache" and "distcc" build conflicts. For starters, though, I'd like to know why this BuildConflict is there in the first place, so that I can verify whether my changes actually work. In a quick test, simply commenting out the BuildConflicts did not cause any particular build issues. The .info file also contains no comments that explain this build conflict... Cheers, Max -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
On 01 Dec 2009, at 14:44, Jean-François Mertens wrote: > Build went through w/o problem on 64bit, but on 32bit (same machine) > failed with the strange "Too many open files" : > >> Making all in intl-java >> /bin/sh ../javacomp.sh -d . ./gnu/gettext/GettextResource.java >> ./gnu/gettext/GettextResource.java:1: error: Cannot read the source >> from ./gnu/gettext/GettextResource.java due to internal exception >> java.io.FileNotFoundException:./gnu/gettext/GettextResource.java >> (Too many open files) >> 1 problem (1 error) > the situation became very unpleasant, as every selfupdate wanted to relaunch this build, and more and more pkgs were depending on this broken pkg ... Looking into the builddir, "wc" showed that the CONF_CLASSPATH=... line in gettext-runtime/javacomp.sh listed 152 jar files, in /sw/ share/java _ clearly from pkgs on which libgettext8-shlibs had no dependency :) . Adding then "ulimit -n 1024" as an additional command in the CompileScript allowed to bypass the hurdle ... Jean-Francois -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
On Wed, Dec 02, 2009 at 06:39:11PM +0100, Max Horn wrote: > > Am 01.12.2009 um 15:58 schrieb Jean-Fran?ois Mertens: > > > > > On 01 Dec 2009, at 15:18, Charles Lepple wrote: > > > >> On Tue, Dec 1, 2009 at 8:44 AM, Jean-Fran?ois Mertens > >> wrote: > >>> I notice there is buildconflicts for ccache-default : > >>> this breaks the operation of ccache on anything _ fink or not! _ > >>> going > >>> on in parallel.. > >>> An "export CCACHE_DISABLE=1" (instead of the current "env > >>> CCACHE_DISABLE=1", > >>> so as to apply also to the make command, not only the configure > >>> command) > >>> should suffice in principle ... > >> > >> Jean-Fran?ois, > >> > >> After seeing your email, I went back to re-install ccache-default, > >> and > >> it looks like fink did it automatically. I remember seeing the > >> message > >> saying fink was going to temporarily remove it, and I guess it put it > >> back when it was done. > >> > >> Did ccache-default remain uninstalled on your system? > > > > No ; in general, a BuildConlicts gets reinstalled by fink at the end > > of > > the build. > > That's why I mentioned above "things going on in parallel". > > Exactly. I am unhappy whenever a package forces me to uninstall ccache- > default, even if it is only temporary and and it gets reinstalled > later on automatically: It affects all my concurrent build activities, > which is negative. Also, I wonder what happens if I try to "fink > build" two packages *in parallel* (i.e. in different terminals) that > both conflict with ccache-default , esp. if one finishes earlier than > the other ? The first one's attempt to reinstall (i.e., while the second one is still building) will fail because a build_lock_ still exists, not just a fink "remove this before start the process" action. The whole purpose of the buildlock system is to make it safe to run multiple fink instances concurrently. Which adds to the poor user experience in this case because "could not reinstall after building" will cause the first fink process to fail. dan -- Daniel Macks dma...@netspace.org http://www.netspace.org/~dmacks -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Am 01.12.2009 um 15:58 schrieb Jean-François Mertens: > > On 01 Dec 2009, at 15:18, Charles Lepple wrote: > >> On Tue, Dec 1, 2009 at 8:44 AM, Jean-François Mertens >> wrote: >>> I notice there is buildconflicts for ccache-default : >>> this breaks the operation of ccache on anything _ fink or not! _ >>> going >>> on in parallel.. >>> An "export CCACHE_DISABLE=1" (instead of the current "env >>> CCACHE_DISABLE=1", >>> so as to apply also to the make command, not only the configure >>> command) >>> should suffice in principle ... >> >> Jean-François, >> >> After seeing your email, I went back to re-install ccache-default, >> and >> it looks like fink did it automatically. I remember seeing the >> message >> saying fink was going to temporarily remove it, and I guess it put it >> back when it was done. >> >> Did ccache-default remain uninstalled on your system? > > No ; in general, a BuildConlicts gets reinstalled by fink at the end > of > the build. > That's why I mentioned above "things going on in parallel". Exactly. I am unhappy whenever a package forces me to uninstall ccache- default, even if it is only temporary and and it gets reinstalled later on automatically: It affects all my concurrent build activities, which is negative. Also, I wonder what happens if I try to "fink build" two packages *in parallel* (i.e. in different terminals) that both conflict with ccache-default , esp. if one finishes earlier than the other ? Ideally, no package would ever build conflitc with ccache-default -- for most of them, it should be possible to set CCACHE_DISABLE (as Jean- François explained). This solution is far superior to a build conflict. It's faster (no need to remove and re-install another package), requires less user interaction, does not affect other ongoing compilations (be it by Fink or something else), i.e., is more self-contained. Bye, Max -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
On 01 Dec 2009, at 15:18, Charles Lepple wrote: > On Tue, Dec 1, 2009 at 8:44 AM, Jean-François Mertens > wrote: >> I notice there is buildconflicts for ccache-default : >> this breaks the operation of ccache on anything _ fink or not! _ >> going >> on in parallel.. >> An "export CCACHE_DISABLE=1" (instead of the current "env >> CCACHE_DISABLE=1", >> so as to apply also to the make command, not only the configure >> command) >> should suffice in principle ... > > Jean-François, > > After seeing your email, I went back to re-install ccache-default, and > it looks like fink did it automatically. I remember seeing the message > saying fink was going to temporarily remove it, and I guess it put it > back when it was done. > > Did ccache-default remain uninstalled on your system? No ; in general, a BuildConlicts gets reinstalled by fink at the end of the build. That's why I mentioned above "things going on in parallel". Jean-Francois -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
On Tue, Dec 1, 2009 at 8:44 AM, Jean-François Mertens wrote: > I notice there is buildconflicts for ccache-default : > this breaks the operation of ccache on anything _ fink or not! _ going > on in parallel.. > An "export CCACHE_DISABLE=1" (instead of the current "env > CCACHE_DISABLE=1", > so as to apply also to the make command, not only the configure command) > should suffice in principle ... Jean-François, After seeing your email, I went back to re-install ccache-default, and it looks like fink did it automatically. I remember seeing the message saying fink was going to temporarily remove it, and I guess it put it back when it was done. Did ccache-default remain uninstalled on your system? -- - Charles Lepple -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Tested on 10.5.8 (all software updates installed; Core2Duo) _ both 32bit and 64bit. There was no distribution field to comment out, so the thing ran straight after "fink selfupdate" _ no time to add "-m" ... But "fink check on the debs" is OK (on 64bit), and I see no TestScript.. I notice there is buildconflicts for ccache-default : this breaks the operation of ccache on anything _ fink or not! _ going on in parallel.. An "export CCACHE_DISABLE=1" (instead of the current "env CCACHE_DISABLE=1", so as to apply also to the make command, not only the configure command) should suffice in principle ... Build went through w/o problem on 64bit, but on 32bit (same machine) failed with the strange "Too many open files" : > Making all in intl-java > /bin/sh ../javacomp.sh -d . ./gnu/gettext/GettextResource.java > ./gnu/gettext/GettextResource.java:1: error: Cannot read the source > from ./gnu/gettext/GettextResource.java due to internal exception > java.io.FileNotFoundException:./gnu/gettext/GettextResource.java > (Too many open files) > 1 problem (1 error) Best, Jean-Francois -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
Koen van der Drift wrote: [] > I didn't see a Distribution flag in the info file. Not only is there no Distribution field, it also is built and installed automatically by selfupdate, no questions asked (well, it does actually ask permission, but declining would mean stopping selfupdate). The reason is that libgettext3-shlibs, which is essential and got a new Revision, is automatically updated; it Depends on "gettext-bin (>= %v-%r)", hence gettext-bin will be updated, too, and in this case this means to the latest version gettext-bin-0.17-17, which builds and installs libgettext8-shlibs. You could as well have made it essential right away. -- Martin -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
On Nov 30, 2009, at 2:25 PM, Daniel Macks wrote: > At long last and thanks to jack and can't-even-remember-whom-else, we > now have a new libintl. It's core, so I'm playing conservative with > availability: tested on 10.4, so that's where we have it so far. If > some 10.5 and 10.6 folks on various architectures could comment out > the Distribution flag in their libgettext8-shlibs.info and get some > (hopefully:) positive reports that it 'fink -m build's, can make it > more widely available... > > dan I've been playing with it for a while on 10.6/x86_64 with no issues. Daniel smime.p7s Description: S/MIME cryptographic signature -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] New libgettext8 package
On Nov 30, 2009, at 2:25 PM, Daniel Macks wrote: > If > some 10.5 and 10.6 folks on various architectures could comment out > the Distribution flag in their libgettext8-shlibs.info and get some > (hopefully:) positive reports that it 'fink -m build's, can make it > more widely available... No problem on 10.5/G5, I now have: i gettext 0.10.40-126 Message localization support i gettext-bin 0.17-17 GNU Internationalization utilities i gettext-tools 0.14.5-4GNU Internationalization utils (shared libs) i libgettext3-dev 0.14.5-3GNU Internationalization utilities (Development Files) i libgettext3-shlibs 0.14.5-3GNU Internationalization utils (shared libs) i libgettext8-shlibs 0.17-17 GNU Internationalization utils (shared libs) i libgettextpo2-shlibs0.14.5-4GNU Internationalization utils (shared libs) I didn't see a Distribution flag in the info file. - Koen. -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
