Prof A Olowofoyeku (The African Chief) wrote:
On 25 Jul 2012 at 16:09, Waldek Hebisch wrote:
I wrote:
Hi Waldek
Something is broken under Win32 (compiling with msys environment). This is what I have noticed so far;
- rts-config.inc is not installed when you run 'make pascal.install'
- make-lang.inc has "@true" in it. This results in a "command not
found" error
I will report other problems as I isolate them - but there is a big difference from the release version, in the file sizes when you run 'make pascal.bindist' (about 500kb difference in the tarball size). I will investigate further and will report back in due course.
I have found the issues (under Win32, gcc-3.4.5 backend sources);
- "@true" causes an error in 'pascal.install' and 'pascal.bindist', so
I have removed it.
- "rts-config.inc" does not get installed. I believe it is something to
do with "TREE_GIMPLE_H" definitions. Since I don't fully understand TREE_GIMPLE_H, I have manually copied the code that installs the file to the relevant section.
- The GPC info files are not built or installed. I am yet to find a
solution to that.
Solved: I found that the git p/doc/info/ does not contain the .info files. It only contains a zero-byte file called ".git_is_stupid" !
Also, p/doc/generated/ does not contain "gpc-run.1". It also only contains a zero-byte file called ".git_is_stupid".
How do I update the git repository? Or will you do it yourself?
Sorry, I forgot to mention this: git repository is supposed to contain only source files. So machine generated files like content of p/doc/info/ and p/doc/generated/ is omited. Building gpc should fill those directores with content. But for this you need appropriate tools, in particular 'texinfo' package. Look at the output of 'configure' in build log, if configure can not find needed tools it will print a message and skip building documentation.
Git repository does not replace release tarballs -- simply it gives access to code between releases. Content is similar to what 'minimal' gpc tarballs used to contain.
Concerning updating git repository: I probably could give write access to persons needing it (I would have to check github instructions). However, more popular method seem to be that developer use GitHub 'fork' feature to create own version and then ask maintainer of main repository to merge changes back to master version. Anyway, for documentation the only thing that needs updating is README -- it should clearly say that you need to have 'texinfo'.
BTW: Please keep discussion on the mailing list. One, other folks may have similar problems and learn solution from archived message. Second, others may find good answer earlier.
On 27 Jul 2012 at 0:10, Waldek Hebisch wrote:
[...]
Sorry, I forgot to mention this: git repository is supposed to contain only source files. So machine generated files like content of p/doc/info/ and p/doc/generated/ is omited. Building gpc should fill those directores with content. But for this you need appropriate tools, in particular 'texinfo' package. Look at the output of 'configure' in build log, if configure can not find needed tools it will print a message and skip building documentation.
The problem is that texinfo was there all the time. The gcc configure log reports this:
"configure: WARNING: *** Makeinfo is missing or too old. *** Info documentation will not be built."
Well, I don't know about that, before it is there, and it is the latest version (v4.13).
[...]
Concerning updating git repository: I probably could give write access to persons needing it (I would have to check github instructions). However, more popular method seem to be that developer use GitHub 'fork' feature to create own version and then ask maintainer of main repository to merge changes back to master version.
Ok, I could look into that, thanks.
BTW: Please keep discussion on the mailing list. One, other folks may have similar problems and learn solution from archived message. Second, others may find good answer earlier.
Fair enough!
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/
Prof. Abimbola A. Olowofoyeku (The African Chief) wrote:
On 27 Jul 2012 at 0:10, Waldek Hebisch wrote:
[...]
Sorry, I forgot to mention this: git repository is supposed to contain only source files. So machine generated files like content of p/doc/info/ and p/doc/generated/ is omited. Building gpc should fill those directores with content. But for this you need appropriate tools, in particular 'texinfo' package. Look at the output of 'configure' in build log, if configure can not find needed tools it will print a message and skip building documentation.
The problem is that texinfo was there all the time. The gcc configure log reports this:
"configure: WARNING: *** Makeinfo is missing or too old. *** Info documentation will not be built."
Well, I don't know about that, before it is there, and it is the latest version (v4.13).
This is a bug in gcc-3.4.*: it checks for texinfo versions between 4.2 and 4.9 and considers every other version (like 4.13) as too old. Given that gcc-3.4.6 is from March 2006 and texinfo 4.11 (the next version after 4.9) is from September 2007 it was easy to overlook this problem.
I am not sure what is a good fix for this: gcc configure machinery is a mess and if we patch it we will need specific versions of other tools. Probably the easiest workaround (untested) is to create a little script, like:
-------------<cut here>-------------------------- #!/bin/sh
if [ "$1" == "--version" ] ; then echo "makeinfo (GNU texinfo) 4.8" else exec /usr/bin/makeinfo "$@" fi ------------<cut here>---------------------------
and then add 'MAKEINFO=/path/to/the/script' option to make command.
On 1 Aug 2012 at 19:50, Waldek Hebisch wrote:
[...]
This is a bug in gcc-3.4.*: it checks for texinfo versions between 4.2 and 4.9 and considers every other version (like 4.13) as too old. Given that gcc-3.4.6 is from March 2006 and texinfo 4.11 (the next version after 4.9) is from September 2007 it was easy to overlook this problem.
I am not sure what is a good fix for this: gcc configure machinery is a mess and if we patch it we will need specific versions of other tools.
Yes, I had discovered and fixed the bug in the gcc configure script (changed "4.[2-9]*" to "4.[1-9]*").
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/
-
Prof A Olowofoyeku (The African Chief) -
Waldek Hebisch