From: usa@...
Date: 2015-01-30T07:10:42+00:00
Subject: [ruby-core:67898] [ruby-trunk - Bug #8115] make install	DESTDIR=/my/install/path fails

Issue #8115 has been updated by Usaku NAKAMURA.

Backport changed from 2.0.0: REQUIRED, 2.1: DONE to 2.0.0: DONE, 2.1: DONE

ruby_2_0_0 r49444 merged revision(s) 41756.

----------------------------------------
Bug #8115: make install DESTDIR=/my/install/path fails
https://bugs.ruby-lang.org/issues/8115#change-51296

* Author: Vit Ondruch
* Status: Closed
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-linux]
* Backport: 2.0.0: DONE, 2.1: DONE
----------------------------------------
=begin
In Fedora packaging, we used to use (({make install DESTDIR=/my/install/path})) to install compiled extension into the folder, which RPM used to pick up the extension. However, since Ruby 2.0.0, this approach fails with message such as;

 make install DESTDIR=/builddir/build/BUILDROOT/ruby-mysql-2.8.2-9.fc20.i386
 make: *** No rule to make target `/builddir/build/BUILDROOT/ruby-mysql-2.8.2-9.fc20.i386/usr/include/ruby.h', needed by `mysql.o'.  Stop. 
 
Apparently, the mkmf creates Makefile, where everything depends on DESTDIR (see the diff of makefiles here [1]). This is wrong IMO, since obviously Ruby's header files location has nothing to do with location I'd like to install my libraries.

Could you fix this issue? Or if that was always wrong approach, could you provide us better one?

Please note that this was originally reported here: https://bugzilla.redhat.com/show_bug.cgi?id=921650

[1] https://gist.github.com/voxik/5186924
=end


---Files--------------------------------
Makefile (7.1 KB)
0001-mkmf-s-system-configuration-should-use-expanded-valu.patch (1 KB)


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