Hi, my nightly fetch-PyPy build job stopped working two days ago because the nightly builds now require libssl 1.0.0. It's not currently available on our integration test server. Is that dependency really necessary or was it just an accidental side effect of a system update? Stefan
On Fri, Aug 31, 2012 at 9:22 AM, Stefan Behnel <stefan_ml@behnel.de> wrote:
Hi,
my nightly fetch-PyPy build job stopped working two days ago because the nightly builds now require libssl 1.0.0. It's not currently available on our integration test server.
Is that dependency really necessary or was it just an accidental side effect of a system update?
Stefan
This was an effect of a system update. Binary compatibility on linux is hard :/ Cheers, fijal
Hi, On Fri, Aug 31, 2012 at 9:27 AM, Maciej Fijalkowski <fijall@gmail.com> wrote:
This was an effect of a system update. Binary compatibility on linux is hard :/
I hacked *yet again another time* to link openssl statically in the binary, like it should have been before. A bientôt, Armin.
Armin Rigo, 31.08.2012 10:15:
On Fri, Aug 31, 2012 at 9:27 AM, Maciej Fijalkowski wrote:
This was an effect of a system update. Binary compatibility on linux is hard :/
I hacked *yet again another time* to link openssl statically in the binary, like it should have been before.
The same applies to libffi.so.6 now. Stefan
Given that binary compatibility on linux is practically a broken mess thats just burning developer time, we might want standardize on a distro that nightly/releases work on and defer the distro compat to the people at fault - the distributions -- Ronny On 09/29/2012 01:19 PM, Stefan Behnel wrote:
Armin Rigo, 31.08.2012 10:15:
On Fri, Aug 31, 2012 at 9:27 AM, Maciej Fijalkowski wrote:
This was an effect of a system update. Binary compatibility on linux is hard :/
I hacked *yet again another time* to link openssl statically in the binary, like it should have been before.
The same applies to libffi.so.6 now.
Stefan
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Stefan Behnel, 29.09.2012 13:19:
Armin Rigo, 31.08.2012 10:15:
On Fri, Aug 31, 2012 at 9:27 AM, Maciej Fijalkowski wrote:
This was an effect of a system update. Binary compatibility on linux is hard :/
I hacked *yet again another time* to link openssl statically in the binary, like it should have been before.
The same applies to libffi.so.6 now.
Oh, and after getting around that problem, the next on the list is "libtinfo.so.5", which, it seems, is part of ncurses? This is starting to get tedious ... Stefan
or statically link everything in... at least people will be able to run pypy on their machines. On Sat, Sep 29, 2012 at 8:36 AM, Ronny Pfannschmidt <Ronny.Pfannschmidt@gmx.de> wrote:
Given that binary compatibility on linux is practically a broken mess thats just burning developer time, we might want standardize on a distro that nightly/releases work on and defer the distro compat to the people at fault - the distributions
-- Ronny
On 09/29/2012 01:19 PM, Stefan Behnel wrote:
Armin Rigo, 31.08.2012 10:15:
On Fri, Aug 31, 2012 at 9:27 AM, Maciej Fijalkowski wrote:
This was an effect of a system update. Binary compatibility on linux is hard :/
I hacked *yet again another time* to link openssl statically in the binary, like it should have been before.
The same applies to libffi.so.6 now.
Stefan
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
-- Leonardo Santagada
i vaguely remember that its impossible to statically link glibc, due to libnss On 09/29/2012 03:55 PM, Leonardo Santagada wrote:
or statically link everything in... at least people will be able to run pypy on their machines.
On Sat, Sep 29, 2012 at 8:36 AM, Ronny Pfannschmidt <Ronny.Pfannschmidt@gmx.de> wrote:
Given that binary compatibility on linux is practically a broken mess thats just burning developer time, we might want standardize on a distro that nightly/releases work on and defer the distro compat to the people at fault - the distributions
-- Ronny
On 09/29/2012 01:19 PM, Stefan Behnel wrote:
Armin Rigo, 31.08.2012 10:15:
On Fri, Aug 31, 2012 at 9:27 AM, Maciej Fijalkowski wrote:
This was an effect of a system update. Binary compatibility on linux is hard :/
I hacked *yet again another time* to link openssl statically in the binary, like it should have been before.
The same applies to libffi.so.6 now.
Stefan
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
On Sat, Sep 29, 2012 at 3:55 PM, Leonardo Santagada <santagada@gmail.com> wrote:
or statically link everything in... at least people will be able to run pypy on their machines.
you cannot statically link glibc and libffi is compiled without -fPIC on debian/ubuntu to make it harder
On Sat, Sep 29, 2012 at 8:36 AM, Ronny Pfannschmidt <Ronny.Pfannschmidt@gmx.de> wrote:
Given that binary compatibility on linux is practically a broken mess thats just burning developer time, we might want standardize on a distro that nightly/releases work on and defer the distro compat to the people at fault - the distributions
-- Ronny
On 09/29/2012 01:19 PM, Stefan Behnel wrote:
Armin Rigo, 31.08.2012 10:15:
On Fri, Aug 31, 2012 at 9:27 AM, Maciej Fijalkowski wrote:
This was an effect of a system update. Binary compatibility on linux is hard :/
I hacked *yet again another time* to link openssl statically in the binary, like it should have been before.
The same applies to libffi.so.6 now.
Stefan
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
--
Leonardo Santagada _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Hi, On Sat, Sep 29, 2012 at 5:35 PM, Maciej Fijalkowski <fijall@gmail.com> wrote:
or statically link everything in... at least people will be able to run pypy on their machines.
you cannot statically link glibc and libffi is compiled without -fPIC on debian/ubuntu to make it harder
To summarize: it's an infinite amount of mess that we are running away from. If someone, anyone, feels like helping --- and is ready to put in the necessary amount of work, including never-ending future work --- then in this case I'd be happy to leave him the job of correctly configuring "tannit", the machine we use. Otherwise, people with different distributions will have to wait for the next release to be packaged for their distribution. Or else find themselves a machine with sufficient RAM and 1-2 free hours, which is not that hard any more IMHO. It is documented how to get a "squeezed" translation (for 30% more time) in 1.6GB of RAM (32-bit) or 3.0GB of RAM (64-bit) at http://pypy.org/download.html#building-from-source . A bientôt, Armin.
participants (5)
-
Armin Rigo -
Leonardo Santagada -
Maciej Fijalkowski -
Ronny Pfannschmidt -
Stefan Behnel