This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

egcs build bug


This is definitely naughty. The error arises while running the configure
script.

[summer@bilby egcs-1.1.2]$ echo 'time buildCC >OverallLog 2>&1' | batch
warning: commands will be executed using /bin/sh
job 76 at 1999-12-15 11:07
[summer@bilby egcs-1.1.2]$ tail -f OverallLog

/mnt/mo/usr/egcs0/bin /mnt/mo/usr/egcs/bin ; /usr/bin/gcc ; egcs-2.91.66 ; CFLAGS=-O0
mkdir: cannot make directory `/usr/share/texmf/dvips': Permission denied
kpsestat: /usr/share/texmf/dvips/..: No such file or directory
chmod: too few arguments
Try `chmod --help' for more information.
mkdir: cannot make directory `/usr/share/texmf/dvips/config': No such file or directory
kpsestat: /usr/share/texmf/dvips/config/..: No such file or directory
chmod: too few arguments
Try `chmod --help' for more information.
/usr/bin/texconfig: /tmp/texconf3542/logfile: No such file or directory
Links are now set up to build a native compiler for i686-pc-linux-gnu


I'm building egcs from source, I'm not root and I don't have tetex-dvips
installed. I suggest the appropriate action is one of these;
1	Omit that part of the build
2	Barf, mentioning that that part of the build can be omitted with
.'configure --without-documentation' or some such.

I don' t know just what would happen if I ran this is root, but
the Red Hat rpm illustrated my point that one should not blindly download
any src.rpm and build it as root (we were discussing the question on a
mailing list).


 -- 
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]