Closed jeffhammond closed 8 years ago
The problem is a lingering remnant from your update. When there is a difference in the file system (e.g., a directory is removed), but you have built the code before and so there is build product in that directory, git doesn't remove it. Thus, autogen sees the common directory and looks for the Makefile.am that should be in it, but doesn't find it because that file no longer exists.
Bottom line: whenever you do an update to a branch like this, you should do a "git clean -dfx" before building to ensure that all the cruft gets removed.
I have not built the code and there is no build directory yet. Obviously, I cannot run configure
if autogen.pl
fails...
In any case, I can run autogen.pl
if I rm -rf * && git checkout .
, but I don't consider that an acceptable solution. This sort of issue has never happened with any other Autotools-based project I use...
The Open MPI project is pretty complex and dynamic. If you are working off of master or one of the other active git branches, you can expect this kind of behavior. One option to avoid these sorts of issues is to work off of the release tarballs at http://www.open-mpi.org/software/ompi/v1.10/ or friends. Then you don't need to use autogen.pl at all.
Or, as I said, you can just run "git clean -dfx" to remove any stale stuff and then run autogen et al. It's just a git artifact caused by having multiple branches in the same repo - when you change between them, the directories that are in one and not the other branch carry across. Thus, you have to remove them with the "clean" command.
@hppritcha
Yes, I'm aware of the benefits of rehearse tarballs every time I have to build the latest Autotools from source in order to configure MPICH ;-)
In this case, I'm hoping to diagnose a bug so that it can be fixed before 1.10 drops, in which case tracking Git will save me the trouble of starting from scratch if a patch is made available.
As far as I am concerned, I have three clones (master, v2.x and v1.10) and I never checkout from one branch to an other. that saves some time since I only run autogen.pl/configure when needed, and I do not run into these kind of troubles. I set remote repos, but I only use them for cherry-picking purpose. on my laptop, I also mirror ompi and ompi-release (git clone --mirror) so i do not have to connect multiple times to github when updating my clones.
my 0.02 US$
@ggouaillardet I don't have the luxury of making those space-time trade-offs:
$ df -h
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
/dev/disk1 233Gi 219Gi 13Gi 95% 57578528 3408991 94% /
This is the state of things after extensive pruning. As much as I'd love to delete my Windows VM to clear up 100 GB or so, it's essential to my day job :rage2:
Anyways, feel free to close this ticket. Now that I know the cause of the issue, I will be able to solve it whenever it appears again in the future.
PS If you did not already know about Wolfenstein emoji support on Github, you're welcome :octocat: :trophy: :unlock:
summary
I cannot being to even build the
v1.10
release branch from source becauseautogen.sh
fails.git info
Start with current v1.10
autogen.sh