Hi Matthias, Right. Before, I erased the old log and did "sage -i gfan".
Now, I did "sage -f gfan", which failed again. I have posted the new log under the old url. Best regards, Simon On 2021-08-30, Matthias Köppe <[email protected]> wrote: > Well, then the gfan.log that you shared cannot possibly come from the same > install as the config.log that you shared. Can you run "./sage -f gfan" > again? > > From your log: > Building gfan-0.6.2.p1 > g++ -O2 -g -march=native -DNOCDDPREFIX -DGMPRATIONAL -Wuninitialized > -fno-omit-frame-pointer -O2 -g -c src/polynomialgcd.cpp -o > src/polynomialgcd.o > > It should say: > Building gfan-0.6.2.p1 > g++ -std=gnu++11 -O2 -g -march=native -DNOCDDPREFIX -DGMPRATIONAL > -Wuninitialized -fno-omit-frame-pointer -O2 -g -c > src/polynomialgcd.cpp -o src/polynomialgcd.o > > > On Monday, August 30, 2021 at 11:21:58 AM UTC-7 Simon King wrote: > >> Hi Matthias, >> >> On 2021-08-30, Matthias Köppe <[email protected]> wrote: >> > ./configure correctly determines that it needs to use CXX='g++ >> > -std=gnu++11' to work with this old compiler. >> > Check if you have environment variables CC or CXX set in your global >> > environment -- they should be unset; otherwise, they will override the >> > values determined by ./configure. (This is nonstandard behavior of our >> > build system.) >> >> In a shell: >> king@klap:~/Sage/git/sage$ echo $CC >> >> king@klap:~/Sage/git/sage$ echo $CXX >> >> So, it is not set. >> In a Sage shell: >> (sage-sh) king@klap:sage$ echo $CC >> gcc >> (sage-sh) king@klap:sage$ echo $CXX >> g++ -std=gnu++11 >> >> This is what it should be, right? >> >> Best regards, >> Simon >> > >> > On Sunday, August 29, 2021 at 3:04:34 PM UTC-7 Simon King wrote: >> > >> >> Hi Matthias, >> >> >> >> the two logs are at https://users.fmi.uni-jena.de/~king/logs/ >> >> >> >> Best regards, >> >> Simon >> >> >> >> On 2021-08-29, Matthias Köppe <[email protected]> wrote: >> >> > Singular vendors a part of gfan called gfanlib. Perhaps an >> installation >> >> of >> >> > that is leaking into your build. >> >> > >> >> > If you can share your top-level config.log and the full gfan build >> log, >> >> we >> >> > can take a closer look. >> >> > >> >> > On Sunday, August 29, 2021 at 11:50:32 AM UTC-7 Simon King wrote: >> >> > >> >> >> Hi Matthias, >> >> >> >> >> >> On 2021-08-29, Matthias Köppe <[email protected]> wrote: >> >> >> > On Sunday, August 29, 2021 at 5:44:33 AM UTC-7 Dima Pasechnik >> wrote: >> >> >> > >> >> >> >> is gfan partially taken from the system? >> >> >> >> >> >> >> >> probably. Ubuntu 16.04 has gfan version 0.5, but Sage needs >> 0.6.2. >> >> >> >> A system-wide install of old gfan might get in the way. >> >> >> > >> >> >> > No, that alone cannot explain it -- we test this configuration. >> >> >> > ubuntu-xenial-standard installs the system gfan, then rejects it, >> >> then >> >> >> > correctly builds gfan. >> >> >> >> >> >> What could explain it? Is there a typical application that I might >> have >> >> >> installed and depends on gfan? I mean, it is for Groebner fans. So, >> what >> >> >> *non-mathematical* software would use it? I don't think that I >> installed >> >> >> a mathematical software after the last successful build of Sage. >> >> >> >> >> >> Should I try to uninstall gfan, re-install it, and try again? And, >> >> >> if that fails, uninstall and NOT re-install, but build Sage and hope >> >> >> that it provides a working gfan? >> >> >> >> >> >> Best regards, >> >> >> Simon >> >> >> >> >> >> >> >> > >> >> >> >> >> > >> >> > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/sgjk9g%243p8%241%40ciao.gmane.io.
