Pelles C forum
C language => Windows questions => Topic started by: syntel on March 08, 2017, 05:45:03 PM
-
Hi Folks:
This is my first post here.
1. I use PellesC as a basis for building a high level C language (Harbour) along with several other base C Languages (e.g., MinGW, Borland's C, and Visual C)
2. Recently I updated my PellesC from Version 7 to version 8, and have severe problems related to the Installation Directory.
3. In all previous upgrades and installs, I install my PellesC to C:\PellesC> . However, the default directory is C:\Program files (x86) which I override with the browse button and substitute C:\PellesC.
4. However, when installing to this directory, and when running my standard programs using the new version 8 of PellesC, I crash ! (This happens in sub-dir c:\pellesc\include\win\stralign.h in line 118).
5. If, however, I install to the default directory (c:\program files (x86), it works correctly with no crash -- and there is *no* stralign.h file existing in the default installation !!??
So, I conclude that different files are downloaded to my machine depending on whether I accept the default download directory or whether I substitute a different directory.
Can someone explain this please ?? (Or can someone tell me how to patch my installation to get around this crash at my preferred installation directory)
Thanks !
Mel Smith
(I have done several different installs(and uninstalls) of PellesC over the past week, and in each case scrubbing the registry of the Pelles setting too)
-
Normal PellesC installation don't have stralign.h
msvc, fSDK and others have it.
poide have option -xml for private settings in xml format.
-
TimoVJL said:
>Normal PellesC installation don't have stralign.h
>msvc, fSDK and others have it.
>poide have option -xml for private settings in xml format.
Hi:
My installation *did* have stralign.h when I installed in C:\Pellesc. Is is obvious to me that changing the default installation results in different files being downloaded.
Question: *Why* are there different files for a different directory ?? And does nobody care about these differences, and the reason for this ?? Also, how can the option -xml help me with this problem?
But anyway, thank you for the response.
-Mel Smith
www.whosaway.com
-
Hello Mel,
Nice job your Harbour. :)
As far as we can see the 'standard' PellesC package, as Timo already said, doesn't have 'stralign.h'.
Maybe it has been left in the installation directory from the former release. I'll check as soon I have time (sorry, but I'm a little bit busy this time). Could you please post the 'stralign.h' header from your folder so I can have a look to it?
Anyway there is something strange in your system because the installer, before to propose any 'default directory' checks where PellesC was installed before and then propose this directory (not the standard one). Maybe there are many installations that confuse the registers keys.
You may want try to remove all installations and clean the registry (using one of the tools available around) before to reinstall.
I understand that it is annoying to deal with this problems, but please consider that this is a free tool, we are few people and your problem is never happened before. So all support and cooperation to solve it is appreciated. ;)
-
Hello Mel,
Nice job your Harbour. :)
As far as we can see the 'standard' PellesC package, as Timo already said, doesn't have 'stralign.h'.
Maybe it has been left in the installation directory from the former release. I'll check as soon I have time (sorry, but I'm a little bit busy this time). Could you please post the 'stralign.h' header from your folder so I can have a look to it?
Anyway there is something strange in your system because the installer, before to propose any 'default directory' checks where PellesC was installed before and then propose this directory (not the standard one). Maybe there are many installations that confuse the registers keys.
You may want try to remove all installations and clean the registry (using one of the tools available around) before to reinstall.
I understand that it is annoying to deal with this problems, but please consider that this is a free tool, we are few people and your problem is never happened before. So all support and cooperation to solve it is appreciated. ;)
Hi Frankie:
As I noted before, I completely clean out my system between installs. Even to the point of going to the registry and deleting the associated keys.
But I will do it again and re-install with C:\PELLESC> as the install directory, then provide a list of the files in the c:\pellesc\include\win sub-dir.
Thanks for the response !
-Mel Smith
www.whosaway.com
-
Hello Mel,
Nice job your Harbour. :)
As far as we can see the 'standard' PellesC package, as Timo already said, doesn't have 'stralign.h'.
Maybe it has been left in the installation directory from the former release. I'll check as soon I have time (sorry, but I'm a little bit busy this time). Could you please post the 'stralign.h' header from your folder so I can have a look to it?
Anyway there is something strange in your system because the installer, before to propose any 'default directory' checks where PellesC was installed before and then propose this directory (not the standard one). Maybe there are many installations that confuse the registers keys.
You may want try to remove all installations and clean the registry (using one of the tools available around) before to reinstall.
I understand that it is annoying to deal with this problems, but please consider that this is a free tool, we are few people and your problem is never happened before. So all support and cooperation to solve it is appreciated. ;)
Hi Frankie:
As I noted before, I completely clean out my system between installs. Even to the point of going to the registry and deleting the associated keys.
But I will do it again and re-install with C:\PELLESC> as the install directory, then provide a list of the files in the c:\pellesc\include\win sub-dir.
Thanks for the response !
-Mel Smith
www.whosaway.com
Hi Frankie & Timo:
SUCCESS !!!
1. I ran uninst2.exe, then uninst.exe
2. Deleted c:\Program Files (x86)\PellesC sub-dir
2a. Also deleted c:\users\syntel\documents\Pelles C Projects sub-dir
3. Created an empty directory: C:\PELLESC>
4. Downloaded and installed a Registry Cleaner (Piriform v5.27.5976)
5. Ran the 'registry cleaner'.
5a. Re-booted my Win 7 Pro machine.
6. Ran your setup.exe for all users on my machine
7. Ran setupsdk.exe
THEN, I looked at c:\pellesc\include\win\ sub-dir
and there were the same total of 444 files but, this time, NO stralign.h file !!
So, the only thing different was my running of the registry cleaner !
Conclusion:
Something was left over in my registry from previous installs
Now, I can carry on building a new xHarbour platform under the new Pelles C Version 8 compiler.
My thanks to Frankie and Timo, and especially for the suggestion for using a Registry Cleaner. I haven't used one for a couple of years now, and this suggestion will result in my being able to sleep better tonite.
-Mel Smith
-
:D :D :D
-
:D :D :D
Hi Frankie:
Below is the *older* and incorrect listing of my c:pellesc\include\win sub-directory with stralign.h in it.
I kept getting the same contents after each uninstall and re-install to the c:\pellesc> directory UNTIL I installed in c:\progra~2\Pellesc, then uninstalled and did the Registry Cleaning. Prior to this I did my own 'scrubbing' of the registry.
Anyway, please note the time, and dates numbers of files (129 instead of 344) in the listing *and* the presence of stralign.h
****** listing of c:\pellesc\include\win sub-dir ****
Volume in drive C is OS
Volume Serial Number is 0884-CE9F
Directory of C:\PELLESC\Include\win
04/12/2014 04:55 AM 410 sac.h
04/12/2014 04:55 AM 45,876 sal.h
04/12/2014 04:55 AM 2,231 sal_supp.h
04/12/2014 04:55 AM 826,506 sapi.h
04/12/2014 04:55 AM 708,293 sapi51.h
04/12/2014 04:55 AM 819,267 sapi53.h
04/12/2014 04:55 AM 146,299 sapiddk.h
04/12/2014 04:55 AM 103,165 sapiddk51.h
04/12/2014 04:55 AM 402 sas.h
04/12/2014 04:55 AM 109,939 sbe.h
04/12/2014 04:55 AM 5,593 sberrors.h
04/12/2014 04:55 AM 127,573 sbtsv.h
04/12/2014 04:55 AM 550 scarddat.h
04/12/2014 04:55 AM 14,666 scarderr.h
04/12/2014 04:55 AM 550 scardmgr.h
04/12/2014 04:55 AM 550 scardsrv.h
04/12/2014 04:55 AM 131,530 scardssp.h
04/12/2014 04:55 AM 2,335 scclient.h
04/12/2014 04:55 AM 13,627 scesvc.h
04/12/2014 04:55 AM 30,397 schannel.h
04/12/2014 04:55 AM 2,284 schedule.h
04/12/2014 04:55 AM 5,270 SchemaDef.h
04/12/2014 04:55 AM 615 schnlsp.h
04/12/2014 04:55 AM 344 scode.h
04/12/2014 04:55 AM 8,752 scrnsave.h
04/12/2014 04:55 AM 747 scrptids.h
04/12/2014 04:55 AM 3,011 scserver.h
04/12/2014 04:55 AM 13,207 sddl.h
04/12/2014 04:55 AM 9,244 sdkddkver.h
04/12/2014 04:55 AM 89,946 sdoias.h
04/12/2014 04:55 AM 97,533 sdpblb.h
04/12/2014 04:55 AM 2,491 sdperr.h
04/12/2014 04:55 AM 635 sdv_driverspecs.h
04/12/2014 04:55 AM 204,620 searchapi.h
04/12/2014 04:55 AM 4,506 secext.h
04/12/2014 04:55 AM 1,744 security.h
04/12/2014 04:55 AM 721,926 segment.h
04/12/2014 04:55 AM 640 sehmap.h
04/12/2014 04:55 AM 2,245 sens.h
04/12/2014 04:55 AM 1,419 sensapi.h
04/12/2014 04:55 AM 27,095 sensevts.h
04/12/2014 04:55 AM 33,928 sensors.h
04/12/2014 04:55 AM 41,225 sensorsapi.h
04/12/2014 04:55 AM 7,998 servprov.h
04/12/2014 04:55 AM 7,582 SessdirPublicTypes.h
04/12/2014 04:55 AM 216,145 setupapi.h
04/12/2014 04:55 AM 1,102 setupdd.h
04/12/2014 04:55 AM 1,693 sfc.h
04/12/2014 04:55 AM 23,768 shappmgr.h
04/12/2014 04:55 AM 175,729 shdeprecated.h
04/12/2014 04:55 AM 3,558 shdispid.h
04/12/2014 04:55 AM 70,560 shellapi.h
04/12/2014 04:55 AM 11,185 sherrors.h
04/12/2014 04:55 AM 3,425 shfolder.h
04/12/2014 04:55 AM 11,453 shidfact.h
04/12/2014 04:55 AM 22,521 ShImgData.h
04/12/2014 04:55 AM 263,795 shldisp.h
04/12/2014 04:55 AM 46,571 shlguid.h
04/12/2014 04:55 AM 214,146 shlobj.h
04/12/2014 04:55 AM 120,453 shlwapi.h
04/12/2014 04:55 AM 1,104,203 ShObjIdl.h
04/12/2014 04:55 AM 14,350 shtypes.h
04/12/2014 04:55 AM 19,764 simpdata.h
04/12/2014 04:55 AM 5,206 simpdc.h
04/12/2014 04:55 AM 630 sipbase.h
04/12/2014 04:55 AM 3,426 sisbkup.h
04/12/2014 04:55 AM 70,473 slerror.h
04/12/2014 04:55 AM 846 sliddefs.h
04/12/2014 04:55 AM 10,003 slpublic.h
04/12/2014 04:55 AM 1,316 smpab.h
04/12/2014 04:55 AM 1,975 smpms.h
04/12/2014 04:55 AM 3,861 smpxp.h
04/12/2014 04:55 AM 7,311 SmtpGuid.h
04/12/2014 04:55 AM 14,222 smx.h
04/12/2014 04:55 AM 24,215 snmp.h
04/12/2014 04:55 AM 12,865 SoftPub.h
04/12/2014 04:55 AM 3,105 spapidef.h
04/12/2014 04:55 AM 34,295 spcollec.h
04/12/2014 04:55 AM 29,263 spddkhlp.h
04/12/2014 04:55 AM 23,378 specstrings.h
04/12/2014 04:55 AM 1,945 specstrings_adt.h
04/12/2014 04:55 AM 60,323 specstrings_strict.h
04/12/2014 04:55 AM 2,952 specstrings_supp.h
04/12/2014 04:55 AM 10,943 specstrings_undef.h
04/12/2014 04:55 AM 34,078 sperror.h
04/12/2014 04:55 AM 29,681 speventq.h
04/12/2014 04:55 AM 91,844 sphelper.h
04/12/2014 04:55 AM 1,497 sporder.h
04/12/2014 04:55 AM 8,143 spuihelp.h
04/12/2014 04:55 AM 33,200 sql.h
04/12/2014 04:55 AM 91,320 sqlext.h
04/12/2014 04:55 AM 26,183 sqloledb.h
04/12/2014 04:55 AM 7,556 sqltypes.h
04/12/2014 04:55 AM 28,623 sqlucode.h
04/12/2014 04:55 AM 4,065 sql_1.h
04/12/2014 04:55 AM 5,494 SrRestorePtApi.h
04/12/2014 04:55 AM 16,476 srv.h
04/12/2014 04:55 AM 666 sspguid.h
04/12/2014 04:55 AM 94,555 sspi.h
04/12/2014 04:55 AM 869 sspserr.h
04/12/2014 04:55 AM 386 sspsidl.h
04/12/2014 04:55 AM 6,184 statusdeviceservice.h
04/12/2014 04:55 AM 2,338 stgprop.h
04/12/2014 04:55 AM 27,500 sti.h
04/12/2014 04:55 AM 4,290 stierr.h
04/12/2014 04:55 AM 2,762 stireg.h
04/12/2014 04:55 AM 816 stllock.h
04/12/2014 04:55 AM 9,113 stm.h
04/12/2014 04:55 AM 563 storage.h
04/12/2014 04:55 AM 2,690 storprop.h
04/12/2014 04:55 AM 16,057 StrAlign.h ******** here it is ********
04/12/2014 04:55 AM 44,338 streamcache.h
04/12/2014 04:55 AM 47,373 streamdescription.h
04/12/2014 04:55 AM 736,361 strmif.h
04/12/2014 04:55 AM 14,940 strongname.h
04/12/2014 04:55 AM 329,302 strsafe.h
04/12/2014 04:55 AM 86,973 structuredquery.h
04/12/2014 04:55 AM 25,746 structuredquerycondition.h
04/12/2014 04:55 AM 12,650 subauth.h
04/12/2014 04:55 AM 41,351 subscriptionservices.h
04/12/2014 04:55 AM 40,827 subsmgr.h
04/12/2014 04:55 AM 18,955 svcguid.h
04/12/2014 04:55 AM 47,088 svrapi.h
04/12/2014 04:55 AM 4,246 syncdeviceservice.h
04/12/2014 04:55 AM 8,117 synchronizationerrors.h
04/12/2014 04:55 AM 133,219 syncmgr.h
04/12/2014 04:55 AM 5,288 syncop.h
04/12/2014 04:55 AM 51,453 syncregistration.h
04/12/2014 04:55 AM 2,282 syncregistrationerrors.h
129 File(s) 9,223,198 bytes
0 Dir(s) 230,676,541,440 bytes free
******************************************
-
Those are not PellesC files.
Same old time stamp in every file.
Could you zip that stralign.h for us ?
Just to guess where it came from.
-
Those are not PellesC files.
Same old time stamp in every file.
Could you zip that stralign.h for us ?
Just to guess where it came from.
Hi Timo:
Sorry I can't zip it because I now only have the listing itself as a .txt file. But the file and all the others *appeared* in my *empty* C:\pellesc\include\win\ sub-dir only *after* I ran the setup.exe. So they came into being via the running of setup.exe. And I can't re-create the conditions the resulted in stralign.h
Also, we finished building our latest version of xHarbour today under PellesC Version 8, and it is now published on our repository for the Harbour language (www.whosaway.com). The only change we had to make was to substitute the 'Make' utility from Visual C 2015 (nmake.exe) to replace pomake.exe Pomake causes our 'build' to crash in the late stages of building. Using the Visual C make utility corrects this problem.
btw, our next task is to wrestle with the recent version of Visual C (VC2015) installed also on my route drive as c:\VC2015>. We have it installed, but it, too, crashes while starting to build xHarbour. We used to have older versions of PellesC and Visual C on our system, and they worked correctly in building xHarbour. But now we have these current problems. Keeps us busy !
xHarbour can be thought of as Hi-C type of language, and is somewhat like Python. But, to us, much more powerful and with more clarity. Started in 1999 and still growing.
Thanks again for your help and we'll try again to use POMAKE in our building process when we have time to re-test.!
-Mel Smith