Bug 462276

Summary:	net-misc/curl-7.29.0-r1 on hardened with -D_FORTIFY_SOURCE in CFLAGS - configure: CFLAGS error: CFLAGS may only be used to specify C compiler flags, not macro definitions. Use CPPFLAGS for: -D_FORTIFY_SOURCE=2
Product:	Gentoo Linux	Reporter:	Bruno <bonbons>
Component:	Current packages	Assignee:	Anthony Basile <blueness>
Status:	RESOLVED INVALID
Severity:	normal	CC:	gregkh
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	config.log emerge --info build.log

Description Bruno 2013-03-19 08:58:31 UTC

Configure script of curl bails out complaining about presence of macro definitions in CLFAGS. It complains about -D_FORTIFY_SOURCE=2.


checking for x86_64-pc-linux-gnu-ar... /usr/bin/x86_64-pc-linux-gnu-ar
configure: using CFLAGS: -O2 -pipe -march=core2 -fstack-protector-all -D_FORTIFY_SOURCE=2 -fstack-protector-all -D_FORTIFY_SOURCE=2 -fstack-protector-all -D_FORTIFY_SOURCE=2 -fstack-protector-all -D_FORTIFY_SOURCE=2
configure: CFLAGS error: CFLAGS may only be used to specify C compiler flags, not macro definitions. Use CPPFLAGS for: -D_FORTIFY_SOURCE=2
configure: CFLAGS error: CFLAGS may only be used to specify C compiler flags, not macro definitions. Use CPPFLAGS for: -D_FORTIFY_SOURCE=2
configure: CFLAGS error: CFLAGS may only be used to specify C compiler flags, not macro definitions. Use CPPFLAGS for: -D_FORTIFY_SOURCE=2
configure: CFLAGS error: CFLAGS may only be used to specify C compiler flags, not macro definitions. Use CPPFLAGS for: -D_FORTIFY_SOURCE=2
configure: error: Can not continue. Fix errors mentioned immediately above this line.



Reproducible: Always

Comment 1 Bruno 2013-03-19 09:01:16 UTC

Created attachment 342610 [details]
config.log

Comment 2 Bruno 2013-03-19 09:01:36 UTC

Created attachment 342612 [details]
emerge --info

Comment 3 Anthony Basile gentoo-dev

2013-03-21 13:16:35 UTC

Use CPPFLAGS for -D_FORTIFY_SOURCE=2 doesn't sound right.  Can you attatch the build log?

Comment 4 Bruno 2013-03-21 13:28:19 UTC

Created attachment 342842 [details]
build.log

Comment 5 Anthony Basile gentoo-dev

2013-03-24 18:44:09 UTC

(In reply to comment #4)
> Created attachment 342842 [details]
> build.log

Okay this occurs if you have CFLAGS="-D_FORTIFY_SOURCE=2" anywhere in your environment.  Can you see if you have that in your make.conf?  Or maybe somewhere else you in system?  There's nothing for me to do with curl since curl never touches _FORTIFY_SOURCE and it does respect CPP/CFLAGS.

Comment 6 Bruno 2013-03-25 20:50:20 UTC

(In reply to comment #5)
> Okay this occurs if you have CFLAGS="-D_FORTIFY_SOURCE=2" anywhere in your
> environment.  Can you see if you have that in your make.conf?  Or maybe
> somewhere else you in system?  There's nothing for me to do with curl since
> curl never touches _FORTIFY_SOURCE and it does respect CPP/CFLAGS.

I had it in CFLAGS/CXXFLAGS via /etc/portage/bashrc (), dating back from early hardening some longer time ago.
Removed it from there as hardened gcc profile is expected to handle it. With that fixed, curl compile.

Comment 7 Anthony Basile gentoo-dev

2013-03-26 12:00:32 UTC

(In reply to comment #6)
> (In reply to comment #5)
> > Okay this occurs if you have CFLAGS="-D_FORTIFY_SOURCE=2" anywhere in your
> > environment.  Can you see if you have that in your make.conf?  Or maybe
> > somewhere else you in system?  There's nothing for me to do with curl since
> > curl never touches _FORTIFY_SOURCE and it does respect CPP/CFLAGS.
> 
> I had it in CFLAGS/CXXFLAGS via /etc/portage/bashrc (), dating back from
> early hardening some longer time ago.
> Removed it from there as hardened gcc profile is expected to handle it. With
> that fixed, curl compile.

thanks.