X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Jim Michaels Newsgroups: comp.os.msdos.djgpp Subject: Re: errors using C++ libraries Date: Fri, 2 Jan 2009 01:15:40 -0800 (PST) Organization: http://groups.google.com Lines: 80 Message-ID: <24847567-cad8-4c1e-ac21-dc24ae7f06c3@v39g2000pro.googlegroups.com> References: <21cb02cc-b32a-4057-b191-8dcd61624c63 AT p2g2000prf DOT googlegroups DOT com> <9e625b31-0599-4156-90c1-0d98aeba94c4 AT e6g2000vbe DOT googlegroups DOT com> NNTP-Posting-Host: 76.115.70.155 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: posting.google.com 1230887740 1560 127.0.0.1 (2 Jan 2009 09:15:40 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: Fri, 2 Jan 2009 09:15:40 +0000 (UTC) Complaints-To: groups-abuse AT google DOT com Injection-Info: v39g2000pro.googlegroups.com; posting-host=76.115.70.155; posting-account=05hOMwoAAAB6R8xtiQKzEljSMzgOhVF1 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5,gzip(gfe),gzip(gfe) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id n029U585002984 Reply-To: djgpp AT delorie DOT com On Jan 1, 9:14 am, Rugxulo wrote: > Hi, > > On Dec 31 2008, 4:55 pm, Jim Michaels wrote: > > > > > this thing hit send all by itself.  as I was saying, before, I was > > able to compile programs just fine.  now I can't.  I haven't changed > > anything. > > I don't know - maybe the mcafee antivirus or webroot spysweeper got a > > hold of something and deleted it, but that seems farfetched. > > What GCC/G++ are you using? (4.2.3? 4.3.2?) What DJDEV? (2.03? 2.04?) > What BinUtils? (2.16.1? 2.17? 2.19?) What OS? (MS-DOS 7.10? FreeDOS? > WinXP?) Are you using an LFN-aware system or not? Did you unpack on an > LFN-aware system? Did you upgrade any DJGPP packages to newer versions > recently? Is your %DJGPP% env. variable still set correctly? Did your > DJGPP.ENV file get modified recently? > > I usually keep .ZIP archives of all DJGPP packages in case I want to > reinstall or copy to another computer or whatever. This might be a > good idea for you in the future, at least for the core stuff (GCC, > GPP, BNU, DJDEV, MAK). F:\DJGPP>gpp --version gpp.exe (GCC) 4.1.0 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. C:\DJGPP>gpp --version gpp.exe (GCC) 4.2.3 Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. C:\DJGPP> I think I am using 2.04 for the one on c: and 2.03 for the one on f:. OS: XP Pro SP3. (OS=Windows_NT) on f: (2.03) binutils 2.17. on c: binutils 2.17 (actually what I did was expand them all. XP expands them alphabetucally so they are done in order of lower version to higher version#). > WinXP?) Are you using an LFN-aware system or not? Did you unpack on an > LFN-aware system? That is not relevant to XP. XP does not respond to changes in the registry for LFN. that is for win9x. So yeah, it was probably LFN- aware. NT family systems mangle the long filepaths into tildes with a number into 8.3. I saw a microsoft KB article that says you can't change that. tried it using command.com, same errors. gpp.exe: environment variable DJGPP points to corrupt file 'f:/djgpp/ 2.03/v2/djg pp.env' C:\PRJ\MD5\MD5-1.0\DOS>dir f:\djgpp\2.03\v2\djgpp.env The system cannot find the path specified. (I do not know where to get the file from) Did you upgrade any DJGPP packages to newer versions no. I downloaded everything all at once and installed what I got. > recently? Is your %DJGPP% env. variable still set correctly? Did your I use 2 separate djenv files, one on c:\ and one on f:\ > DJGPP.ENV file get modified recently? no. I set it up and left it. I don't want to touch something that is running well. and it was running well up until now for some odd reason.