17126 – db-3.2.9-r1 fails, if ${CC} is not defined

Bug 17126 - db-3.2.9-r1 fails, if ${CC} is not defined

Summary: db-3.2.9-r1 fails, if ${CC} is not defined

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	High normal (vote)
Assignee:	Martin Schlemmer (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-03-09 02:58 UTC by Michal Maruska
Modified:	2003-08-22 13:34 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 Michal Maruska 2003-03-09 02:58:31 UTC

the ebuild contains this code:
/bin/sh ./libtool --mode=compile ${CC} -c ${CFLAGS} -D_GNU_SOURCE  ...
which needs ${CC} defined. If it is not, it fails w/ a cryptic error -c not valid fro libtool.   however the next line is:
gcc -s -static ... 
Is the ${CC} necessary, if then  fixed "gcc" is used ?

Reproducible: Always
Steps to Reproduce:
1. unsert CC
2. emerge db
3.

Comment 1 Martin Schlemmer (RETIRED) gentoo-dev

2003-03-09 10:00:53 UTC

Please try db-3.2.9-r2.

If on a x86 box, you can do:

  # ACCEPT_KEYWORDS="~x86" emerge db

Comment 2 Zach Welch (RETIRED) gentoo-dev

2003-03-09 16:09:13 UTC

Is there any reason not to bump -r2 to stable?

Comment 3 Martin Schlemmer (RETIRED) gentoo-dev

2003-03-09 17:13:31 UTC

No reason I can think of.  It fixes a few problems, and *should* have been tested
ok.

Comment 4 Georg Sauthoff 2003-05-01 02:49:12 UTC

Hi,

why is db-3.2.9-r2 not marked as stable yet?

Comment 5 Martin Schlemmer (RETIRED) gentoo-dev

2003-08-22 13:34:07 UTC

-r2 is long time stable already.