Bug 177706 - dev-lang/ocaml 3.09.3 doesn't install *opt binaries
|
Bug#:
177706
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: ml@gentoo.org
|
Reported By: carlo@gentoo.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: dev-lang/ocaml 3.09.3 doesn't install *opt binaries
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-05-08 19:37 0000
|
/usr/bin/ocamlopt
/usr/bin/ocamldep.opt
etc. get not installed with this version. 3.09.2 is fine. Also I noticed that
the ocaml build script still relies on the X11R6 legacy symlinks, instead using
/usr/include/X11/ and /usr/$(get_libdir)/X11.
does -r1 or emerging it without "test" in your features solves the issue ?
it seems that phreak tracked that one to "make bootstrap" deleting *opt
binaries
Christian, can you confirm this ? I don't understand how "make bootstrap" can
be considered as a test anyway. make compare could be a test, but make
bootstrap seems really weird to me.
(In reply to comment #1)
> Christian, can you confirm this ? I don't understand how "make bootstrap" can
> be considered as a test anyway. make compare could be a test, but make
> bootstrap seems really weird to me.
Ned (solar) tracked these, yes .. somehow the make bootstrap (that's what
FEATURES=test does) removes the *opt files, and I haven't figured that out.
Yes, FEATURES=-test does it. Wonder why this ebuild got stable without
disabling the test, when this is apparently a known issue...
11 May 2007; Alexis Ballier <aballier@gentoo.org> ocaml-3.09.3.ebuild,
ocaml-3.09.3-r1.ebuild:
Dont run make bootstrap for src_test, it deletes ocamlopt, upstream does not
provide a clean test suite, if we want one we definitely should not use make
bootstrap, closes bug #159237 and bug #177706
(In reply to comment #3)
> Yes, FEATURES=-test does it. Wonder why this ebuild got stable without
> disabling the test, when this is apparently a known issue...
Well the issue is known since Ned tracked these, apparently not so long ago.
And don't ask me why it has gone stable with such a major issue ;)
*** Bug 176909 has been marked as a duplicate of this bug. ***