Frank:
My sysadmin set up a recent alpha but it crashed on a simple 'hello world' program. Is 20041218 the most recent stable version?
Yes, it is. However, an alpha should not be as unstable as in not being able to compile a simple program. (It's just been tested somewhat less thorough than a beta.) If you provide more information, readers of the list can probably help you set it up working. (Error messages, system and version, backend version, etc., the usual stuff ...)
My sysadmin did the installation:
| > I just installed the latest _alpha_ version of gpc under /usr/local/gpc | > (the old version is under /usr/local/gpc.old). I have also moved | > /usr/local/bin/gpc to /usr/local/bin/gpc-2.1 and /usr/local/bin/gpc-run | > to /usr/locla/bin/gpc-run-2.1 to make sure they don't get run | > inadvertently. | > | > Make sure that your compile scripts use /usr/local/gpc/bin/gpc instead | > of /usr/local/bin/gpc . Also, keep in mind that the gpc developers | > still consider this to be alpha code, so you may encounter as many new | > bugs as (hopefully fixed) old ones. | | Thanks. | | Unfortunately it is too alpha - it crashes even for this: | | strawberry 40% cat t.p | program t (output); | begin | writeln(output,'hello world'); | end. | strawberry 41% /usr/local/gpc/bin/gpc t.p | strawberry 42% a.out | Segmentation Fault | | :-( | | strawberry 44% /usr/local/gpc/bin/gpc -v | Reading specs from /export/data/local/gpc/bin/../lib/gcc-lib/sparc-sun-solaris2.8/3.3.3/specs | Configured with: /export/home/bryantd/gpc-build/../gcc-3.3.3/configure --enable-languages=pascal --prefix=/usr/local/gpc | Thread model: posix | gpc version 20050331, based on gcc-3.3.3 | | When I try to use /usr/local/bin/gpc-2.1 in my gpcc script | (/home/strawberry/toms/work/emptytest/gpcc2.1), I get: | | gpc1: Invalid option `-Wno-identifier-case-local' | | so I can't compile until this is fixed ...
My gpcc script is at ftp://ftp.ncifcrf.gov/pub/delila/gpcc in gpcc2.1 I just modified the location of the compiler.
I'm working on a Sun:
% uname -aimnprsvX SunOS strawberry 5.9 Generic_117171-12 sun4u sparc SUNW,Sun-Blade-1000System = SunOS
Good luck with that, it doesn't seem to be much to go on ...
Tom
Dr. Thomas D. Schneider National Institutes of Health National Cancer Institute Center for Cancer Research Nanobiology Program Molecular Information Theory Group Frederick, Maryland 21702-1201 toms@ncifcrf.gov permanent email: toms@alum.mit.edu (use only if first address fails) http://www.ccrnp.ncifcrf.gov/~toms/
Is there some place on the web site that tells this that I missed? (I don't see how you determined the above, for example.)
See the (2nd) URL in my sig. http://www.gnu-pascal.de/todo.html
Thanks!! I didn't think to look for solved bugs under 'to do' ... ;-)
Tom
Dr. Thomas D. Schneider National Institutes of Health National Cancer Institute Center for Cancer Research Nanobiology Program Molecular Information Theory Group Frederick, Maryland 21702-1201 toms@ncifcrf.gov permanent email: toms@alum.mit.edu (use only if first address fails) http://www.ccrnp.ncifcrf.gov/~toms/
Tom Schneider wrote:
Frank:
My sysadmin set up a recent alpha but it crashed on a simple 'hello world' program. Is 20041218 the most recent stable version?
Yes, it is. However, an alpha should not be as unstable as in not being able to compile a simple program. (It's just been tested somewhat less thorough than a beta.) If you provide more information, readers of the list can probably help you set it up working. (Error messages, system and version, backend version, etc., the usual stuff ...)
My sysadmin did the installation:
| > I just installed the latest _alpha_ version of gpc under /usr/local/gpc | > (the old version is under /usr/local/gpc.old). I have also moved | > /usr/local/bin/gpc to /usr/local/bin/gpc-2.1 and /usr/local/bin/gpc-run | > to /usr/locla/bin/gpc-run-2.1 to make sure they don't get run | > inadvertently. | > | > Make sure that your compile scripts use /usr/local/gpc/bin/gpc instead | > of /usr/local/bin/gpc . Also, keep in mind that the gpc developers | > still consider this to be alpha code, so you may encounter as many new | > bugs as (hopefully fixed) old ones. | | Thanks. | | Unfortunately it is too alpha - it crashes even for this: | | strawberry 40% cat t.p | program t (output); | begin | writeln(output,'hello world'); | end. | strawberry 41% /usr/local/gpc/bin/gpc t.p | strawberry 42% a.out | Segmentation Fault | | :-(
Aha, so it isn't GPC that crashes, but the compiled executable. That's already more information than in your last mail.
One possibility could be a confusion of runtime library versions or compiler parts. I see your admin installed GPC in a nonstandard directory. Did he do this correctly, i.e. either set the --prefix on configure, or else set GPC_EXEC_PREFIX?
If that's ok, can you run the program in a debugger to find out where it crashes?
| strawberry 44% /usr/local/gpc/bin/gpc -v | Reading specs from /export/data/local/gpc/bin/../lib/gcc-lib/sparc-sun-solaris2.8/3.3.3/specs | Configured with: /export/home/bryantd/gpc-build/../gcc-3.3.3/configure --enable-languages=pascal --prefix=/usr/local/gpc | Thread model: posix | gpc version 20050331, based on gcc-3.3.3 | | When I try to use /usr/local/bin/gpc-2.1 in my gpcc script | (/home/strawberry/toms/work/emptytest/gpcc2.1), I get: | | gpc1: Invalid option `-Wno-identifier-case-local' | | so I can't compile until this is fixed ...
Uhm, fixed? gpc-2.1 is 3 years old, and we don't actually plan to backport new features to it. If it's just this one (you don't require other newer features), you can take out this option for 2.1 (which simply didn't exist back then).
My gpcc script is at ftp://ftp.ncifcrf.gov/pub/delila/gpcc in gpcc2.1 I just modified the location of the compiler.
It's a bit longish, so I can't read it all now.
BTW, one thing:
: # -Widentifier-case-local : # Warn about an identifier written with varying case within one : # program/module/unit. : # THIS IS BADLY IMPLEMENTED BECAUSE IT DOES NOT FOLLOW SCOPE RULES! : # That is, a local variable in one proceedure affects the case : # of local variables in later procedures, violating scope rules. : # I was unable to convince the GPC writers to fix it. : # (They even got all huffy and nasty about this.) : # So I will NOT use it here as it gives bogus messages.
You know, this is free software. If you want something implemented, you basically have 4 choices:
1. Do it yourself.
2. Ask politely and/or convince someone to do it for you.
3. Pay someone to do it for you.
4. Shout and offend people if they don't do for free what you want them to do.
Apparently you chose 4. I will keep this in mind in our further correspondence.
BTW, your quick jumping to conclusions that "[GPC] is too alpha" when in fact it may just be an installation problem on your (or your admin's) part, or claiming that an older version not supporting newer options is something that needs to be "fixed" [by other people, I suppose you mean], are also some (weaker) forms of 4.
If you're interested in 3., mail me privately. (As a paying constomer, you'd have some legitimation to get angry if things are not done as you like.) For 2., this was probably my last time trying to help you for free.
Frank