Closed westerman closed 12 years ago
westerman
commented
12 years ago Ah, I think that this was caused by my sysadmins "hiding" the compile environment from me. At least on one of my systems. Now I am getting:
checking for open... no configure: error: The 'open' function is missing.
Ah well, time to bug my sysadmin.
dcjones
commented
12 years ago Your using an older version of autoconf than I am, which is the cause of the configure errors. I'll push a commit shortly to make those integer type checks optional.
Could you tell me the output of gcc --version. I might be passing a flag that's not supported by your version of gcc, which would explain the second error.
westerman
commented
12 years ago Hi Daniel. I've added my sysadmin Doug Yatcilla to this conversation because he was able to compile quip for me. It is possible that I was just doing something dumb. Doug: did you have to do anything special to get quip to compile and install?
As for your question:
gcc --version gcc (GCC) 4.4.0 Copyright (C) 2009 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Rick Westerman westerman@purdue.edu
On Aug 22, 2012, at 11:16 PM, Daniel Jones wrote:
Your using an older version of autoconf than I am, which is the cause of the configure errors. I'll push a commit shortly to make those integer type checks optional.
Could you tell me the output of gcc --version. I might be passing a flag that's not supported by your version of gcc, which would explain the second error.
— Reply to this email directly or view it on GitHub.
westerman
commented
12 years ago Daniel, my sysadmins reply is below.
I am now testing quip. Hope that it is doing something useful. It is slow.
----- Forwarded Message -----
On Thu Aug 23 07:12:16 2012, Rick Westerman westerman@purdue.edu wrote:
Hi Daniel. I've added my sysadmin Doug Yatcilla to this conversation because he was able to compile quip for me. It is possible that I was just doing something dumb. Doug: did you have to do anything special to get quip to compile and install?
Rick,
I downloaded this https://github.com/downloads/dcjones/quip/quip-1.1.1.tar.gz
I did not use autoconf since the configure file was already present. The test files were missing. Other than that, I saw no errors.
-Doug
Rick Westerman westerman@purdue.edu
Bioinformatics specialist at the Genomics Facility. Phone: (765) 494-0505 FAX: (765) 496-7255 Department of Horticulture and Landscape Architecture 625 Agriculture Mall Drive West Lafayette, IN 47907-2010 Physically located in room S049, WSLR building
dcjones
commented
12 years ago Ok, closing this issue. If it's running much slower than advertised please feel free to make a new issue.
quip-git> autoreconf -i ./git-version-gen: line 7: [: !=: unary operator expected ./git-version-gen: line 7: [: !=: unary operator expected configure.ac:19: error: possibly undefined macro: AC_TYPE_UINT8_T If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:20: error: possibly undefined macro: AC_TYPE_UINT16_T configure.ac:21: error: possibly undefined macro: AC_TYPE_INT32_T configure.ac:22: error: possibly undefined macro: AC_TYPE_UINT32_T configure.ac:23: error: possibly undefined macro: AC_TYPE_UINT64_T autoreconf: /usr/bin/autoconf failed with exit status: 1
I have not tried to debug this yet but line 7 can be avoid via putting $branch into quotes so that a null is not being compared. I do not know enough about autoconf to debug the rest.