Freeciv - Bugs: bug #19893, Build from tarball requires same... [Gna!]

Freeciv - Bugs: bug #19893, Build from tarball requires same...

Group

Main
- Main
- View Members
- Search
Homepage
Download
Docs
- Browse
- Submit
- Edit
- Digest
- Export
- Search
Mailing Lists
Source Code
- Use Subversion
- Browse Sources Repository
Bugs
- Browse
- Reset to all open ones
- Submit
- Digest
- Export
- View Statistics
- Search
Tasks
- Browse
- Reset to all open ones
- Submit
- Digest
- Export
- View Statistics
- Search
Patches
- Browse
- Reset to all open ones
- Submit
- Digest
- Export
- View Statistics
- Search

Show feedback again

bug #19893: Build from tarball requires same libtool version that was used while running autogen.sh

Submitted by:	Marko Lindqvist <cazfi>
Submitted on:	Tue 03 Jul 2012 06:31:05 PM UTC

Category:	bootstrap	Severity:	3 - Normal
Priority:	5 - Normal	Status:	None
Assigned to:	None	Open/Closed:	Open
Release:		Operating System:	None
Planned Release:

Add a New Comment (Rich Markup):

You are not logged in

Please log in, so followups can be emailed to you.

( Jump to the original submission)

Sat 07 Jul 2012 12:43:34 AM UTC, comment #9: They are not symlinks in tarball. It's probably automake that takes care of that.	Marko Lindqvist <cazfi>
Sat 07 Jul 2012 12:39:04 AM UTC, comment #8: Honestly ? only files belong into tarball - symlinks might for one or other reason be invalid. Well, just my opinion.	Anonymous
Fri 06 Jul 2012 10:11:13 PM UTC, comment #7: > Does it work if you use "libtoolize -c -f" instead ? Yes, that's how I eventually managed to get my build going. Not sure if we should use that in autogen.sh...	Marko Lindqvist <cazfi>
Fri 06 Jul 2012 10:02:11 PM UTC, comment #6: Does it work if you use "libtoolize -c -f" instead ?	Anonymous
Fri 06 Jul 2012 09:20:14 PM UTC, comment #5: The libtoolize bug I referred to is the fact that "libtoolize -f" does not update m4 in my specific use case. Nothing to do with autogen.sh really, as I've not even used it in my latest tests but just "libtoolize -f" and "aclocal -I m4 -I dependencies/m4" directly. Yes, we should still change aclocal to run (also) after libtoolize in autogen.sh, but with that libtoolize bug it would't help as libtoolize really does nothing.	Marko Lindqvist <cazfi>
Fri 06 Jul 2012 08:30:27 PM UTC, comment #4: No. Again, right now autogen.sh works (in this regard) like this on such generated tarball: aclocal runs - it uses macros from m4/; aclocal.m4 gets generated libtoolize runs - ltmain.sh and macros in m4/ are updated ...but that doesn't update aclocal.m4 generated by aclocal. Anyway, autoreconf proves it's the expected behavior. With a recent enough automake it wouldn't probably matter as those m4_include macros in such dirs, but IIRC, that's only since automake 1.11. ... Wait, now that I think about it point 4 doesn't make sense, unless either timestamps are messed up or you force regeneration of configure script. Could you explain a bit more ?	Anonymous
Fri 06 Jul 2012 06:52:23 PM UTC, comment #3: There is "-f" passed to libtoolize in our autogen.sh after all, it just doesn't work under the circumstances. I think I've got bug to file against libtool.	Marko Lindqvist <cazfi>
Wed 04 Jul 2012 11:40:59 AM UTC, comment #2: Well, a part of the problem lies in autogen.sh script - it's just not complicated enough ;) Once libtoolize gets run after aclocal, aclocal needs to be run again (see autoreconf - that script does a bit too much in some places, not enough in the others, but in this case is quite clear). Also, as AC_CONFIG_MACRO_DIR is set and autogen.sh uses 'libtoolize -f' the macros should be overwritten. Does the failure still happen after applying above fix ? If so, could you attach the log.	Anonymous
Wed 04 Jul 2012 10:48:27 AM UTC, comment #1: There's more. The situation cannot be fixed by running autogen.sh in target system even if it has required tools (which would not be needed for ./configure && make). 1) aclocal is used to collect old macros from m4/ before libtoolize is used (see 2) to put new macros there 2) as macro files are already present (from tarball) and libtoolize is not forced to overwrite them, old macros remain in m4/	Marko Lindqvist <cazfi>
Tue 03 Jul 2012 06:31:05 PM UTC, original submission: 1. Have libtool 2.4.2 and freeciv svn checkout on computer A 2. ./autogen.sh && make dist 3. Transfer produced tarball to computer B with libtool 2.4 4. ./configure -> fail due to m4 macros being for different libtool version	Marko Lindqvist <cazfi>

(Note: upload size limit is set to 1024 kB, after insertion of the required escape characters.)

Attach File(s):


Comment:

No files currently attached

Depends on the following items: None found

Items that depend on this one: None found

Carbon-Copy List

-unavailable- added by cazfi (Submitted the item)

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

Please enter the title of George Orwell's famous dystopian book (it's a date):

No Changes Have Been Made to This Item

Show feedback again