From:	"jonathan bailey" <jbailey8 AT triad DOT rr DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	latest info on gcc3 compile
Lines:	41
X-Newsreader:	Microsoft Outlook Express 4.72.3110.5
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID:	<Qnc_6.29184$Md.8681725@typhoon.southeast.rr.com>
Date:	Wed, 27 Jun 2001 03:26:40 GMT
NNTP-Posting-Host:	24.163.5.158
X-Complaints-To:	abuse AT rr DOT com
X-Trace:	typhoon.southeast.rr.com 993612400 24.163.5.158 (Tue, 26 Jun 2001 23:26:40 EDT)
NNTP-Posting-Date:	Tue, 26 Jun 2001 23:26:40 EDT
Organization:	RoadRunner - Triad
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hello All,
Well, I've been spending the last hour or so trying all the other
suggestions sent to me so far reguarding the ./specs permission
denied problem, and this is what I've found out so far:

If I delete the specs file in my installed gcc dir (u:\djgppv2\lib) I get
the following response from the xgcc in e:\gcc-3.0\gcc:

command: xgcc.exe -v

Using builtin specs.
Configured with: configure  : (reconfigured) configure --prefix=u:/djgppv2 :
(reconfigured) configure --prefix=/dev/env/DJDIR
Thread model: single
gcc version 3.0

If I then re-run 'make bootstrap', I still get the permission denied error

If I put the specs file back in place in my installed gcc dir, I get the
following:

command: xgcc.exe -v

Reading specs from ./specs
xgcc.exe: ./specs: Permission denied (EACCES)

I even tried manually typing in the same command line that make
is trying to execute with xgcc and replacing 'xgcc' with 'gcc' (the one
in my installed dir), and then the specs permission denied problem
goes away, but then there are other problems. But this is expected
since I'm then using the wrong gcc. This strongly suggests there is
something wrong with xgcc.exe and/or it's being passed incorrect
parameters. At the moment I'm stumped, I don't have a clue as to
what's going on. If anyone can figure this out, I'll be grateful. I even
had a response saying that I might have to wait until the official gcc 3.0
binaries are out. The sender may be right...
                                               john
jbailey8 AT triad DOT rr DOT com

- Raw text -