First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 172225
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: optical media herd <media-optical@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Ihar `Philips` Filipau <thephilips@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 172225 depends on: Show dependency tree
Bug 172225 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-03-25 20:08 0000
cdrkit build (cmake bases) uses simple compiler name - "c++" - instead of fully
qualified one.

That breaks cross and/or distributed compilations.

Reproducible: Always

------- Comment #1 From Lars Weiler (RETIRED) 2007-03-25 23:16:09 0000 -------
Hmm, sounds like an error due to the 'which-cleanup' discussion on gentoo-dev. 
It seems I have to find another way for telling cmake the correct
compiler-path.

------- Comment #2 From Ihar `Philips` Filipau 2007-03-25 23:41:56 0000 -------
Care to elaborate? I'm developer - I might understand what you say ;-)

Why good old 'CC="ccache distcc gcc" make love' doesn't work? I'm not familiar
with cmake, but my understanding was that it doesn't care much and just picks
as $(CC) whatever it is told.

------- Comment #3 From Lars Weiler (RETIRED) 2007-04-01 21:51:05 0000 -------
This should be fixed with cdrkit-1.1.4.

cmake was missing a variable for the location of c++, so it ever took the
default, just "c++" instead of something else given by the environment.

Please test.

------- Comment #4 From Ihar `Philips` Filipau 2007-04-03 00:43:16 0000 -------
I have tried it now and it works.

Though my cdrkit is at version 1.1.2.

First Last Prev Next    No search results available      Search page      Enter new bug