[sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

Dear all, Thank you very much for your answers. I can now understand that I was building incrementally, but I do not understand what was the issue. Finally, after many attempts, what was successful was: >sudo make distclean and then >make build I am not sure why the sudo was necessary, but its

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

Don't worry too much about this one, Trac#24107 is under way (slowly, I know... There is a ton of docs to understand and update...). -- Emmanuel Charpentier Le lundi 4 décembre 2017 16:13:26 UTC+1, Thierry (sage-googlesucks@xxx) a écrit : > > On Mon, D

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On 2017-12-04 16:04, Thierry wrote: The problem in just rebuilding is that there might be old files lying around still interacting Well, those shouldn't interact. If they do, that's a bug. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsu

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On Mon, Dec 04, 2017 at 04:13:20PM +0100, Thierry wrote: [...] > perhaps python is a "dependent" of openssl spkg, not a "dependency", or > perhaps it is a "dependency" of some virtual openssl package that will be Damn, of course i meant the other way (python depends on meta-openssl, so meta-opens

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On Mon, Dec 04, 2017 at 03:58:03PM +0100, Erik Bray wrote: > On Mon, Dec 4, 2017 at 3:47 PM, Jeroen Demeyer wrote: > > On 2017-12-04 15:37, Thierry wrote: > >> > >> No, we have to be able to remove all the old stuff from the package. > > > > > > You said "rebuilds the package and its dependencies"

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On Mon, Dec 04, 2017 at 03:47:31PM +0100, Jeroen Demeyer wrote: > On 2017-12-04 15:37, Thierry wrote: > >No, we have to be able to remove all the old stuff from the package. > > You said "rebuilds the package and its dependencies" but you really mean > "uninstalls the package and its dependencies"

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On Mon, Dec 4, 2017 at 3:47 PM, Jeroen Demeyer wrote: > On 2017-12-04 15:37, Thierry wrote: >> >> No, we have to be able to remove all the old stuff from the package. > > > You said "rebuilds the package and its dependencies" but you really mean > "uninstalls the package and its dependencies" (pos

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On 2017-12-04 15:37, Thierry wrote: No, we have to be able to remove all the old stuff from the package. You said "rebuilds the package and its dependencies" but you really mean "uninstalls the package and its dependencies" (possibly followed by a rebuild which is just a normal build at that

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On Mon, Dec 04, 2017 at 03:31:13PM +0100, Jeroen Demeyer wrote: > On 2017-12-04 15:23, Thierry wrote: > >A great improvement in > >the dev workflow would be to have a kind of "make clean " that > >rebuilds the package and its dependencies > > Doesn't "make -B " do something like that? I haven't tr

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On 2017-12-04 15:23, Thierry wrote: A great improvement in the dev workflow would be to have a kind of "make clean " that rebuilds the package and its dependencies Doesn't "make -B " do something like that? I haven't tried. -- You received this message because you are subscribed to the Google

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On 2017-12-04 15:23, Thierry wrote: i would vote to consider such issues as not-a-bug I would *personally* report it as a bug if it would happen to me and I know what causes it. Upgrade failures can be because of real bugs. For example, if this would happen on every beta, it would be quite an

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On Mon, Dec 4, 2017 at 3:23 PM, Thierry wrote: > Hi, > > On Mon, Dec 04, 2017 at 03:00:07PM +0100, Jeroen Demeyer 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

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

Hi, On Mon, Dec 04, 2017 at 03:00:07PM +0100, Jeroen Demeyer 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.

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On Mon, Dec 4, 2017 at 3:00 PM, Jeroen Demeyer 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 o

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

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

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On Monday, December 4, 2017 at 9:37:42 AM UTC, Jeroen Demeyer wrote: > > On 2017-12-04 00:46, Dima Pasechnik wrote: > > I saw this as well, while incrementally building 8.1.rc4. > > I cannot reproduce this... > Anyway, it's not a bug. Of course it's not possible to test for all the possible

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

On 2017-12-04 00:46, Dima Pasechnik wrote: I saw this as well, while incrementally building 8.1.rc4. I cannot reproduce this... -- 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, se

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

This seems to be a red herring. I saw this as well, while incrementally building 8.1.rc4. The problem when away after make distclean and re-building from scratch. On Saturday, December 2, 2017 at 12:56:57 PM UTC, Dima Pasechnik wrote: > > it seems to be > > undefined symbol: _PySlice_Unpack >

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

it seems to be undefined symbol: _PySlice_Unpack in both cases here. There was something of this sort mentioned here: https://bugs.python.org/issue30074 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop rece

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

Nils, in your case were you building from scratch or it was an update of an existing compiled version? Did you try on the 8.1.rc4? It would be a mess to have 8.1 out with this failure. Vincent On 02/12/2017 13:11, Nils Bruin wrote: I actually had a similar problem when building the latest "de

[sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

as well, it's not clear whether you try to build from scratch, and what release... On Friday, December 1, 2017 at 9:20:42 PM UTC, Dima Pasechnik wrote: > > Do you have LD_LIBRARY_PATH set to something? > > > On Friday, December 1, 2017 at 5:36:29 PM UTC, Tristan Vaccon wrote: >> >> Hi everyone,

[sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

Do you have LD_LIBRARY_PATH set to something? On Friday, December 1, 2017 at 5:36:29 PM UTC, Tristan Vaccon wrote: > > Hi everyone, > > I am working on a guest Ubuntu LTS 16.04 inside a Windows 7 host, using a > Virtual Machine (VMWare Workstation 12 Player). > I am using git trac and I have iss