Arch Linux

nstgc

Member

Registered: 2014-03-17

Posts: 393

[Solved] Merging makepkg.conf -- CFLAGS question

pacman was upgraded today and with it is a makepkg.conf.pacnew. I ran pacdiff, and saw that the difference, aside from the "-j6" make flag, was "--param=ssp-buffer-size=4" in both CFLAGS and CXXFLAGS. I'm not sure what this does, or if it is desirable. Since I don't recall setting this myself, I figure I should probably remove it. Could anyone confirm?

[edit] The answer is "yes", do what seems right.

Last edited by nstgc (2015-10-06 00:29:12)

graysky

Wiki Maintainer

From: :wq

Registered: 2008-12-01

Posts: 10,731

Website

Re: [Solved] Merging makepkg.conf -- CFLAGS question

Yes, foo.bar.pacnew is what the the package provides and should always be diffed against foo.bar with you intelligently merging the changes.

---

AUR packages • Zsh and other configs

ayekat

Member

Registered: 2011-01-17

Posts: 1,632

Re: [Solved] Merging makepkg.conf -- CFLAGS question

There is a gcc flag -fstack-protector, which emits extra code for preventing buffer overflows for buffers with a size of more than 8 bytes (e.g. an 32-bit integer array with 2 or more elements), also called "stack smashing".

In case you use that flag, there is -ssp-buffer-size, which changes that minimum size to 4 bytes, and it was probably considered to be a sane default by the package maintainers (I usually leave package configurations as default as possible if I don't know what they're there for, or I don't have any reason why I would want it otherwise).

---

pkgs │ hacks │ cfg │ blag

Raynman

Member

Registered: 2011-10-22

Posts: 1,539

Re: [Solved] Merging makepkg.conf -- CFLAGS question

https://projects.archlinux.org/svntogit … ges/pacman

Check last two commits with links to bug reports.

nstgc

Member

Registered: 2014-03-17

Posts: 393

Re: [Solved] Merging makepkg.conf -- CFLAGS question

Okay, thank you all.