Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 728980 - mail-client/neomutt: calls GCC directly
Summary: mail-client/neomutt: calls GCC directly
Status: RESOLVED DUPLICATE of bug 724716
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Nicolas Bock
Depends on:
Blocks: tc-directly 728302
  Show dependency tree
Reported: 2020-06-21 09:27 UTC by Agostino Sarubbo
Modified: 2020-07-05 07:52 UTC (History)
1 user (show)

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

build.log (build.log,72.97 KB, text/plain)
2020-06-21 09:27 UTC, Agostino Sarubbo

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2020-06-21 09:27:47 UTC
@@This is an auto-filed bug@@
If you think that a different summary clarifies the issue better, feel free to change it.

Issue: mail-client/neomutt fails to compile.
Discovered on: amd64

If you need further logs, feel free to ask.
Comment 1 Agostino Sarubbo gentoo-dev 2020-06-21 09:27:52 UTC
Created attachment 645488 [details]

build log and emerge --info
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2020-06-23 01:04:11 UTC
This line made me suspicious, because it looks like it's giving compiler args:
>false -I. -std=c99 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 
> -D__EXTENSIONS__   \
> -o docs/makedoc ./docs/makedoc.c

... it's trying to call /usr/bin/gcc (not cc?) directly, and its absence causes CC_FOR_BUILD to become false.

This ends up in the Makefile:
# Build-time compiler and flags. These are used for building executables that
# are only used at build-time, e.g., docs/makedoc. These are different from CC /
# CFLAGS / LDFLAGS because the host and target systems might be different.

I would say CC_FOR_BUILD should be $(CC_FOR_BUILD) or, if it does not exist, $(CC).
Comment 3 Agostino Sarubbo gentoo-dev 2020-07-05 07:52:08 UTC

*** This bug has been marked as a duplicate of bug 724716 ***