Mail Archives: djgpp/2002/11/18/13:15:14
Jonquil wrote:
>
> JMK <jeffrey DOT m DOT klopotic AT lmco DOT nospam DOT com> wrote in message news:<3DD577AC DOT 3BF46C58 AT lmco DOT nospam DOT com>...
> > > Shaymaa, the original error was in your program, but
> > > the new error you are describing:
> > >
> > > > Installation error, cannot exec 'as': No such file
> > > > or directory (ENENOT)
> > >
> > > sure sounds like an installation problem (as JMK
> > > originally suggested, ironically). So I'm forwarding
> > > your message back to the DJGPP mailing list for the
> > > suggestions of folks much more knowledgable than I am
> > > about these matters.
> > >
> > > Best regards,
> > >
> > > Tom
> > >
> > > __________________________________________________
> > > Do you Yahoo!?
> > > Yahoo! News - Today's headlines
> > > http://news.yahoo.com
> >
> > Shaymaa,
> >
> > The installation may not have gone correctly such that your compiler
> > cannot find the files it needs.
>
> how do i know which files? i succesfully unzipped everything.:
> these are the files that i downloaded.
>
> C:\> mkdir djgpp
> C:\> cd djgpp
> C:\DJGPP> unzip32 d:\tmp\djdev203.zip
> C:\DJGPP> unzip32 d:\tmp\faq230b.zip
> C:\DJGPP> unzip32 d:\tmp\rhid149b.zip
> C:\DJGPP> unzip32 d:\tmp\bnu213b.zip
> C:\DJGPP> unzip32 d:\tmp\fil41b.zip
> C:\DJGPP> unzip32 d:\tmp\gcc32b.zip
> C:\DJGPP> unzip32 d:\tmp\gpp32b.zip
> C:\DJGPP> unzip32 d:\tmp\mak3791b.zip
> C:\DJGPP> unzip32 d:\tmp\txi42b.zip
> C:\DJGPP> unzip32 d:\tmp\ntlfn08b.zip
> C:\DJGPP> unzip32 d:\tmp\all402.zip
> C:\DJGPP> unzip32 d:\tmp\grx245s.zip
>
> > Check your environment variable. The instructions are in the readme.1st
> > file in the djgpp directory. From a DOS window, check and see if correct
> > by typing "set djgpp". You should be able to get to the file djgpp.env
> > with that directory string.
>
> yes, it worked with me, i got the right path for it.
>
> > Also check your path by typing "path" and verify that your path command
> > is correct. A quick way to check is go to some directory other than
> > djgpp and try typing "gcc". It should return with "No input files". If
> > it complains about "gcc is not recognized...", your path command needs
> > repair.
>
> both worked.
> i checked the path, it was correct, but why did they write it three
> times like this: PATH HEREEEEEEEEEEEEEEEEEE
> i typed in djgpp and i got: "no input files."
This is good. But if you next try compiling a simple "hello world" type
app, it should compile if you supply a file, i.e.,
gcc -o hello.exe hello.cpp // should give you a hello.exe program or
reasons why not
with hello.cpp being the sample "hello world" app of Stroustrup, Special
Edition, p.46:
#include<iostream>
int main()
{
std::cout<<"Hello World\n";
}
It should compile and *not* give you the ENOENT error.
If you get ENOENT, there is a system issue -- something is not pointing
to your includes. A commandline method of addressing the issue is to
use the include command when you compile/link,
gcc -o hello.exe hello.cpp -I ./subdir1/subdir2/includes
...........................^include switch with additional path to
search
>
> > Finally, if you are installed on Windows NT, there is an issue with long
> > filenames that can also cause such problems. If you unzip with other
> > than djgpp's unzip, you may need to get a zipfile ntlfnXX.zip (XX is a
> > version number).
>
> i am using windows Xp and in the readme_1st file it says to use the
> unzip32.exe or any program that supports long file names. i used
> unzip32.exe and it worked. they told me to check for a certain file
> that if found, means you did it correctly. i found mine.
then long filenames shouldn't be an issue, but then again.... could it
be a regional problem with the OS version you are using? maybe
something I don't see with the version I'm at. That could mean you need
to check more locally.
>
> >
> > Hope this helps.
> >
> > Jeff
>
> thank you very much Jeff. i read the posts for my original question
> and to me it seems that maybe because i have gcc-3.2 and we were
> always using i think 2.9.. the way i understood it is that the formats
> are different but i used the one for 3.2 like the std::cout<<"Hello
> World"; and it still didnt work...
If you got the ENOENT message again, the next place to check is the .env
file or any other resource that points to where your includes are.
In the meantime, glad it helped to some extent. If you find out what it
was, I'd be interested to find out.
Jeff
>
> thanks again for your help.
>
> Regards,
> Shaymaa
- Raw text -