On Tue, Jun 12, 2018 at 03:01:52PM +0800, Fam Zheng wrote: > On Tue, 06/12 14:52, Peter Xu wrote: > > On Tue, Jun 12, 2018 at 02:41:19PM +0800, Fam Zheng wrote: > > > On Tue, 06/12 14:24, Peter Xu wrote: > > > > Hi, > > > > > > > > For example, I wanted to compile QEMU once and install it on multiple > > > > systems. What would be the suggested way to do so? > > > > > > > > Is there something similar to "make bin-rpmpkg" for Linux? > > > > > > > > Thanks in advance, > > > > > > No. The big question is the libraries. Even if you create the rpm, the > > > libraries > > > that you have linked against are not necessarily available on the systems > > > you > > > install. This means you either list all possible libraries as required in > > > the > > > rpm spec, which is a waste, or the list is generated dynamically, which > > > is not > > > trivial. For example, you can easily build QEMU against a custom glib, > > > but it's > > > very tricky to generate an rpm from it that works on other systems. > > > > That's true. But my question was actually specific to when the > > systems are sharing basically the same environment (kernel, library > > versions, etc.). A simple solution is that on each system I install > > qemu official package then the dependencies will all be there, then I > > install my custom package (which will possibly install the binaries > > under /usr/local) and I run the customized binary. > > Then simply do > > ./configure --prefix=/tmp/qemu-install && \ > make && \ > make install && \ > scp -r /tmp/qemu-install $remote > > ?
Yeh, maybe. :) But it'll still be good if we can have a single package to play around with. If there is no known way to do, we can try to figure a way out. -- Peter Xu
