Hello
I have compiled this snapshot with djgpp (W98 dos box). Seems successfull but the crtdemo.pas, as well as other programs of mine which use crt, fail. To check that nothing has gone wrong with my djgpp setup I have then compiled some previous snapshots. Everything seems correct up to 20001230 (which succeeds with crtdemo and the whole test suite). 20001231 fails to compile with a message:
make.exe[2]: *** No rule to make target `/djgpp/gnu/gcc-2.952/gcc/p/../ggc-callbacks.c', needed by `ggc-callbacks.o'. Stop.
looks like a mistyping... It seems to have been corrected in 20010101 which compiles OK, but something else is hidden. Since djgpp and linux you mainly use are different with respect to crt and curses it may have been unnoticed in your setup.
Hope this helps
Maurice
Hello,
Maurice Lombardi wrote:
make.exe[2]: *** No rule to make target `/djgpp/gnu/gcc-2.952/gcc/p/../ggc-callbacks.c', needed by `ggc-callbacks.o'. Stop.
looks like a mistyping...
That's not a typo; the file reads indeed `../ggc-callbacks.c'.
The existence of this file should not have made it into `Make*-2.95.in'; it is mentioned in `Make*-2.97.in' only.
Maybe the 8.3 file names in MS-DOS made the contents of `Make*-2.97.in' show up in `Make*.in'? But this should have shown up earlier. I am quite sure that I always checked in the 2.95 version as `Makefile.in', not the 2.97 building site ...
Peter
Hi
Perhaps an odd request to come from the English-speaking world but I am processing some text that comes from certain European countries which can include accents. Is there a default set of characters that includes such characters that occur from time to time in non-English languages? Particularly if it is also case-specific.
ie if c in ['A'..'Z'] ... will throw a wobbly if presented with umlaut or grave accents but I want to have either (a) an automatic translation into the unaccented character (it is just used for storing) or (b) an extended set of (say) upper-case accented characters. Even just the accented characters themselves since I could obviously extend the basic set.
After all, UpCase and LoCase recognise accents ...
TIA
John
j.logsdon@lancaster.ac.uk wrote:
Perhaps an odd request to come from the English-speaking world but I am processing some text that comes from certain European countries which can include accents. Is there a default set of characters that includes such characters that occur from time to time in non-English languages? Particularly if it is also case-specific.
ie if c in ['A'..'Z'] ... will throw a wobbly if presented with umlaut or grave accents but I want to have either (a) an automatic translation into the unaccented character (it is just used for storing) or (b) an extended set of (say) upper-case accented characters. Even just the accented characters themselves since I could obviously extend the basic set.
After all, UpCase and LoCase recognise accents ...
There are functions IsAlphaNum (check is character is alphanumeric) etc. in gpc.pas for this purpose. I just noticed that IsAlpha is missing. I'm adding it soon (if you don't want to upgrade GPC, you can, of course, use IsAlphaNum and make sure it's not a digit).
These functions are locale dependent, i.e. they work according to the language specified in the environment variable LANG or LC_CTYPE (just like UpCase and LoCase).
Frank
Peter Gerwinski a écrit :
Hello,
Maurice Lombardi wrote:
make.exe[2]: *** No rule to make target `/djgpp/gnu/gcc-2.952/gcc/p/../ggc-callbacks.c', needed by `ggc-callbacks.o'. Stop.
looks like a mistyping...
That's not a typo; the file reads indeed `../ggc-callbacks.c'.
The existence of this file should not have made it into `Make*-2.95.in'; it is mentioned in `Make*-2.97.in' only.
OK this is the clue. In the gpc-20001231.tar.gz file, make-lang.in is identical to make-lang-2.97.in and makefile.in is identical to makefile-2.97.in, whereas in gpc-20010101 they are identical to 2.95 files. I don't know how you select which of make*.in is used among the 2.8, 2.95 and 2.97 versions, or if the unnumbered file is selected by default.
I will recompile now 20010101 after eliminating all 2.97 files in order to see if the problem about crt remains.
Hope this helps
Maurice
Maurice Lombardi wrote:
In the gpc-20001231.tar.gz file, make-lang.in is identical to make-lang-2.97.in and makefile.in is identical to makefile-2.97.in, whereas in gpc-20010101 they are identical to 2.95 files.
Hupps! This should not happen - in the `.tar.gz' files, `Make*.in' should alway be identical to `Make*-2.95.in'. The other `Make*-2.*.in' are there for manual use by people with special requirements/interests. (Also, the installation instructions assume gcc-2.95.x.)
Thanks,
Peter
Maurice Lombardi a écrit :
I will recompile now 20010101 after eliminating all 2.97 files in order to see if the problem about crt remains.
I have compiled the new 20010107 instead. Compiles OK but the crtdemo problem remains. Do you have it in dosemu ?
Maurice
-
Frank Heckenbach -
j.logsdon＠lancaster.ac.uk -
Maurice Lombardi -
Peter Gerwinski