News:

Download Pelles C here: http://www.pellesc.se

Main Menu

Recent posts

#71
Announcements / Re: Release Candidate #1 for v...
Last post by Vortex - July 20, 2026, 10:54:15 PM
Hi Pelle,

Thanks for the new release of Poasm fixing the issue.
#72
Beginner questions / Re: Unresolved External Symbol
Last post by StevenCooper - July 20, 2026, 06:26:09 PM
Quote from: Pelle on July 20, 2026, 02:55:21 PM
Quote from: StevenCooper on July 19, 2026, 08:15:51 AMPOLINK: error: Unresolved external symbol '__stod' - referenced from 'C:\Users\steco\Documents\Pelles C Projects\LotteryScratchOffs\output\LotteryScratchOffs.obj'.
__stod() was an internal helper function, no longer needed, and (obviously) never documented.

This symbol can't pop out of thin air, so the most likely reasons are:
1) you are somehow pulling in (old) #include files from the wrong directory
2) the file LotteryScratchOffs.obj is not (re)built properly, or the associated source file (LotteryScratchOffs.c ?!) contains some private reference to __stod.



If I'm remembering correctly, when I jumped to version 14.5, I did NOT first uninstall version 10; so, maybe the Setup program did not overwrite some of the old files; it was a pretty big jump.

As it turns out, I really didn't need to abandon version 10 after all; the problem I had when I installed it on Windows 11 Pro was I would get this error message when trying to build a project:

Error Code: 1073741819

The .obj files would get built, then the above error message would appear, and the build would stop. I have since discovered that all I need to do when I get that message is click on the "Build" button again, and the build process will finish correctly.

I have found that Version 11 of Pelles C has the same problem, intermittently, and again, I just click on the "Build" button a second time and the process finishes and I have an executable program.

Before I left Windows 10, I saved the Registry keys for Pelles configuration, so I could restore my configuration in the new version. I installed those keys in the Windows 11 registry before I installed Pelles C Version 10.

Any chance those old registry keys are causing problems?

I do have a precompiled library called Srclib from Version 10; perhaps I need to re-compile it in Version 14.5 before I recompile programs that use that library (almost all my programs use it).

I may, if I decide to move to Version 14, try completely uninstalling Pelles c, and manually delete registry keys and residual files and folders before doing a "clean" install of version 14. However, for now, I'm perfectly happy with Version 11, more or less.
#73
Beginner questions / Re: Just installed Pelles C an...
Last post by MrBcx - July 20, 2026, 05:39:25 PM
Quote from: Pelle on July 20, 2026, 03:22:29 PM
Quote from: MrBcx on July 18, 2026, 04:13:31 PMThe main thing is: DO NOT use spaces in your folder name.
Pelles C was tested from the start with spaces in the path. This has always worked here.

Sorry ... I should have been more clear.

Eliminating spaces in paths is a tenet that I adopted long ago. I did encounter problems
with paths containing spaces in the past.  Regardless of the cause(s), those instances
were always resolved by changing to unambiguous paths.

#74
Announcements / Version 14.50 is now released
Last post by Pelle - July 20, 2026, 04:10:15 PM
See https://www.pellesc.se/, Download (and Changes).

Changes from Release Candidate #1:
    Fixed minor linker problem with one (not very common) form of weak external symbol.
#75
Announcements / Re: Release Candidate #1 for v...
Last post by Pelle - July 20, 2026, 03:45:20 PM
Quote from: Vortex on July 14, 2026, 03:56:05 PMRegarding the keyword ALIAS :
Could you give an example?
The ALIAS directive is not very useful. It was once added because MASM had it, but the implementation in POASM was always a bit backwards because of related support for other "weak external" symbols. Trying to clean this up now made POASM better, but of course then it fails in POLINK (now fixed).

The only time I ever used the ALIAS directive was when building older versions of oldnames*.lib, using a bunch of auto-generated assembly files, mapping open() to _open(), chdir() to _chedir(), and so on. This has since been replaced with a different and better approach.

#76
Beginner questions / Re: Just installed Pelles C an...
Last post by Pelle - July 20, 2026, 03:25:58 PM
Quote from: PabloMack on July 19, 2026, 05:17:02 AMI am running Windows 10. I installed PellesC in an Admin account for everyone but I am trying to use it under a non-privilege account.
This have been tested in the past, but not recently. Then again, I doubt much have changed (in the installer at least)...
#77
Beginner questions / Re: Just installed Pelles C an...
Last post by Pelle - July 20, 2026, 03:22:29 PM
Quote from: MrBcx on July 18, 2026, 04:13:31 PMThe main thing is: DO NOT use spaces in your folder name.
Pelles C was tested from the start with spaces in the path. This has always worked here.
#78
Bug reports / Re: PoFmt bug
Last post by Pelle - July 20, 2026, 03:14:06 PM
I guess POFMT needs to be aware of more non-preprocessed types. Changing va_list to __VA_LIST_TYPE__ improve things.
Version 14.50 is done, so this will have to wait until some (possible) future version.
#79
Beginner questions / Re: Unresolved External Symbol
Last post by Pelle - July 20, 2026, 02:55:21 PM
Quote from: StevenCooper on July 19, 2026, 08:15:51 AMPOLINK: error: Unresolved external symbol '__stod' - referenced from 'C:\Users\steco\Documents\Pelles C Projects\LotteryScratchOffs\output\LotteryScratchOffs.obj'.
__stod() was an internal helper function, no longer needed, and (obviously) never documented.

This symbol can't pop out of thin air, so the most likely reasons are:
1) you are somehow pulling in (old) #include files from the wrong directory
2) the file LotteryScratchOffs.obj is not (re)built properly, or the associated source file (LotteryScratchOffs.c ?!) contains some private reference to __stod.

#80
Beginner questions / Re: Unresolved External Symbol
Last post by Vortex - July 20, 2026, 09:10:30 AM
Hi Steven,

You should not have to recompile everything if some files are not modified.