From: merch-redmine@...
Date: 2014-12-01T16:59:01+00:00
Subject: [ruby-core:66624] [ruby-trunk - Bug #10554] preview2 fails to	generate prelude.c

Issue #10554 has been updated by Jeremy Evans.


Vit Ondruch wrote:
> Ok, this seems to be due to r48607 and associated commits. Looking at builds of Ruby 2.1, prelude.c was always generated, while now it is shipped as part of the tarball. And unfortunately, I consider this move in wrong direction, since inclusion of pregenerated prelude.c is more or less against Fedora's policy [2]. Yes, this paragraph is about pre-built binaries and libraries, but I believe that pre-generated code is the same in the same spirit.
> 
> Is there any technical reason, why the prelude.c should be pre-generated and shipped in the source tarball? Would you mind to remove it and let it be generated, as it always was? Thanks.

By this argument, the source tarball shouldn't contain parse.c, only parse.y, making bison a requirement for building.  And it shouldn't contain configure/Makefile, only configure.in/Makefile.in, making autoconf/automake a requirement for building.  Is it Fedora's policy to delete files generated by bison/autoconf/automake and regenerate them before compiling the software?  If not, why would prelude.c be any different?

----------------------------------------
Bug #10554: preview2 fails to generate prelude.c
https://bugs.ruby-lang.org/issues/10554#change-50239

* Author: Vit Ondruch
* Status: Open
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: ruby-2.2.0-preview2
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
~~~
generating prelude.c
echo executable host ruby is required.  use --with-baseruby option.; false ./tool/generic_erb.rb -I. -c -o prelude.c \
	./template/prelude.c.tmpl ./prelude.rb ./enc/prelude.rb ./gem_prelude.rb ./abrt_prelude.rb
executable host ruby is required. use --with-baseruby option.
uncommon.mk:780: recipe for target 'prelude.c' failed
~~~

I have no Ruby installed on my build machine. Last time I checked r48476, which was working just fine.




-- 
https://bugs.ruby-lang.org/