Just as a follow-up, I tried compiling apache + mod_ssl with aggressive i686 optimizations myself. The packages compiled and installed cleanly, but when I tried to access a page, the server seg-faulted. So, I guess the moral here is to be extremely careful what optimization flags you provide. -- John Ross Hunt bigboote@mediaone.net mailto:bigboote@mediaone.net
I would suggest using SuSE's source RPM for apache (it's in the zq1 series). It has everything set up for apache + mod_ssl. All you have to do is download the appropriate module from modssl.org, comment out the 'NoSource:' directive in apache.spec, and rebuild. They have the '$RPM_OPT_FLAGS' set up correctly in the spec file, so if your ~./rpmrc file is valid, the '--target=i686' qualifier should work correctly.
Good luck,
-- John Ross Hunt bigboote@mediaone.net mailto:bigboote@mediaone.net
John:
I did like you said and created the .rpmrc file in the home directory. I read in the manual where it talked about that.
When I execute the command:
rpm -ba --target=i686
and I watch the output of the file compiling, I keep seeing one of the flags as -m486 among the other flags. Is this misleading, or is there something I'm missing. This first RPM I'm working with is the source code for apache + mod_ssl. I've written the RPM, and now I would like to be able to take advantage of the fact that I'm on a Pentium II machine. Does passing these flags to RPM insure that I will be building it for that different architecture, or do i need to "prepare" the actual apache and mod_sll source code to take advantage of it too?
- Mike
On Sat, 1 Jul 2000, John Bigboote wrote:
The system-wide config file is usually /usr/lib/rpm/rpmrc. You should never modify it directly though. In your home directory, create a file called ~/.rpmrc and make your customizations there. Here's a quick example:
-- ~/.rpmrc -- optflags: i686 -O9 -mpentiumpro -mcpu=pentiumpro -fstrength-reduce -fexpensive-optimizations -finline-functions -fomit-frame-pointer -funroll-loops -ffast-math -foptimize-register-move -fdefer-pop -mfancy-math-387 -- end --
If the package uses './configure' make sure there is a CFLAGS="$RPM_OPT_FLAGS" in your .spec file preceding the ./configure statement like this:
CFLAGS="$RPM_OPT_FLAGS" ./configure [--other-options]
If not, the 'optflags' above won't make have any effect. Now, try building your package with the --target statement:
rpm -ba --target=i686 mypackage.spec
Ok, we now know enough to be dangerous. :) Definitely check out rpm.org, the rpm documentation project and of course gcc documentation. The gcc optimizations used in the preceding example are very aggressive could break some programs. They should be used with caution.
http://www.rpm.org/ http://rpmdp.org/rpmbook/ http://gcc.gnu.org/
-- John Ross Hunt bigboote@mediaone.net mailto:bigboote@mediaone.net
Afternoon:
Does anyone out there have experience rebuilding RPMS? I'm thinking of recompiling some of the RPMS I have to i586 or i686 status. I've got gcc-2.95 installed, so I believe I can take advantage of the pentium optimizations.
My understanding is that there is a config file that should edited to tell the system when I execute a:
rpm -ba
to take advantage of those optimizations. Any leads?
- Mike
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
John: Would you be willing to send me your SRC RPM? I always like to compare what I come up with to how other people do stuff. Who knows, if mine works, I'll be happy to show you what I did. - Mike On Sun, 2 Jul 2000, John Bigboote wrote:
Just as a follow-up, I tried compiling apache + mod_ssl with aggressive i686 optimizations myself. The packages compiled and installed cleanly, but when I tried to access a page, the server seg-faulted. So, I guess the moral here is to be extremely careful what optimization flags you provide.
-- John Ross Hunt bigboote@mediaone.net mailto:bigboote@mediaone.net
I would suggest using SuSE's source RPM for apache (it's in the zq1 series). It has everything set up for apache + mod_ssl. All you have to do is download the appropriate module from modssl.org, comment out the 'NoSource:' directive in apache.spec, and rebuild. They have the '$RPM_OPT_FLAGS' set up correctly in the spec file, so if your ~./rpmrc file is valid, the '--target=i686' qualifier should work correctly.
Good luck,
-- John Ross Hunt bigboote@mediaone.net mailto:bigboote@mediaone.net
John:
I did like you said and created the .rpmrc file in the home directory. I read in the manual where it talked about that.
When I execute the command:
rpm -ba --target=i686
and I watch the output of the file compiling, I keep seeing one of the flags as -m486 among the other flags. Is this misleading, or is there something I'm missing. This first RPM I'm working with is the source code for apache + mod_ssl. I've written the RPM, and now I would like to be able to take advantage of the fact that I'm on a Pentium II machine. Does passing these flags to RPM insure that I will be building it for that different architecture, or do i need to "prepare" the actual apache and mod_sll source code to take advantage of it too?
- Mike
On Sat, 1 Jul 2000, John Bigboote wrote:
The system-wide config file is usually /usr/lib/rpm/rpmrc. You should never modify it directly though. In your home directory, create a file called ~/.rpmrc and make your customizations there. Here's a quick example:
-- ~/.rpmrc -- optflags: i686 -O9 -mpentiumpro -mcpu=pentiumpro -fstrength-reduce -fexpensive-optimizations -finline-functions -fomit-frame-pointer -funroll-loops -ffast-math -foptimize-register-move -fdefer-pop -mfancy-math-387 -- end --
If the package uses './configure' make sure there is a CFLAGS="$RPM_OPT_FLAGS" in your .spec file preceding the ./configure statement like this:
CFLAGS="$RPM_OPT_FLAGS" ./configure [--other-options]
If not, the 'optflags' above won't make have any effect. Now, try building your package with the --target statement:
rpm -ba --target=i686 mypackage.spec
Ok, we now know enough to be dangerous. :) Definitely check out rpm.org, the rpm documentation project and of course gcc documentation. The gcc optimizations used in the preceding example are very aggressive could break some programs. They should be used with caution.
http://www.rpm.org/ http://rpmdp.org/rpmbook/ http://gcc.gnu.org/
-- John Ross Hunt bigboote@mediaone.net mailto:bigboote@mediaone.net
Afternoon:
Does anyone out there have experience rebuilding RPMS? I'm thinking of recompiling some of the RPMS I have to i586 or i686 status. I've got gcc-2.95 installed, so I believe I can take advantage of the pentium optimizations.
My understanding is that there is a config file that should edited to tell the system when I execute a:
rpm -ba
to take advantage of those optimizations. Any leads?
- Mike
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (2)
-
bigboote＠mediaone.net -
mike＠universe.ne.mediaone.net