mldonkey, a multi-networks file-sharing client - Tasks: task #4441, some ./configure issues
You are not allowed to post comments on this tracker with your current authentication level.
task #4441: some ./configure issues
Submitter: | Rebel2k <rebel2k> | ||
Submitted: | Thu 21 Jul 2005 03:29:38 PM UTC | ||
Category: | Core | Priority: | 5 - Normal |
Status: | Cancelled | Assigned to: | None |
Open/Closed: | Closed | Should Start On: | Thu 21 Jul 2005 12:00:00 AM UTC |
Should be Finished on: | Wed 21 Dec 2005 12:00:00 AM UTC |
Fri 18 Aug 2006 07:19:06 PM UTC, comment #2: |
spiralvoice <spiralvoice> |
Wed 03 May 2006 02:13:20 PM UTC, comment #1: ./configure is autoconf generated, so it's probably an autoconf bug/feature...
|
pango <mlpango> |
Thu 21 Jul 2005 03:29:38 PM UTC, original submission:
Well, I have looked at the configure script of mldonkey today and a few things attract my attention:
|
Rebel2k <rebel2k> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2006-08-18 | spiralvoice | Status | None | Cancelled | |
Open/Closed | Open | Closed | |||
2005-09-19 | dprice | Dependencies | Removed dependency from task #4686 | - |
Powered by Savane 3.13-d3ae.
Corresponding source code
1. DirectConnect sourcecode (and opennapster, soulseek, openft) are kept for later re-implementation
2. --disable-xyz and --enable-xyz work everytime, --enablexyz-abc is not supported because the former are supported values in autoconf
http://article.gmane.org/gmane.comp.sysutils.autoconf.general/7960
"uniformity of interface. I can (theoretically) pass the same
--enable-foo --without-bar --disable-baz
flags to all configure scripts of all packages that use Autoconf: they
either ignore it, or deal with it (in a hopefully similar way). That
way, packages can be stacked, and flags passed to sub-configure scripts
without them erroring out due to unknown flags."
So you can have any value after "--disable-" and "--enable-"
but not before the last "-".