Right, I got it fixed and theres 2 things:
PKZIP had set up a user variable named PATH that was set to " "C:\Program
Files\PKWARE\PKZIPC\" " which was appended on the end of the system path. This
just repeated an earlier entry.
Removing the "'s from the path let make find the correct path.
--
On 01 February 2008 13:56, Richard Head wrote:
Right, so...
> D:\Current_Work\Stand Alone Image Fusion\Image Fusion Toolkit>gcc -v
> Reading specs from /usr/lib/gcc/i686-pc-cygwin/3.4.4/specs
> Configured with: /usr/build/package/orig/test.respin/gcc-3.4.4-3/configure
> --ver bose --prefix=/usr
> Ok, show us: cut and paste the actual output from your shell when you run
> the following commands:
>
> path
> which -a gcc
> gcc -v
> ls -la /bin/gcc
>
> cheers,
> DaveK
Here you go (enjoy ;) ):
PATH=C:\MentorGraphics\2005EXP\SDD_HOME\common\win32\bin;C:\MentorGraphics\2005E
XP
On Fri, Feb 01, 2008 at 01:41:48PM +, Richard Head wrote:
>> What kind of "not working"? If it's still saying "Not found", then it's
>> got
>> to be not in the path after all; if it's some other error message now, tell
>> us
>> which?
>
>Still saying gcc: command not found, and d:\cygwin\b
On 01 February 2008 13:42, Richard Head wrote:
>> What kind of "not working"? If it's still saying "Not found", then it's
>> got to be not in the path after all; if it's some other error message now,
>> tell us which?
>>
>
> Still saying gcc: command not found, and d:\cygwin\bin is def in th
> What kind of "not working"? If it's still saying "Not found", then it's got
> to be not in the path after all; if it's some other error message now, tell us
> which?
>
Still saying gcc: command not found, and d:\cygwin\bin is def in the path.
--
Unsubscribe info: http://cygwin.com/ml
On 01 February 2008 13:03, Richard Head wrote:
> How stupid of me.
> Main.c was in the wrong directory *slaps forehead*.
D'oh! ~(_8^(|)
> As for the gcc command not being found, that wasnt in the path, but now it
> is, and its still not working. Odd.
What kind of "not working"? If it's
How stupid of me.
Main.c was in the wrong directory *slaps forehead*.
As for the gcc command not being found, that wasnt in the path, but now it is,
and its still not working. Odd. Maybe Ill just stick with the cywin shell
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Prob
On 01 February 2008 12:12, Richard Head wrote:
>> Are you running make from Cygwin's shell or from the Windows command line
>> shell instead?
>
> Windows Command Line.
>
> Ive just tried it in the Cygwin shell and I get the same first error. The
> 2nd has gone away (It can find gcc now!)
So,
El Friday 01 February 2008 13:11:53 Richard Head escribió:
> > Are you running make from Cygwin's shell or from the Windows command line
> > shell instead?
>
> Windows Command Line.
>
> Ive just tried it in the Cygwin shell and I get the same first error. The
> 2nd has gone away (It can find gcc no
>
> Are you running make from Cygwin's shell or from the Windows command line
> shell instead?
Windows Command Line.
Ive just tried it in the Cygwin shell and I get the same first error. The 2nd
has gone away (It can find gcc now!)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-
El Friday 01 February 2008 12:38:30 Richard Head escribió:
> Hi, first post in here.
>
> Im not a very experienced C programmer, and Im fiddling with make. I
> have the following make file (entitled Makefile):
>
> fusionTK.exe : main.o fusionFileIO.o fusionAlgorithms.o
> gcc main.o fusionFi
alex hardy wrote:
Cygwin cannot find make command
That's because you didn't install it. Rerun setup and choose the
make package. Anticipating your next problem, you may want to
consider installing the gcc and gdb packages too.
--
Larry Hall http://www.rfk.com
RFK Par
13 matches
Mail list logo
