Hi,
Ludovic Courtès skribis:
> I have tested the following patch and successfully built nss on
> i686-linux with it:
I pushed it as 21fe1e077aa77488bd413ef3255973c60d7468fe on
‘core-updates’.
Ludo’.
Hi,
Christopher Baines skribis:
>> My suggestion would be to:
>>
>> (substitute* "nss/tests/gtests/gtests.sh"
>> (("SOURCE_DIR=.*")
>> (string-append "SOURCE_DIR=" (getcwd) "/nss\n")))
>>
>> WDYT?
>
> That looks good to me.
I have tested the following patch and successfully built nss
Ludovic Courtès writes:
> Hi!
>
> Christopher Baines skribis:
>
>> When running without datefudge, the tests work and the cd in gtests.sh
>> seems to fail:
>>
>> Running tests for gtests
>> TIMESTAMP gtests BEGIN: Mon Jul 22 10:09:27 UTC 2024
>> ./gtests.sh: line 25: cd: ./nss/tests: No such fil
Hi!
Christopher Baines skribis:
> When running without datefudge, the tests work and the cd in gtests.sh
> seems to fail:
>
> Running tests for gtests
> TIMESTAMP gtests BEGIN: Mon Jul 22 10:09:27 UTC 2024
> ./gtests.sh: line 25: cd: ./nss/tests: No such file or directory
> /tmp/guix-build-nss-3
Ludovic Courtès writes:
> Ludovic Courtès skribis:
>
>> So the easiest short-term solution seems to be using datefudge to run
>> the ‘nss’ tests on 32-bit platforms, as Chris already suggested before
>> (patch below; it’s being built right now, I’ll see tomorrow if it
>> worked…).
>
> It failed:
Ludovic Courtès skribis:
> So the easiest short-term solution seems to be using datefudge to run
> the ‘nss’ tests on 32-bit platforms, as Chris already suggested before
> (patch below; it’s being built right now, I’ll see tomorrow if it
> worked…).
It failed:
--8<---cut here---
Hi,
This bug report is to keep track of the discussions around libfaketime
for i686-linux. Right now, libfaketime segfaults when used to run the
test suite of ‘nss’ on i686-linux. This can be reproduced in a simple
way as of ‘core-updates’ commit
05e6bd3efe1b03190839d2b91b09fa768c4ef83c:
--8<--
