Greetings. This is mainly to Dbug. I think I am getting into trouble, as I get the error "Too many defined labels" when compiling 1337.
The error is generated at the linking stage, I think by link65. I have taken a look a the sources, but did not spot where the error comes from or which is the limit.
If it is indeed that I have reached the maximum number of labels, I have a problem. I am not sure how to solve this, although most labels are local. If maybe there is a way to increase this number it would be great.
Another possibility is that it there is some kind of error in the sources or something I need to check?
Any hint, please?
Think I am in trouble: Too many defined labels
Ok, it's a hard limit in the old Link65.c:
This limit is not in the C++ version, but I did not release a version with it because there is a bug :p
I will try to see if I can fix the C++ version, and if not I can probably rebuild a C version with a new limit, like 2010
Code: Select all
if (dcount > 1999)
{
linkerror("\nToo many defined labels\n");
exit(1);
}
I will try to see if I can fix the C++ version, and if not I can probably rebuild a C version with a new limit, like 2010
Ok thanks Dbug. That explains why I did not see where the error message was in the svn sources. Surely that is the size of the internal dictionary that manages them.Dbug wrote:Ok, it's a hard limit in the old Link65.c:
This limit is not in the C++ version, but I did not release a version with it because there is a bug :p
I will try to see if I can fix the C++ version, and if not I can probably rebuild a C version with a new limit, like 2010
So I surpassed 2000 labels? Wow. I could even have a look and try to compile a new version with something as 10000 labels for me...
The C++ linker has been fixed thanks to a good repro-case by Chema, so the constraints on the number of labels is now gone.
The next big bug in the current osdk code is something with XA not accepting some characters in comments. When this is fixed I will release a new version of the OSDK (Release Candidate) and ask people to test it before I publish it - it may contains bugs I've missed, because there's quite a lot of modified code.
The next big bug in the current osdk code is something with XA not accepting some characters in comments. When this is fixed I will release a new version of the OSDK (Release Candidate) and ask people to test it before I publish it - it may contains bugs I've missed, because there's quite a lot of modified code.