[Fink-devel] multi-cpu machines... make -j 2
Hi All, I'm just getting a chance to use a dual G5 at work... much fun! (It's also my first machine with 10.3) Is there a way with for fink to notice that there are two cpu's and issue a make -j 2 for packages that can handle it? I know, the G5 2 GHz cpu's are pretty darn fast by themselves, but would be great to get even more out of these machines! Thanks -kurt --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] multi-cpu machines... make -j 2
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 [EMAIL PROTECTED] wrote: Hi All, I'm just getting a chance to use a dual G5 at work... much fun! (It's also my first machine with 10.3) Is there a way with for fink to notice that there are two cpu's and issue a make -j 2 for packages that can handle it? To make the answer short. Technically it is possible, yet fink/Fink does not officially support this. For various reasons, some are technical, some are political. Please review the mailing list for further detail, as this has been rehashed numerous times. Thank you and happy finking - -d -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (Darwin) iD8DBQE/5fPHPMoaMn4kKR4RAyznAJ9bcBg8iq9kAahSLxKNQdz5mQuyaQCfTpCr LTl9ithPLV8Njr22WkngPpY= =a4CM -END PGP SIGNATURE- --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] linker question
Hi, What do I add to an info file to link with a specific library (libstdc++ in this case)? thanks, - Koen. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Problems with ant-1.6.0-21
I'm having a problem installing the new 1.6.0 version of ant. It fails when running build.sh This results in no ant subdirectory, so nothing is copied to /sw/lib/ant Any ideas? Here's my attempt at debugging the build.sh script /sw/src/ant-1.6.0-21/apache-ant-1.6.0 [EMAIL PROTECTED] sudo sh -x ./build.sh + cygwin=false + darwin=false ++ uname + darwin=true + '[' -z /Library/Java/Home ']' + REALANTHOME=/sw/lib/ant + '[' -z /sw/src/ant-1.6.0-21/apache-ant-1.6.0 ']' + ANT_HOME=/sw/src/ant-1.6.0-21/apache-ant-1.6.0/bootstrap + export ANT_HOME + test '!' -f bootstrap/lib/ant.jar -o '!' -x bootstrap/bin/ant -o '!' -x bootstrap/bin/antRun + test '!' -f bootstrap/lib/ant.jar -o '!' -x bootstrap/bin/ant -o '!' -x bootstrap/bin/antRun + '[' /sw/lib/ant '!=' '' ']' + false + ANT_INSTALL=-Dant.install=/sw/lib/ant + bootstrap/bin/ant -lib lib/optional -Dant.install=/sw/lib/ant java.lang.InstantiationException: org.apache.tools.ant.Main at java.lang.Class.newInstance0(Class.java:293) at java.lang.Class.newInstance(Class.java:261) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:214) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:90) Here's the full output of the fink build. /usr/bin/sudo /sw/bin/fink rebuild ant Information about 2204 packages read in 1 seconds. The following package will be rebuilt: ant /bin/rm -rf ant-1.6.0-21 /bin/mkdir -p /sw/src/ant-1.6.0-21 bzip2 -dc /sw/src/apache-ant-1.6.0-src.tar.bz2 | /sw/bin/tar -xf - JAVA_HOME=/Library/Java/Home ./build.sh -Ddist.name=ant -Dchmod.fail=false dist ... Bootstrapping Ant Distribution ... Compiling Ant Classes Note: Some input files use or override a deprecated API. Note: Recompile with -deprecation for details. ... Copying Required Files ... Building Ant Distribution Buildfile: build.xml bootstrap: prepare: check_for_optional_packages: build: Created dir: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib Compiling 230 source files to /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/classes Note: Some input files use or override a deprecated API. Note: Recompile with -deprecation for details. Copying 1 file to /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/classes Copying 2 files to /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/classes Copying 2 files to /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/classes/org/ apache/tools/ant/taskdefs/optional/junit/xsl jars: Copying 4 files to /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build Copying 1 file to /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- launcher.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- bootstrap.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- nodeps.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- trax.jar Building MANIFEST-only jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- xalan1.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- xalan1.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- xalan2.jar Building MANIFEST-only jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- xslp.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- xslp.jar Building MANIFEST-only jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- apache-resolver.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- apache-resolver.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- junit.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- jakarta-regexp.jar Building MANIFEST-only jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- jakarta-oro.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- jakarta-oro.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- jakarta-bcel.jar Building MANIFEST-only jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- jakarta-log4j.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- jakarta-log4j.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- commons-logging.jar Building MANIFEST-only jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- apache-bsf.jar Building jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- apache-bsf.jar Building MANIFEST-only jar: /Volumes/Local/sw/src/ant-1.6.0-21/apache-ant-1.6.0/build/lib/ant- stylebook.jar
Re: [Fink-devel] Problems with ant-1.6.0-21
On Mon, 22 Dec 2003, Rohan Lloyd wrote: I'm having a problem installing the new 1.6.0 version of ant. It fails when running build.sh This results in no ant subdirectory, so nothing is copied to /sw/lib/ant Any ideas? That's something I added last night. I'll take a look at it, but it did work for me. -- Hisashi T Fujinaka - [EMAIL PROTECTED] BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] bin-dist made more regularely
Hi Dave et al., I pick up the thread here. As you might have seen, I committed the first version of the new bindist scripts to cvs. I used the branch 'remis-bindist' for the scripts module. The scripts are documented in a new README and the HOWTO reflects the changes. I'd be glad if some of the experts could look over the scripts and comment about them. Here some remarks about the first round of comments: On Dec 16, 2003, at 9:00 AM, David R. Morrison wrote: Hi Remi. My preference would be for you to create a CVS branch in the scripts module for your changes, and then when you are done and everyone agrees, we can move them to HEAD. I have a few corrections to what you wrote: From the scripts/bindist/HOWTO: Q: What is needed before I can start making a binary distribution? A: - You need a working fink installation. However during the build phase all but the essential packages will be purged. Thus DON'T DO IT on a production system where you relay on certain fink packages. - The user building the binary distribution must be able to get root privilegies on the build machine using 'sudo' - The maintainer must have an account at SourceForge.net which enables her/him to upload the binary distribution. This is no longer relevant, actually. The final step in the distribution process must be handled by the fink-core team, and its something we've been asked not to document publically. The goal of the HOWTO can be to describe how to get a working bindist into the (local) bindist directory. done. - Enough disk space to hold the local binary distribution (quantify???) - Before making a new binary distribution, the packages used must be tagged in cvs with the release number used. There is a question about order of events here. It's true that everything in the bindist needs to be tagged. On the other hand, it has often been necessary to make minor repairs to packages as the bindist is being created. Sometimes, I've tagged everything before I started and then revised the tags every time I made a repair. Other times, I've left the tagging to the end. I strongly prefer to tag the packages first and move the tag if necessary for those packages which fail. This allows further commits while the bin dist is built. Otherwise you'll have to freeze the tree during the hole build or pay close attention to keep the bin dist consistent. - If a binary distribution for the stable tree is built, only the stable tree must be enabled (at /sw/etc/fink.conf). Otherwise packages might get built against libraries existing only in the unstable tree. There is another consideration here, too: the crypto tree. I always first build the bindist with the crypto tree disabled, to make sure that we haven't accidentally put things into the non-crypto tree which depend on things in the crypto tree. Then I make a second pass, with both stable/main and stable/crypto enabled. This is handled automatically in 'bdbuild'. The script defines in which order the categories in the main tree are built. I force the build of each package, i.e. fink is called with 'rebuild' instead of 'build'. This assures that each package going into the bindist has only those dependencies installed which it defines itself. This has the disadvantage, that some packages are built twice. This overhead can be minimised by defining a clever order of the categories. The version implemented in 'bdbuild' is my first best guess. There are a few other tweaks which are necessary as well. Fink is not very smart about specifying the default choice, and in the automated system, we always take the default choice. For this reason, I remove the various system-foo packages before I start making the bindist. (Will be less necessary in 10.3 since most system-foo package are now virtual packages and needn't be added or removed.) This is now handled by 'MatchPackageRegEx' which disfavours any system packages. For this to work you'll need a fink newer than yesterday, Dec 20 2003. -- -- - Q: What scripts need to be run to make a binary distribution? A: # First edit bdenv.csh to set up the site specific settings # Then source the file to set up the environment source bdenv.csh # Create the directory structure for a new release, f.e. 7.0. This # assumes that the packages in cvs used for the binary distribution # are cvs tagged to 7.0 ./bdnewrel 7.0 # Get the sources from cvs and copy them into the dist structure # excluding those packages which may not be distributed as binaries ./bdsources # Next build the deb files for the sources copied in the previous # step. Successfully compiled packages are copied into the dist # structure, including the source files. ./bdbuild # After the previous step
Re: [Fink-devel] Problems with ant-1.6.0-21
On 22 Dec 2003, at 10:55 AM, Hisashi T Fujinaka wrote: On Mon, 22 Dec 2003, Rohan Lloyd wrote: I'm having a problem installing the new 1.6.0 version of ant. It fails when running build.sh This results in no ant subdirectory, so nothing is copied to /sw/lib/ant Any ideas? That's something I added last night. I'll take a look at it, but it did work for me. I've found the cause. I had fop installed, which includes ant-1.5.1. It was picking that up in my CLASSPATH, and getting very confused. When I removed fop and tried installing ant-1.6.0 it worked fine. -- Rohan Lloyd --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] /sw in .patch and .patch filenames
I notice a *lot* of packages have hardcoded /sw in their .patch files. So first, could everyone please check the things yuo maintain for this problem? I'm going to make 'fink validate' whine about this shortly... To make this and other validator checks more reliable, I'm wondering about .patch filenames. Is there a time when having a *.info and *.patch where the corresponding filename roots * do not match is a good idea? We never say not to do this, but Packaging Manual says that's the usual way. A lot of packages now use PatchScript that reads the patchfile (cf. Patch) the validator code doesn't know to check the .patch at all, so if this is the rule we could always check *.patch if it is present (instead of checking whatever Patch: says). dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] /sw in .patch and .patch filenames
On 22 Dec 2003, at 1:55 PM, Daniel Macks wrote: I notice a *lot* of packages have hardcoded /sw in their .patch files. So first, could everyone please check the things yuo maintain for this problem? I'm going to make 'fink validate' whine about this shortly... To make this and other validator checks more reliable, I'm wondering about .patch filenames. Is there a time when having a *.info and *.patch where the corresponding filename roots * do not match is a good idea? We never say not to do this, but Packaging Manual says that's the usual way. A lot of packages now use PatchScript that reads the patchfile (cf. Patch) the validator code doesn't know to check the .patch at all, so if this is the rule we could always check *.patch if it is present (instead of checking whatever Patch: says). One example I've seen is emacs21. There are 3 variants (emacs21, emacs21-xaw3d and emacs21-nox) but they all use the same patch file. /sw/fink/10.2-gcc3.3/unstable/main/finkinfo/editors [EMAIL PROTECTED] grep \.patch emacs21*.info emacs21-21.3-11.info: sed 's|@PREFIX@|%p|g' %a/emacs21-%v-%r.patch | patch -p1 emacs21-nox-21.3-11.info: sed 's|@PREFIX@|%p|g' %a/emacs21-%v-%r.patch | patch -p1 emacs21-xaw3d-21.3-11.info: sed 's|@PREFIX@|%p|g' %a/emacs21-%v-%r.patch | patch -p1 -- Rohan Lloyd --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: fink/perlmod/Fink ChangeLog,1.477,1.478 Validation.pm,1.79,1.80
great work Dan, just like to say that first :D
My take on this is as follows
number one I think it needs to be an error or a warning with blinking
lights :) number two patch file checking when using Patch: is easy and
done, PatchScript checking as you say is a little more tough, we need
to parse it and I think search for %a, no matter what we need to use %a
to call patch. So we parse PatchScript for /sw then check for %a to
find the patch file and parse it. I'm gonna have a look at this unless
you get to it first.
I'd like to say with all this new work recently Fink sure is moving
ahead and looking good. Thanks Dan.
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.
On 21-Dec-03, at 11:15 PM, Daniel Macks wrote:
Update of /cvsroot/fink/fink/perlmod/Fink
In directory sc8-pr-cvs1:/tmp/cvs-serv5583
Modified Files:
ChangeLog Validation.pm
Log Message:
Warn on hardcoded /sw in .patch in Patch (not in PatchScript).
Index: ChangeLog
===
RCS file: /cvsroot/fink/fink/perlmod/Fink/ChangeLog,v
retrieving revision 1.477
retrieving revision 1.478
diff -u -d -r1.477 -r1.478
--- ChangeLog 22 Dec 2003 02:06:28 - 1.477
+++ ChangeLog 22 Dec 2003 06:15:54 - 1.478
@@ -1,3 +1,8 @@
+2003-12-22 Daniel Macks [EMAIL PROTECTED]
+
+ * Validation.pm: Check for hardcoded /sw in patch file (as loaded
+ by Patch, not as by PatchScript).
+
2003-12-21 Daniel Macks [EMAIL PROTECTED]
* Services.pm: Gave prompt_selection_new more flexible default-
Index: Validation.pm
===
RCS file: /cvsroot/fink/fink/perlmod/Fink/Validation.pm,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -d -r1.79 -r1.80
--- Validation.pm 19 Dec 2003 12:33:41 - 1.79
+++ Validation.pm 22 Dec 2003 06:15:54 - 1.80
@@ -254,7 +254,7 @@
# Should check/verifies the following in .info files:
# + the filename matches %f.info
-# + patch file is present
+# + patch file (from Patch, not PatchScript) is present
# + all required fields are present
# + warn if obsolete fields are encountered
# + warn about missing Description/Maintainer/License fields
@@ -264,7 +264,8 @@
# + warn if fields seem to contain the package name/version, and
suggest %n/%v should be used
# (excluded from this are fields like Description, Homepage etc.)
# + warn if unknown fields are encountered
-# + warn if /sw is hardcoded in the script or set fields
+# + warn if /sw is hardcoded in the script or set fields or patch file
+# (from Patch, not PatchScript)
# + correspondence between source* and source*-md5 fields
# + if type is bundle/nosource - warn about usage of Source etc.
#
@@ -272,6 +273,7 @@
# - better validation of splitoffs
# - validate dependencies, e.g. foo ( 1.0-1) should generate an
error since
# it uses instead of .
+# - checks against patch files used in PatchScript (not just Patch)
# - ... other things, make suggestions ;)
#
sub validate_info_file {
@@ -598,6 +600,11 @@
}
elsif ($patch_file_content =~ m/\r/s) {
print Error: Patch file has Mac line endings. ($value)\n;
+$looks_good = 0;
+ }
+ # Check for hardcoded /sw.
+ if ($patch_file_content =~ /\/sw([\s\/]|$)/) {
+print Warning: Patch file appears to contain a hardcoded /sw.
($value)\n;
$looks_good = 0;
}
}
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for
IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys
admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Fink-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-commits
PGP.sig
Description: This is a digitally signed message part
