Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#28868 - [boost-build] add makepkg toolset

Attached to Project: Community Packages
Opened by Roman Matsybora (matsic) - Sunday, 11 March 2012, 13:34 GMT
Last edited by Jakob Gruber (schuay) - Wednesday, 14 March 2012, 16:08 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Jakob Gruber (schuay)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

It would be nice to add makepkg version to gcc toolset with options from makepkg.conf file in site-config.jam, so we can compile packages with predefined compile flags

for example it could be:
<<<
GCC_COMPILE_FLAGS = "-march=native -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2" ;
GCC_LINK_FLAGS = "-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu" ;
using gcc : makepkg : g++ : <cflags>$(GCC_COMPIPLE_FLAGS) <cxxflags>$(GCC_COMPILE_FLAGS) <linkflags>$(GCC_LINK_FLAGS) ;
>>>

with this toolset all packages compiled with boost-build will compile with
<<<
bjam toolset=gcc-makepkg
>>>
This task depends upon

Closed by  Jakob Gruber (schuay)
Wednesday, 14 March 2012, 16:08 GMT
Reason for closing:  Won't implement
Additional comments about closing:  I'd prefer not adding this kind of customization to official packages.
Comment by Jakob Gruber (schuay) - Wednesday, 14 March 2012, 13:51 GMT
Could you clarify what you mean? Which files are involved, how should the files be changed, etc..
Comment by Roman Matsybora (matsic) - Wednesday, 14 March 2012, 14:57 GMT
using gcc ;
GCC_MAKEPKG_COMPILE_FLAGS = "-march=native -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2" ;
GCC_MAKEPKG_LINK_FLAGS = "-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu" ;
using gcc : makepkg : : <cflags>$(GCC_MAKEPKG_COMPILE_FLAGS) <cxxflags>$(GCC_MAKEPKG_COMPILE_FLAGS) <linkflags>$(GCC_MAKEPKG_LINK_FLAGS) ;

# these lines can be added in 'site-config.jam'
Comment by Jakob Gruber (schuay) - Wednesday, 14 March 2012, 15:05 GMT
And the purpose of these lines is only to use these custom build flags when specifying toolset=gcc-makepkg?
I still don't see what makepkg has to do with this, since you seem to set the flags explicitly in that code snippet?
Comment by Roman Matsybora (matsic) - Wednesday, 14 March 2012, 15:28 GMT
if pakage builds with bjam, then we can write in build() function in PKGBUILD file:
build(){
cd "$srcdir/$pkgname-$pkgver"
bjam toolset=gcc-makepkg release
}

and we can use user's compilation flags for this

Loading...