Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error compiling fastQValidator #12

Open
denisemauldin opened this issue Apr 26, 2016 · 6 comments
Open

Error compiling fastQValidator #12

denisemauldin opened this issue Apr 26, 2016 · 6 comments

Comments

@denisemauldin
Copy link

Compiling libStatGen doesn't throw any errors, but when compiling fastQValidator, it does:

g++ -std=c++0x -O4 -pipe -Wall -I/tools/src/libStatGen//include -I. -D__ZLIB_AVAILABLE__ -D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS -o ../bin/fastQValidator ../obj/FastQValidator.o /tools/src/libStatGen//libStatGen.a -lm -lz
/tools/src/libStatGen//libStatGen.a(GzipFileType.o): In function GzipFileType::GzipFileType(char const*, char const*)': GzipFileType.cpp:(.text+0xdf): undefined reference togzopen64'
/tools/src/libStatGen//libStatGen.a(GzipFileType.o): In function GzipFileType::seek(long, int)': GzipFileType.cpp:(.text._ZN12GzipFileType4seekEli[GzipFileType::seek(long, int)]+0x9): undefined reference togzseek64'
/tools/src/libStatGen//libStatGen.a(GzipFileType.o): In function GzipFileType::tell()': GzipFileType.cpp:(.text._ZN12GzipFileType4tellEv[GzipFileType::tell()]+0x5): undefined reference togztell64'

@mktrost
Copy link
Contributor

mktrost commented Apr 27, 2016

Do you have the development version of zlib installed?

@denisemauldin
Copy link
Author

Yes. 1.2.8. I was incorrect though and it's libStatGen that's throwing the error. The compile doesn't show anything, but the tests fail. I had to manually add the -L/tools/lib directory containing -lz to the Makefiles/Makefile.include. Not sure if there's something you can do to detect that. It is in my LD_LIBRARY_PATH.

@jonathonl
Copy link
Contributor

On which OS are you building?

@denisemauldin
Copy link
Author

CENTOS. Mostly I think it's that I have my updated libraries in a different path (/tools) rather than in the system paths.

@jonathonl
Copy link
Contributor

So adding "-L/tools/lib" solved your problem then? Or are you still getting errors when building the tests?

@denisemauldin
Copy link
Author

Yes, adding -L/tools/lib solved my problem. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants