Le mar. 14 juin 2022 à 23:05, Sebastian Andrzej Siewior <
sebast...@breakpoint.cc> a écrit :
> On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote:
> > Hi Sebastian,
> Hi,
>
> > Any hint or idea about this ? Even wild ideas that I could try,
> > before I have to remove the files from mips.
>
> I conf
On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote:
> Hi Sebastian,
Hi,
> Any hint or idea about this ? Even wild ideas that I could try,
> before I have to remove the files from mips.
I confirmed on eller that nodejs 16.15.0+dfsg-1 builds with openssl
3.0.3-7. I was about to give-it-back but then
control: forwarded -1 https://github.com/openssl/openssl/issues/18535
On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote:
> Hi Sebastian,
Hi,
> Any hint or idea about this ? Even wild ideas that I could try,
> before I have to remove the files from mips.
Okay. So if you do
OPENSSL_init_cry
On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote:
> Hi Sebastian,
Hi,
> Any hint or idea about this ? Even wild ideas that I could try,
> before I have to remove the files from mips.
I added RAND_status() as the first instruction in Start() (src/node.cc)
before InitializeOncePerProcess(). With th
On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote:
> Hi Sebastian,
Hi,
> Any hint or idea about this ? Even wild ideas that I could try,
> before I have to remove the files from mips.
before I forget:
on amd64 the entry point to init is:
| #0 OPENSSL_init_crypto (opts=opts@entry=64, settings=set
On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote:
> Hi Sebastian,
Hi Jérémy,
> Any hint or idea about this ? Even wild ideas that I could try,
> before I have to remove the files from mips.
for some reason ossl_err_load_crypto_strings() is not invoked on mipsel
but is invoked on amd64. Therefore
Hi Sebastian,
Le dim. 29 mai 2022 à 16:27, Jérémy Lal a écrit :
>
>
> Le jeu. 26 mai 2022 à 19:23, Sebastian Andrzej Siewior <
> sebast...@breakpoint.cc> a écrit :
>
>> On 2022-05-26 13:49:13 [+0200], Jérémy Lal wrote:
>> > Thanks for the feedback.
>> np.
>>
>> > Indeed, the latest nodejs versio
Le jeu. 26 mai 2022 à 19:23, Sebastian Andrzej Siewior <
sebast...@breakpoint.cc> a écrit :
> On 2022-05-26 13:49:13 [+0200], Jérémy Lal wrote:
> > Thanks for the feedback.
> np.
>
> > Indeed, the latest nodejs version (18.x) embeds an updated openssl.cnf,
> > which is exactly the one
> > of the o
On 2022-05-26 13:49:13 [+0200], Jérémy Lal wrote:
> Thanks for the feedback.
np.
> Indeed, the latest nodejs version (18.x) embeds an updated openssl.cnf,
> which is exactly the one
> of the openssl debian package, without the [ssl_sect] part at the end.
>
> Why this fails only on mipsel is a mys
Le jeu. 26 mai 2022 à 09:57, Sebastian Andrzej Siewior <
sebast...@breakpoint.cc> a écrit :
> On 2022-05-20 13:07:55 [+0200], Jérémy Lal wrote:
> > nodejs dynamically links to openssl, and since openssl >= 3,
> > on mipsel, some of its tests are failing, see
> > https://buildd.debian.org/status/pa
On 2022-05-20 13:07:55 [+0200], Jérémy Lal wrote:
> nodejs dynamically links to openssl, and since openssl >= 3,
> on mipsel, some of its tests are failing, see
> https://buildd.debian.org/status/package.php?p=nodejs
>
> The failures look like openssl was configured with no-err, e.g:
> Asserti
Package: openssl
Version: 3.0.3-4
Severity: normal
Hi,
nodejs dynamically links to openssl, and since openssl >= 3,
on mipsel, some of its tests are failing, see
https://buildd.debian.org/status/package.php?p=nodejs
The failures look like openssl was configured with no-err, e.g:
AssertionErr
12 matches
Mail list logo
