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

The testsuite cannot be run without installation #5483

Closed
vicuna opened this issue Jan 18, 2012 · 4 comments
Closed

The testsuite cannot be run without installation #5483

vicuna opened this issue Jan 18, 2012 · 4 comments

Comments

@vicuna
Copy link

vicuna commented Jan 18, 2012

Original bug ID: 5483
Reporter: @glondu
Assigned to: @xclerc
Status: closed (set by @damiendoligez on 2013-05-17T19:33:25Z)
Resolution: duplicate
Priority: normal
Severity: minor
Version: 3.13.0+dev
Target version: 4.00.1+dev
Fixed in version: 4.01.0+dev
Category: ~DO NOT USE (was: OCaml general)
Duplicate of: #5710
Monitored by: mehdi

Bug description

Currently (r12043), the testsuite assumes that ocaml has been installed. For example, it calls $PREFIX/bin/ocamlc, or ./program where program is a bytecode executable refering to $PREFIX/bin/ocamlrun.

Moreover, the testsuite somehow assumes that the compilation tree is still around. For example, it uses config/Makefile.

I would like to run the testsuite automatically as part of the Debian release process, on all supported architectures, but these shortcomings prevents it without multiple compilations (not counting bootstrap): the only workaround I can think of is to compile everything one time with a local $PREFIX for running the tests, and then with a global $PREFIX for the released binaries.

I don't know the details of gcc and (e)glibc, but the test-suite of coq (at least) can be run without recompiling a throw-away version of everything.

@vicuna
Copy link
Author

vicuna commented Jul 10, 2012

Comment author: @damiendoligez

We are now at r12681, and I think this has been fixed. Xavier?

@vicuna
Copy link
Author

vicuna commented Jul 11, 2012

Comment author: @alainfrisch

I've no idea whether this has been fixed or not, but since the test suite is not part of the distribution, I don't think this should be considering blocking for 4.00.

@vicuna
Copy link
Author

vicuna commented Jul 11, 2012

Comment author: @xclerc

One still has to install in order to run the test suite.

It should be possible to change that by playing with -nopervasives,
LD_LIBRARY_PATH and the like, but it is worth the trouble?

@vicuna
Copy link
Author

vicuna commented Aug 1, 2012

Comment author: @protz

Side-note: #5710 has a patch for that!

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

No branches or pull requests

1 participant