Bug 9213 – Mozilla build 1.0.1-r1 fails

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Alexander Isacson 2002-10-16 15:37:59 UTC]

This is what I get.

gcc -o FillRect.o -c -DOSTYPE=\"Linux2.4\" -DOSARCH=\"Linux\" -DOJI   
-I../../../dist/include/Xrender/X11/extensions -I../../../dist/include
-I/var/tmp/portage/mozilla-1.0.1-r1/work/mozilla/dist/include/nspr         
-fPIC -I/X11/extensions -I./extensions   -include ../../../config-defs.h
-DMOZILLA_CLIENT -Wp,-MD,.deps/FillRect.pp FillRect.c
In file included from Composite.c:26:
Xrenderint.h:33: Xext.h: No such file or directory
In file included from FillRect.c:26:
Xrenderint.h:33: Xext.h: No such file or directory
In file included from Composite.c:26:
Xrenderint.h:36: renderproto.h: No such file or directory
make[3]: *** [Composite.o] Error 1
make[3]: *** Waiting for unfinished jobs....
In file included from FillRect.c:26:
Xrenderint.h:36: renderproto.h: No such file or directory
make[3]: *** [FillRect.o] Error 1
make[3]: Leaving directory
`/var/tmp/portage/mozilla-1.0.1-r1/work/mozilla/other-licenses/Xft/Xrender'
make[2]: *** [libs] Error 2
make[2]: Leaving directory
`/var/tmp/portage/mozilla-1.0.1-r1/work/mozilla/other-licenses/Xft'
make[1]: *** [tier_9] Error 2
make[1]: Leaving directory `/var/tmp/portage/mozilla-1.0.1-r1/work/mozilla'
make: *** [default] Error 2

!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 124, Exitcode 2
!!! (no error message)

[Comment 1 Martin Schlemmer (RETIRED) 2002-10-17 17:45:51 UTC]

Add the following to bottom of src_unpack() function, or wait for rsync
to update the ebuild:

--------------------------------------------------------------------------
    cd ${S}/other-licenses/Xft/Xrender
    ln -s /usr/X11R6/include/X11/extensions/Xext.h Xext.h
    ln -s /usr/X11R6/include/X11/extensions/renderproto.h renderproto.h
--------------------------------------------------------------------------

[Comment 2 Martin Schlemmer (RETIRED) 2002-12-01 07:33:33 UTC]

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