gm2
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hardest part every time :) - start.


From: Dragiša Durić
Subject: Re: Hardest part every time :) - start.
Date: Tue, 21 Apr 2020 17:38:11 +0200

Hi Christoph,

Different Debian based systems, different versions of libraries. I have
also tried to symlink libmpfr.so.6 to 4 and it worked, but no
guarantees there:). Looks like two major versions change to me.

Regards,
Dragiša

On Tue, 2020-04-21 at 00:54 +0200, Christoph Schlegel wrote:
> Hello,
> 
> GNU Modula-2 is available as a binary package from the official 
> repositories in Debian testing/Ubuntu. I use the compiler on a
> "normal" 
> Kubuntu installation and did not have any problems until now.
> 
> Greetings,
> Christoph
> 
> Am 20.04.2020 um 12:53 schrieb Dragiša Durić:
> > Hello people,
> > 
> > After some (pretty long time) I am trying to restart my Modula-2
> > projects.
> > 
> > This time I have Ubuntu 18.04 LTS on mu laptop. First thing, of
> > course, 
> > I tried to get .deb from floopsie. I got it, installed it and
> > it... 
> > failed. Problem is - Ubuntu has libmpfr.so.6 and floopsie's deb is
> > build 
> > with .so.4.
> > 
> > Ok, this is easy, I thought... just get source tarball from
> > floopsie and 
> > that will unravel.
> > 
> > Yes, but no... No instructions in archive. Presumably, all of us
> > are 
> > building .deb's three times per day, or something. Ok, I google.
> > But, 
> > Ubuntu does not have dh_make, it has dh_builddev... But in end, it 
> > failed. It looks for DEBIAN/control, when I rename debian to DEBIAN
> > it 
> > fails because at some step debian/control was missing...
> > 
> > (BTW, I made a number of RPM recipes in past, and RPM is blessing 
> > compared to this unholy mess.)
> > 
> > Ok, I give up on .deb. But look, this source archive comes with
> > already 
> > combined-in trees. I get into gm2 folder, mkdir build, cd build, 
> > ..configure... make SHELL=/bin/bash
> > 
> > Wow, it actually works... Compilation starts and for some time no 
> > purple, no cyan... Nice! I leave it and go to sleep.
> > 
> > In the morning....
> > 
> > 
> > ...ing makeinfo --split-size=5000000 --split-size=5000000"  compare
> > 
> > make[2]: Entering directory '/home/dragisha/gm2/gm2/build'
> > 
> > make[3]: Entering directory '/home/dragisha/gm2/gm2/build'
> > 
> > rm -f stage_current
> > 
> > make[3]: Leaving directory '/home/dragisha/gm2/gm2/build'
> > 
> > Comparing stages 2 and 3
> > 
> > Bootstrap comparison failure!
> > 
> > gcc/gm2/gm2-compiler-boot/M2Version.o differs
> > 
> > Makefile:23761: recipe for target 'compare' failed
> > 
> > make[2]: *** [compare] Error 1
> > 
> > make[2]: Leaving directory '/home/dragisha/gm2/gm2/build'
> > 
> > Makefile:23740: recipe for target 'stage3-bubble' failed
> > 
> > make[1]: *** [stage3-bubble] Error 2
> > 
> > make[1]: Leaving directory '/home/dragisha/gm2/gm2/build'
> > 
> > Makefile:1007: recipe for target 'all' failed
> > 
> > make: *** [all] Error 2
> > 
> > 
> > 
> > Really?!??!?
> > 
> > Is it actually possible to make this on anything except this one
> > Debian 
> > box in basement somewhere?
> > 
> > I remember it was a hell to build it on a RPM system. But it was
> > ten 
> > years ago! On a RPM system!
> > 
> > I know mountain of work is put in gm2.. And I appreciate it a
> > lot!!! But 
> > this GCC, are those people crazy? It is 2020th, and whole mess they
> > made 
> > just got far worse in 25 years time I am trying to build things
> > with it.
> > 
> > Is it possible to get some sensible instructions, or binary
> > releases or 
> > anything except "Run son, run from Modula-2, and do not look back!"
> > 
> > Regards,
> > Dragiša
> > 
> > p.s. I also tried 9.2.0 branch from git... After I did sh 
> > ./combine-trees and got int scratch/sources/gm2... gcc 4.7.4 
> > everywhere... Ok, I thought, this is maybe bootstrap version... 
> > started... and it failed after gazillion of warnings, lots of
> > magenta 
> > and purple and then just dies with some stupid error, gnu_inline
> > something.
> 
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]