You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By overriding the local flags, libcs50 gets compiled withour RELRO for Archlinux.
Would RELRO (or other local flags) inhibit the functionality of libcs50? If not, would it be an option to not override local flags, but simply add the desired flags from the Makefile to the local flags?
I have applied the following patch to the Makefile to add the flags from Makefile to the local CFLAGS and LDFLAGS, instead of overriding the local flags (Linux only):
Not sure where else to ask this question. This is about the manual building of libcs50 on Linux:
The Makefile for libcs50 overrides the local CFLAGS and LDFLAGS. Is this desired behaviour?
The standard flags on Archlinux are currently:
CFLAGS="-march=x86-64 -O2 -pipe -fno-plt -fexceptions \ -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security \ -fstack-clash-protection -fcf-protection"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"
By overriding the local flags, libcs50 gets compiled withour RELRO for Archlinux.
Would RELRO (or other local flags) inhibit the functionality of libcs50? If not, would it be an option to not override local flags, but simply add the desired flags from the Makefile to the local flags?
I have applied the following patch to the Makefile to add the flags from Makefile to the local CFLAGS and LDFLAGS, instead of overriding the local flags (Linux only):
The text was updated successfully, but these errors were encountered: