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

Can't install prodigal #8

Open
mortonjt opened this issue Oct 20, 2015 · 4 comments
Open

Can't install prodigal #8

mortonjt opened this issue Oct 20, 2015 · 4 comments

Comments

@mortonjt
Copy link
Contributor

Got this error when trying to install prodigal

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/mortonjt/Documents/micronota/micronota/bfillings/tests/test_prodigal.py", line 75, in test_predict_genes_wrong_input
    predict_genes(fp, self.temp_dir, 'foo')
AssertionError: "Sequence read failed \(file must be Fasta, Genbank, or EMBL format\)." does not match "Unacceptable application exit status: 1
Command:
cd "/home/mortonjt/Documents/micronota/micronota/bfillings/"; prodigal -d "/tmp/tmpei3o_9q3/foo.fna" -i "/home/mortonjt/Documents/micronota/micronota/bfillings/tests/data/empty" -o "/tmp/tmpei3o_9q3/foo.gbk" -a "/tmp/tmpei3o_9q3/foo.faa" > "/tmp/tmpFQMWrZcnRv8owY5dGdxd.txt" 2> "/tmp/tmpIUmEUFyqgxMcDOnPgbrt.txt"
StdOut:

StdErr:
prodigal: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by prodigal)
@RNAer
Copy link
Collaborator

RNAer commented Oct 22, 2015

@Jorge-C, is there a way to specify the library to compile against in recipe?

@Jorge-C
Copy link
Member

Jorge-C commented Oct 22, 2015

@mortonjt what OS, installation process?

@mortonjt
Copy link
Contributor Author

mortonjt commented Nov 8, 2015

Sorry about the late response. I was installing against Redhat linux.

@Jorge-C
Copy link
Member

Jorge-C commented Nov 9, 2015

Ah, this is actually not surprising.

If we take advantage of travis (i.e., ubuntu 12.04, which is already old-ish) to build packages, we get glibc 2.14, which works on any {d|r}ecent desktop linux. However, it doesn't work in older/more stable server OS (think Red Hat, CentOS...).

IMO, travis is too nice to pass it up (do we really want to maintain a build farm?). If we want to build binaries that work in servers and keep using travis, I think we can explicitly make the packages depend on an old glibc (see this recipe).

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