Bug#476027: ocaml-shout: FTBFS: make[3]: *** No rule to make target `Makefile.shoutfile'. Stop.
Le Monday 14 April 2008 12:24:28 Lucas Nussbaum, vous avez écrit :
> This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is
> now the default on most architectures (even if it's not the case on i386
> yet). Feel free to downgrade this bug to 'important' if your package is
> only built on i386, and this bug is specific to gcc 4.3 (i.e the package
> builds fine with gcc 4.2).
>
> Relevant part:
> > make[3]: Entering directory `/build/user/ocaml-shout-0.2.5/examples'
> > make[3]: Makefile.shoutfile: No such file or directory
> > make[3]: *** No rule to make target `Makefile.shoutfile'. Stop.
> > make[3]: Leaving directory `/build/user/ocaml-shout-0.2.5/examples'
> > make[2]: *** [clean-shoutfile] Error 2
No, this is not, the relevant part is:
> ./configure --host=i486-linux-gnu --build=i486-linux-gnu --prefix=/usr
> --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info configuring
> ocaml-shout 0.2.5
> checking for ocamlc... /usr/bin/ocamlc
> ocaml version is 3.10.1
> ocaml library path is /usr/lib/ocaml/3.10.1
> checking for ocamlopt... /usr/bin/ocamlopt
> checking ocamlopt version... ok
> checking for ocamlc.opt... no
> checking for ocamlopt.opt... no
> checking for ocamldep... /usr/bin/ocamldep
> checking for ocamllex... /usr/bin/ocamllex
> checking for ocamlyacc... /usr/bin/ocamlyacc
> checking for ocamldoc... /usr/bin/ocamldoc
> checking for ocamlmktop... /usr/bin/ocamlmktop
> checking for i486-linux-gnu-gcc... i486-linux-gnu-gcc
> checking for C compiler default output file name...
> configure: error: C compiler cannot create executables
So, exactly the same as the dozen of other serious report we just get.
Now, for the issue itself, I'm pretty surprised since it seems to fail in
something that is not really relevant for either the package or the software,
the configure script.
We rely on general and external functions, so there are two possibilities:
(1) We need to regenerated those scripts
(2) There is something broken between configure and gcc 4.3
(3) There was something broken in your build configuration.
I tend to think it would have been more clever to find out if (2) oe (3) is
the culprit, since all the reports would not be in the good place in this
case.
I'll try to look at this.
Romain
--
Could not recognize the faces standing over me;
They were all dressed in uniforms of brutality.
Reply to: