Josh Saddler

Post details: New Guide

27 June, 2007

06:14 UTC, by Josh Saddler

, 171 words, 1291 views

Categories: Gentoo

New Guide

And now, breaking news in this special report:

I added my Compilation Optimization Guide to our documentation repository just a few moments ago, finally closing Bug 68282. Finally, we have something written down that we've been telling our users on the forums, on Bugzilla, the mailing lists, and IRC for years now. You may consider it definitive.

And no, we won't link to that unofficial wiki floating around. And no, your flags of -fomg-optimize and -funroll-all-loops won't be added to it.

With those caveats, have fun reading! Note that we have always had CFLAG suggestions for all our arches in their respective installation handbooks, that's why the guide doesn't duplicate the list in the GCC handbook.

...we now return you to your previously scheduled distribution checklist broadcast.

News flash!

I added yet another guide to Portage, one that was initially contributed by a user and a few developers some time ago, this one is a vpnc howto. It finally closes Bug 97760 and Bug 30966.

Man, this is some week for closing old bugs.

Permalink 9 comments • Trackback (0)

Trackback address for this post:

http://planet.gentoo.org/developers/htsrv/trackback.php/1353

Comments, Trackbacks:

Comment from: strohel [Visitor]

· http://strohel.bockelman.eu/

Good work, Josh. I always wanted a place where I can point rookies playing with weird CFLAGS. Thanks. (I know, there is plenty of that on gentoo-wiki, but I somehow prefer the "official" docs despite this one is maybe too offensive)

Permalink 27 June, 2007 @ 11:49

Comment from: gregf [Visitor]

Same as above great to have something to point anyone new people to. Have managed to convert a few friends to Gentoo over the years and usually one of the first questions is cflags.

Permalink 27 June, 2007 @ 14:53

Comment from: Francesco [Visitor]

Broken link?

Permalink 27 June, 2007 @ 15:18

Comment from: Xavier Neys [Visitor]

· http://gentoo.neysx.org

we have always had CFLAG suggestions for all our arches in their respective installation handbooks

The above statement is wrong. We've always had x86 CFLAGS duplicated in all handbooks.
I added arch-specific CFLAGS on March 10, 2007

Thanks for the now gcc-optimization.xml guide BTW.

Permalink 27 June, 2007 @ 16:41

Comment from: Josh Saddler [Member]

· http://dev.gentoo.org/~nightmorph

@neysx: Well, "always" is relative.

@Francesco: I temporarily fixed the link to the doc in the post...

Permalink 27 June, 2007 @ 18:03

Comment from: Caster [Visitor]

> Portage cannot use CFLAGS on a per-package basis, nor is there any supported method of forcing it to do so. The flags you set in /etc/make.conf will be used for all packages you install.

/etc/portage/bashrc is not considered "supported"?

Permalink 27 June, 2007 @ 21:22

Comment from: Josh Saddler [Member]

· http://dev.gentoo.org/~nightmorph

@caster:

Not that I've heard of. The most I've heard of is solar's hack to make it work, but I've never heard of it being officially supported or being an official feature. AFAIK, using bashrc is just a way to trick Portage into doing something it shouldn't.

Permalink 27 June, 2007 @ 21:50

Comment from: Francois [Visitor]

About the by package thing.
There is now a way to make it work.
I am not sure it is related to bashrc. It does work as I have used it on numerous occasions. For example on ppc until recently we couldn't compile openoffice.org with any cflags. Which was tiring because you had to change /etc/make.conf every time and you could forget to revert.
The simple solution for that kind of problem is to create a file called
/etc/portage/env/app-office/openoffice
and put CFLAGS="" in it.
This can be made version specific by appending version number.
I have used this on x86 and ppc.

Permalink 28 June, 2007 @ 19:57

Comment from: Hanno [Visitor]

· http://www.hboeck.de/

About LDFLAGS: the guide writes we don't support any of them.

I don't know if we could call this "supported", but at least we accept bugs for LDFLAGS="-Wl,--as-needed", because this is a QA-issue and often leads to makefiles that are broken anyway. So I guess you should mention that.

Permalink 29 June, 2007 @ 17:05

Post details: New Guide

27 June, 2007

New Guide

Trackback address for this post:

Comments, Trackbacks: