Error building gcc-4.9.3.pl on old ticket

[Anna Haensch]

Hi All, 

I'm returning to an old ticket that's been on trac for awhile (#19112...most recent milestone Sage-7.1).  The patchbot has failed, so I know that something isn't right.  I just tried to download and "make"

 the branch and it raised an error, see below: 

[gcc-4.9.3.p1] #define _VSTD std::_LIBCPP_NAMESPACE

[gcc-4.9.3.p1]               ^

[gcc-4.9.3.p1] ../../src/gcc/system.h:685:13: note: 'fancy_abort' declared here

[gcc-4.9.3.p1] extern void fancy_abort (const char *, int, const char *) ATTRIBUTE_NORETURN;

[gcc-4.9.3.p1]             ^

[gcc-4.9.3.p1] 1 error generated.

[gcc-4.9.3.p1] make[6]: *** [c/c-objc-common.o] Error 1

[gcc-4.9.3.p1] make[5]: *** [all-stage1-gcc] Error 2

[gcc-4.9.3.p1] make[4]: *** [stage1-bubble] Error 2

[gcc-4.9.3.p1] make[3]: *** [all] Error 2

[gcc-4.9.3.p1] 

[gcc-4.9.3.p1] real 1m59.934s

[gcc-4.9.3.p1] user 1m8.342s

[gcc-4.9.3.p1] sys 0m39.540s

[gcc-4.9.3.p1] ************************************************************************

[gcc-4.9.3.p1] Error installing package gcc-4.9.3.p1

[gcc-4.9.3.p1] ************************************************************************

[gcc-4.9.3.p1] Please email sage-devel (http://groups.google.com/group/sage-devel)

[gcc-4.9.3.p1] explaining the problem and including the relevant part of the log file

[gcc-4.9.3.p1]   /Users/annahaensch/sage-8.7/logs/pkgs/gcc-4.9.3.p1.log

[gcc-4.9.3.p1] Describe your computer, operating system, etc.

[gcc-4.9.3.p1] If you want to try to fix the problem yourself, *don't* just cd to

[gcc-4.9.3.p1] /Users/annahaensch/sage-8.7/local/var/tmp/sage/build/gcc-4.9.3.p1 and type 'make' or whatever is appropriate.

[gcc-4.9.3.p1] Instead, the following commands setup all environment variables

[gcc-4.9.3.p1] correctly and load a subshell for you to debug the error:

[gcc-4.9.3.p1]   (cd '/Users/annahaensch/sage-8.7/local/var/tmp/sage/build/gcc-4.9.3.p1' && '/Users/annahaensch/sage-8.7/sage' --sh)

[gcc-4.9.3.p1] When you are done debugging, you can type "exit" to leave the subshell.

[gcc-4.9.3.p1] ************************************************************************

make[2]: *** [/Users/annahaensch/sage-8.7/local/var/lib/sage/installed/gcc-4.9.3.p1] Error 1

make[1]: *** [all-toolchain] Error 2

real 3m39.023s

user 2m7.206s

sys 1m13.820s

***************************************************************

Error building Sage.

The following package(s) may have failed to build (not necessarily

during this run of 'make all'):

* package: gcc-4.9.3.p1

  log file: /Users/annahaensch/sage-8.7/logs/pkgs/gcc-4.9.3.p1.log

  build directory: /Users/annahaensch/sage-8.7/local/var/tmp/sage/build/gcc-4.9.3.p1

The build directory may contain configuration files and other potentially

helpful information. WARNING: if you now run 'make' again, the build

directory will, by default, be deleted. Set the environment variable

SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

make: *** [all] Error 1

haenscha-ch:sage-8.7 annahaensch$ 

I imagine this is because the ticket is built on an out of date version of Sage.  I am using OS Mojave (10.14) and Xcode 10.1.  Just to be sure, I re-installed my command line tools and ran "make" on a more recent ticket, it built with to errors. 

Any ideas? 

Thanks! 

-Anna

[Dima Pasechnik]

patchbots are more or less OK, see my answer on the ticket.
You ought to rebase this branch over the latest beta, before trying to build it.
(it's based on a very old version of Sage that doesn't work on OSX
10.14, I think)

Hope this helps.

> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To post to this group, send email to sage-...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/b2c0f20b-f0ac-40f0-b8ea-a17dae8bbf06%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[E. Madison Bray]

To expand on Dima's answer, when resuming work on an old branch with intention of eventually merging it into the current development version (or at least a more recent develop in the near future), I would suggest habitually, if not *always* rebasing in the current version of develop. To summarize

$ git checkout develop

$ git pull

$ git checkout <name-of-feature-branch>

$ git rebase -i develop

as discussed a bit here https://doc.sagemath.org/html/en/developer/advanced_git.html?highlight=rebase#interactively-rebasing

Interactive rebase is useful to check that you're only picking those commits that are relevant to the branch. 

This is essentially the same as if you made a bunch of patch files based on your old branch, and then tried to apply those patches, in order, on top of the current develop branch. 

Depending on the size and complexity of the changes you might encounter merge conflicts in one or more of the commits, especially for an old branch. Each time that happens the rebase process will stop, ask you to manually resolve the conflicts, and then for each file modified you run `git add <filename>` and then when done run `git rebase --continue`. 

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq2cyqS%3D1uhRUq3n-s2UJGFOrrEaJGRbZm_GpmG6fWcc0Q%40mail.gmail.com.