Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, guys
how can I get the configuration of a rpm?
for example, whatI have is bash-2.05b-20.i366.rpm only, no spec file, how can I get the compilation options for bash?
a common way will be highly preferred!
thanks for your detail,
Distribution: Switched to regualr Ubuntu, because I don't like KDE4, at all. Looks like vista on crack.....
Posts: 675
Rep:
I think you want to download the source for the package you want, and compile from source. Then you can do whatever you want. RPM will limit your options a bit, in exchange for convenience.
I think you want to download the source for the package you want, and compile from source. Then you can do whatever you want. RPM will limit your options a bit, in exchange for convenience.
Best of luck
David
yes, the *.src.rpm has a spec file which has the detailed parameters,
Here is an example on how to build it
2.3.10. Build BASH
Get the bash-2.05 source code package from ftp://ftp.gnu.org/gnu/bash/ and untar it into the /usr/src directory.
Note
BASH version 2.05b, the latest version at the time of this writing, will not build successfully when using the --enable-minimal-config option. This leaves two choices. We can either fix 2.05b by applying the patch posted on gnu.bash.bug under the subject, "Compile error in execute_cmd.c with --enable-minimal-config" or we can simply use the 2.05a version.
bash# cd /usr/src/bash-2.05a
bash# ./configure --enable-static-link \
--enable-minimal-config --host=i386-pc-linux-gnu
bash# make
bash# strip bash
I found that here, I think they are building boot floppys from scratch
With any GNU program, like bash, you can always get the source, somewhere. A src.RPM is just a system to package the source code. The RPM is just a system to package the already built binary. Hope that makes sense.
I noticed that nobody answered the original posters question: "how can I get the compilation options" from a binary installed from an RPM.
I am stuck with the same problem. I need to figure out which flags and configure options fedora used to compile a package because I need to mimic them in an different environment. Does anyone have a clue how to do this? It seems idiotic to not include the compile options within the package meta data Am I just missing it?
As was stated above it is in the srpm. If you used the standard Fedora repos they also carry the srpms for everything. Take a look at the files in /etc/yum.repos.d/ . If you edit those files you will see that there is also a srpm repo within them. They are shut off (enable=0) by default.
Maybe I'm misunderstanding source RPMs. When I downloaded the src.rpm package for openssh I gain access to the 'spec' file which not only contains a list of the valid configuration parameters that fedora uses but also tons of branch statements which alters the configuration parameters used depending on the libraries installed on the system:
I'm not interested in compiling a custom binary of a package tailored to the exact development libraries I have installed on my machine (I can do that with source from the original developers). I specifically want to know what flags and parameters the fedora crew threw in when they prepared and compiled their binary. Do you see the difference? I'm trying to debug a problem and need to do some forensics on a current working implementation not run the fedora script which determines which flags it needs to set to compile a completely different binary on my machine.
The php binary is a fantastic example of what I'm looking for. If you run /usr/bin/php -i you'll be bombarded with all sorts of useful information including the configuration command used like so:
Again, the specific question posed remains unanswered. If the answer is "Nope, you can't get the configuration/compile parameters used from a pre-compiled binary RPM," that's OK with me. I just have to find another way around my problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.