Mail Archives: djgpp/2001/03/26/06:31:47
On 25 Mar 2001, at 15:31, Mr. Veli Suorsa wrote:
> Thanks for your reply!
>
> >> ftp://agnes.dida.physik.uni-essen.de/home/maurice/gpc2952b.zip
> >OK. I try to always give under this same link the lastest gpc snapshot I have
> compiled, and which give zero error when
> >running the whole test suite.
>
> I just updated gcc-2.95.3 version of Djgpp. Every other compiler seems to work
> well (Thanks to Andris).
>
> Can You update this Pascal compiler (gpc2953b.zip) and documentation and inform
> me (download site), too?
I tried to add Pascal support in gcc2953s2.zip after I released DJGPP
port of gcc-2.95.3, but it is not finished and I only did the tests with
scripts intended for cross-building gcc-2.95.3 for DJGPP under Linux.
Now it seems that I may have to rerelease gcc-2.95.3 for DJGPP after
some time, so it's possible I'll get it in (but don't ask, when ...).
> >To force a build in pascal you need to replace --automake by --autobuild as
> compilation option.
> >But this is nowhere provided for in rhide (and in particular is not done when
> you hit compile/build) because of the
> >different logics: looking into the makefiles generated by rhide you have provision
> for RHIDE_COMPILE_LINK_AUTOMAKE but
> >not for RHIDE_COMPILE_LINK_AUTOBUILD
>
> I hope they add this --autobuild as a compilation option to next version.
Somebody who uses Pascal should send patches for RHIDE (but test
them at first, so he/she should be able to build RHIDE from sources)
All this stuff is located in idespec.cc
> >You have probably an older version of rhide. Better upgrade.
>
> My version is Rhide 1.4.7.8 (latest).
>
> >> PASCAL_TYPE=GPC
> >OK
> >
> >> RHIDE_LD_PASCAL=gcc
> >? for me it is gpc
>
> I change it to gcc, because gpc did not works. I "cheat" from Fortran make.
>
>
> >> RHIDE_COMPILE_GPC=$(RHIDE_GPC) $(RHIDE_GPC_FLAGS) $(LOCAL_OPT) -c $(SOURCE_NAME)
>
> >> -o $(OUTFILE)
> >> RHIDE_COMPILE_LINK_GPC=$(RHIDE_LD_PASCAL) $(RHIDE_LIBDIRS) $(C_EXTRA_FLAGS)
>
> >> -o $(OUTFILE) $(OBJFILES) $(LIBRARIES) $(RHIDE_LDFLAGS) $(LDFLAGS) $(RHIDE_LIBS)
>
> >>
> >> RHIDE_COMPILE_LINK_PASCAL_AUTOMAKE=$(RHIDE_COMPILE_LINK_$(PASCAL_TYPE))
> >
> >This is unnecessary since it is identical to the defaults contained in rhide.
> What is necessary is:
> >
> >RHIDE_COMPILE_LINK_GPC_AUTOMAKE=$(RHIDE_LD_PASCAL) $(RHIDE_LIBDIRS) -o $(OUTFILE)
> --autobuild $(RHIDE_GPC_FLAGS)
> >$(SOURCE_NAME) $(LIBRARIES) $(LDFLAGS) $(RHIDE_LDFLAGS) $(RHIDE_LIBS)
>
> I will try this when you send me the new version of GPC.
>
> >i.e. suppress options to automake to avoid those stupid warning messages, and
> probably replace --automake altogether by
> >--autobuild.
> >I am not sure that the latest replacement is still necessary. It was sometimes
> ago but I have not checked it recently.
> >It increases compilation time, but it is more secure.
> >An other convenient way is to use a compilation option --unit-destination-path=
> (better included automatically in the
> >default rhide project if you work mainly in pascal) to put all .o .gpi .gpm
> files into a given directory, and to delete
> >manually all the content of this directory when you want a rebuild (easy only
> if you work in a windows dos box not to
> >need to exit from rhide each time you need to do that, or you can have a .bat
> file in your path to do that and do it by
> >exiting temporarilly from rhide by hitting File/Dos shell).
> >Anyhow be carefull that you have to delete all these files each time you upgrade
> to a new version of gpc.
>
> I use Rhide in Windows Dos box and it works.
>
> If you know how to delete in environment file told temporary files automatically,
> tell me!
>
> >Hope this helps,
>
Andris
- Raw text -