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;
> > >
> > > 1. rts-config.inc is not installed when you run 'make pascal.install'
> > > 2. 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);
> >
> > 1. "@true" causes an error in 'pascal.install' and 'pascal.bindist', so
> > I have removed it.
> >
> > 2. "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.
> >
> > 3. 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.
--
Waldek Hebisch
hebisch(a)math.uni.wroc.pl