572224 – dev-vcs/git: Calls gcc directly, breaking cross-arch distcc

Bug 572224 - dev-vcs/git: Calls gcc directly, breaking cross-arch distcc

Summary: dev-vcs/git: Calls gcc directly, breaking cross-arch distcc

Status:	RESOLVED OBSOLETE

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal
Assignee:	Robin Johnson

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2016-01-17 21:30 UTC by Michał Górny
Modified:	2020-12-07 07:31 UTC (History)
CC List:	1 user (show)

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

Attachments
Build log (dev-vcs:git-2.7.0-r2:20160117-211624.log,237.20 KB, text/x-log) 2016-01-17 21:30 UTC, Michał Górny	Details
View All 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 Michał Górny archtester

2016-01-17 21:30:16 UTC

Created attachment 423196 [details]
Build log

Long story short, the part compiling gnome-keyring support seems not to respect CC and call 'gcc' instead of 'i686-*-gcc'. As a result, I get mix of 32-bit and 64-bit objects via distcc.

Comment 1 Vineet Purswani 2016-03-14 06:22:44 UTC

Hi, I want to work on this bug. It seems to me that there is some minor change required in one of the make file but I am making a very uninformed guess. 

Kindly direct me where to start. Meanwhile, I'll be looking for it by myself.

Comment 2 Denis Dupeyron (RETIRED) gentoo-dev

2016-03-18 18:06:37 UTC

Note to Robin: Vineet is a potential GSoC student.

(In reply to Vineet Purswani from comment #1)
> Kindly direct me where to start. Meanwhile, I'll be looking for it by myself.

Vineet,

The motivation behind having you propose a solution to a bug here is to demonstrate you can research on your own and know how to use our tools. Giving you pointers would defeat the object of the exercise.

Denis.

Comment 3 Robin Johnson archtester

2020-12-07 07:31:47 UTC

I believe this ticket is obsolete, if the problem persists, please reopen