----- Original Message ----- From: "Frank Heckenbach" frank@g-n-u.de To: ioffe_nick@mail.ru; gpc@gnu.de Sent: Thursday, July 24, 2003 19:59 Subject: Re: Re[2]: Linking the libgpc to be shared
Nick Ioffe wrote:
Also before that I got some strange errors when configure erroneusly created rts-config.h file - it didn't found open64 and usleep functions in /usr/local/include/fcntl.h - it was discovered by compiler.
What exactly was set? HAVE_OPEN64 and/or OPEN64_DECLARED?
- The OPEN64_DECLARED.
You mean OPEN64_DECLARED was set and HAVE_OPEN64 not, right? And what exactly was the error message by the compiler?
Also I've discovered some syntax changes that cause me some hardwork in
fixing the project:
- one import and then list of all modules delimited by ';' more than one import like import try; import gpc; doesn't work.
Yes, that's according to EP.
- repeated routine declaration - now I have to get rid of all the parameters in implementation part - otherwise I get "routine declaration doesn't match previous declaration" error
Repeated parameters still work. If you get an error, the declarations either don't actually match, or there's a GPC bug, but I can't tell without an example.
Frank
-- Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: 51FF C1F0 1A77 C6C2 4482 4DDC 117A 9773 7F88
1707
1. The rts-config.h had OPEN64_DEFINED undefined, while HAVE_OPEN64 set to 1. That caused the redeclaration of open64 with some gpc file which is conflicting with /usr/local/include/fcntl.h. 2. It is hard to me to provide the example since the machine I run the gpc is not connected to the Internet. The only thing I can say is that the same module compiled well with gpc- 200205??. I'll try to bring some example...
Thank you very much, again - I appreciate your help a lot, and I wish I could contribute promille of what you're doing here.
Sincerely,
Nick.