On Mon, Dec 4, 2017 at 3:00 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2017-12-04 10:53, Dima Pasechnik wrote: >> >> Anyway, it's not a bug. > > > We are supposed to support incremental builds, so it is a bug. There have > been several reports of if, so it cannot be due to one misconfigured system. > On the other hand, nobody has bothered to create a ticket for it, so maybe > it's not a serious bug.
I have seen something like this as well when switching between some older and newer branches. I think there's a possibility I introduced a regression in https://trac.sagemath.org/ticket/23781, but this is just a guess given that it's the most significant reworking of the Python spkg build of late. I don't know exactly what the problem would be--I'd have to make an explicit effort to reproduce it. I also haven't seen this exact problem manifest, but rather problems having to do with old versions of libpython being linked to incorrectly. I also can't remember on what platform I've seen problems, because there was a Cygwin-specific regression (https://trac.sagemath.org/ticket/24189) introduced by #23781 but that wouldn't have any impact on Ubuntu. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
