2647 – GCC2.95 / GCC3 make.defaults

Bug 2647 - GCC2.95 / GCC3 make.defaults

Summary: GCC2.95 / GCC3 make.defaults

Status:	RESOLVED INVALID

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High normal
Assignee:	Daniel Robbins (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-05-10 19:59 UTC by Pierre-Olivier Bouchard
Modified:	2011-10-30 22:17 UTC (History)
CC List:	0 users

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 Pierre-Olivier Bouchard 2002-05-10 19:59:10 UTC

It would be better to keep the make.defaults the same for the gcc2.95 and gcc3
profiles the same... right now they realy don't produce the same kind of system,
some new use variables are in the 2.95 profile and some deprecated ones exist in
the gcc3 one.

It's really annoying to have to replace the old, gcc3 make.defaults with a good
one each time I emerge rsync, some way to prevent overwriting of newer files, or
config-file protect for profiles could be really useful IMO.

Comment 1 Bart Verwilst 2002-07-05 13:02:44 UTC

Make.defaults are almost identical.. If you use the USE in make.conf right, 
this should be no problem at all..