518156 – CPPFLAGS should be explained in documentation

Bug 518156 - CPPFLAGS should be explained in documentation

Summary: CPPFLAGS should be explained in documentation

Status:	UNCONFIRMED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Enhancement/Feature Requests (show other bugs)
Hardware:	All Linux

Importance:	Normal minor with 1 vote (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-07-26 11:19 UTC by Artem Leshchev
Modified:	2021-05-03 22:09 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Artem Leshchev 2014-07-26 11:19:37 UTC

emerge --info shouldn't warn that CPPFLAGS is unset or make.conf documentation should explain for what it used. Now it can be confused with CXXFLAGS by usual user and set to ${CFLAGS}, what breaks some ebuilds. If it will be explained bugs like bug 518510 will not ever exist.

Comment 1 Samuli Suominen (RETIRED) gentoo-dev

2014-07-26 11:26:56 UTC

Sorry, but you misunderstood me in the bug. It's OK to set proper CPPFLAGS, but you shouldn't put CFLAGS or CXXFLAGS to CPPFLAGS

Comment 2 Artem Leshchev 2014-07-26 11:28:11 UTC

I think it should be explained anyway so it will not be set to optimization flags.