Age | Commit message (Collapse) | Author |
|
|
|
allegedly more portable. Update .SRCINFO for new hashsums!
|
|
|
|
flags for new methods
|
|
graphite flags; output status messages from pgo
|
|
|
|
(extreme and unsafe optimization)
|
|
with whitespace, reduce complexity, use safer methods to set flags)
|
|
|
|
dozen packages with no problems whatsoever, the code stopped working as documented. NOT THE FIRST TIME BASH, WTF??
|
|
-fno-fat-lto-objects
|
|
|
|
filenames
|
|
|
|
|
|
|
|
|
|
in optipng-exec.sh.in
|
|
pkgbase.gen; makes checking for INFAKEROOT irrelevant--which may have been irrelevant anyway)
|
|
|
|
|
|
compression.
|
|
pacman-buildenv_ext-git
|
|
|
|
|
|
|
|
|
|
|
|
|
|
link to archwiki
|
|
deal with my out-of-date troll and pacman-build_env-ext
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Some programs say the compiler is broken when using PGO or LTO,
but really they just have a particular preference for how they
are fed whitespace.
|
|
|
|
The makepkg.conf included here represents some of my own
configuration choices. It is not intended to stay here however;
once the next version of pacman rolls out, I intend to import
users' own makepkg.conf (and makepkg) for the basis to patch on.
|
|
the compiler cannot create executables. I think it is innapropriate
whitespace or other disruption getting into a variable.
|
|
tremendous pressure that's been on me lately. Every single post
has me nervous to the bone; which high-profile personality is going
to forcibly silence me over nothing next?
|
|
|
|
The two sections of makepkg.conf split nicely: build options, and
package options--so let's use file names like that. Also comment
on graphite in config.
|