Bug 168260

Summary:	sys-libc/glibc-2.4-r4 fails to build with -D_FILE_OFFSET_BITS=64 in CFLAGS
Product:	Gentoo Linux	Reporter:	Marco Clocchiatti <ziapannocchia>
Component:	New packages	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	RESOLVED INVALID
Severity:	normal	CC:	vladimir
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge info + emerge log

Description Marco Clocchiatti 2007-02-24 19:49:34 UTC

emerge glibc does not compile.

compilation done in a chrooted 32bit environment, from an amd64 one.
`emerge -e system` fails on glibc.
same behaviour (re)compiling glibc-2.4-r4
doing revdep-rebuild does not helps.

other information in the attachments.

Reproducible: Always

Steps to Reproduce:
1. emerge glibc

or

1. emerge -e system

Actual Results:  
glibc fails on compile

Expected Results:  
I'hope to compile

Comment 1 Marco Clocchiatti 2007-02-24 19:57:05 UTC

Created attachment 111145 [details]
emerge info + emerge log

Comment 2 Marco Clocchiatti 2007-02-25 01:24:02 UTC

The new summary is wrong.
please change:

"both glibc-2.5 and glibc-2.4-r4 fails to build" or something else.

Comment 3 Marco Clocchiatti 2007-02-25 12:52:47 UTC

same behaviour booting directly in 32-bit environment.
chroot seems to be not related with this issue.

Comment 4 SpanKY gentoo-dev

2007-02-26 01:21:26 UTC

remove -D_FILE_OFFSET_BITS=64 from your CFLAGS

Comment 5 Marco Clocchiatti 2007-02-26 12:19:39 UTC

sorry if I reopen the bug, just to precise a particular and to do a question.
In my system, glibc-2.4-r4 is correctly compiled with "-D_FILE_OFFSET_BITS=64".

s939 ~ # bzcat /var/db/pkg/sys-libs/glibc-2.4-r4/environment.bz2 |grep CFLAGS_BASE=|tail -n2
CFLAGS_BASE='-O2 -march=i686 -fomit-frame-pointer -pipe -D_FILE_OFFSET_BITS=64'
    CFLAGS_BASE=${CFLAGS_BASE-${CFLAGS}};

May be, the problem arise from the new gcc version, which would be uncompatible with it.
anyway, you are rigth. moving the wrong CFLAG, glibc compiles fine.

I use -D_FILE_OFFSET_BITS=64 because, some time ago, some programs (such as wget) had problems with long size files.

so, that's the question:
Today, does make it sense to hold this flag, or you suggest to remove it forever?

Comment 6 Kevin F. Quinn (RETIRED) gentoo-dev

2007-03-02 12:24:48 UTC

Never put -D<something> to define a macro in CFLAGS (for one thing, it breaks gcj).  If they go anywhere, it should be CPPFLAGS.  As for -D_FILE_OFFSET_BITS=64, if a package failed without it, bug about that package, don't set it globally (it's likely a configure failure for the affected package).

Comment 7 Jakub Moc (RETIRED) gentoo-dev

2007-08-08 19:53:37 UTC

*** Bug 188164 has been marked as a duplicate of this bug. ***