Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 24115 - mozilla 1.4 ebuild fails
Summary: mozilla 1.4 ebuild fails
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Mozilla Gentoo Team
URL:
Whiteboard:
Keywords:
: 24136 24162 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-07-08 11:32 UTC by Andreas Kotowicz
Modified: 2003-07-10 07:02 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Kotowicz 2003-07-08 11:32:49 UTC
../../../config/nsinstall -R -m 644 libipc_s.a ../../../dist/lib
make[2]: Leaving directory
`/usr/local/mp3/vartmp/portage/mozilla-1.4/work/mozilla/extensions/ip c/src'
make[1]: Leaving directory
`/usr/local/mp3/vartmp/portage/mozilla-1.4/work/mozilla/extensions/ip c'
>>> Copying /etc/skel/.tcsh.config to your home directory ...
cp: cannot create regular file `/root/.tcsh.config': Permission denied
>>> Please edit it to fine-tune the TCSH behaviour.
/usr/local/mp3/vartmp/portage/mozilla-1.4/work/mozilla/extensions/enigmail
/usr/local/mp3/vartmp /portage/mozilla-1.4/work/mozilla/extensions/enigmail
/usr/local/mp3/vartmp/portage/mozilla-1.4/work/mozilla/extensions/enigmail
ex: Command not found.
/usr/local/mp3/vartmp/portage/mozilla-1.4/work/mozilla/extensions/enigmail
Makefile:43: @top_srcdir@/config/config.mk: No such file or directory
Makefile:45: @top_srcdir@/config/rules.mk: No such file or directory
make: *** No rule to make target `@top_srcdir@/config/rules.mk'.  Stop.
Comment 1 Martin Holzer (RETIRED) gentoo-dev 2003-07-08 12:22:55 UTC
do you run emerge as root ?

if no, do it
Comment 2 Kurt 2003-07-08 13:58:22 UTC
I had a problem with building mozilla 1.4 the first time.  My build gave me problems about having /bin/csh as an invalid interpreter.  So emerge csh and then the build worked just fine.
Comment 3 Matti Rendahl 2003-07-08 15:46:35 UTC
I had the same problem, don't know where the "cp: cannot create regular file `/root/.tcsh.config': Permission denied" came from (was root), but I saw the "ex: Command not found." and after 'emerge vi' it built ok. So the ebuild really should depend on 'vi'...

Comment 4 Terje Kvernes 2003-07-08 17:10:54 UTC
I ran into the csh-bug as well, with csh missing.  Mozilla should also depend
on some c-shell of some incarnation as well.

sigh, I had to merge a csh.  :-)
Comment 5 Martin Holzer (RETIRED) gentoo-dev 2003-07-09 00:24:35 UTC
*** Bug 24136 has been marked as a duplicate of this bug. ***
Comment 6 Andreas Kotowicz 2003-07-09 01:09:55 UTC
I did run emerge as root
Comment 7 Guy 2003-07-09 03:07:22 UTC
I also ran emerge as root (bug # 24136)

Note: 'tcsh' was already on my system previously and was upgraded as part of 'emerge -u --deep world'

Regarding 'csh': -------------------------------------------------

emerge -p csh

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild  N   ] sys-devel/pmake-1.45-r2
[ebuild  N   ] app-shells/csh-1.29-r1

As I see it, there are two possibilities I can try after I get back home from work.

1) 'emerge csh'

2) 'emerge unmerge tcsh' then 'emerge (previous version) tcsh'

followed by 'emerge -u mozilla'

Do you have a preference as to which would be more meaningful to you? It's a little painful to compile mozilla even on my system. So I'm not so eager to try both possibilities. ;-)

Or, I can wait to test the 'fixed' ebuild. This is not a problem.
Comment 8 Guy 2003-07-09 03:12:04 UTC
BTW - I do _not_ have VI or VIM installed on this system.

emerge -p vi

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild  N   ] sys-libs/libtermcap-compat-1.2.3
[ebuild  N   ] app-editors/vi-3.7-r3

# emerge -p vim

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild  N   ] dev-util/cscope-15.3
[ebuild  N   ] app-editors/vim-core-6.2-r1
[ebuild  N   ] app-editors/vim-6.2

Comment 9 Andres Toomsalu 2003-07-09 03:56:18 UTC
Same problem? 
------------------------------------- 
../../../config/nsinstall -R -m 644 libipc_s.a ../../../dist/lib 
make[2]: Leaving directory `/var/tmp/portage/mozilla-1.4/work/mozilla/extensions/ipc/src' 
make[1]: Leaving directory `/var/tmp/portage/mozilla-1.4/work/mozilla/extensions/ipc' 
/var/tmp/portage/mozilla-1.4/work/mozilla/extensions/enigmail 
/var/tmp/portage/mozilla-1.4/work/mozilla/extensions/enigmail 
/var/tmp/portage/mozilla-1.4/work/mozilla/extensions/enigmail 
ex: Command not found. 
/var/tmp/portage/mozilla-1.4/work/mozilla/extensions/enigmail 
Makefile:43: @top_srcdir@/config/config.mk: No such file or directory 
Makefile:45: @top_srcdir@/config/rules.mk: No such file or directory 
make: *** No rule to make target `@top_srcdir@/config/rules.mk'.  Stop. 
 
!!! ERROR: net-www/mozilla-1.4 failed. 
!!! Function src_compile, Line 396, Exitcode 2 
!!! (no error message) 
 
Comment 10 Marc Doughty 2003-07-09 04:37:49 UTC
I've got this bug too.
Comment 11 someone 2003-07-09 05:44:52 UTC
The problem is the missing "ex" in the ./makemake in enigmail. This is part of "vim". Install vim, build mozilla and unmerge "vim" to feel safe again... ;)
Comment 12 Brad Laue (RETIRED) gentoo-dev 2003-07-09 09:54:44 UTC
The mozilla ebuild now depends on tcsh, which fixes the first problem. Emerge rsync to grab it.

The missing 'ex' problem is more difficult as a virtual will have to be created. Multiple packages satisfy the 'ex' binary.
Comment 13 Brad Laue (RETIRED) gentoo-dev 2003-07-09 16:09:54 UTC
The purpose of running ./makemake was to simplify matters, unfortunately it created lots more than it should.

I have created an enigmail Makefile which was the practice of previous releases of enigmail upstream. Mozilla no longer has a build dependency on either vi or csh.
Comment 14 Brad Laue (RETIRED) gentoo-dev 2003-07-10 07:02:05 UTC
*** Bug 24162 has been marked as a duplicate of this bug. ***