Am Mon, Mar 20, 2023 at 09:02:01PM +0100 schrieb Michael Schierl:
> Seems that you accidentally attached the object file (binary) instead of
> the assembly output. :-)
Hm, I had accidentally written the assembly output to a .o file, and then
apparently accidentally overwritten the file before
Hello Andreas,
Am 20.03.2023 um 15:54 schrieb Andreas Enge:
Hello Michael,
I am attaching a simplified C file and the corresponding assembly
output; which I cannot read, but there are differences between the two
invocations of fprintf.
Seems that you accidentally attached the object file
Hi Felix,
--- Original Message ---
On Sunday, March 19th, 2023 at 5:49 PM, Felix Lechner via "Development of GNU
Guix and the GNU System distribution." wrote:
>
>
> Hi Andreas,
>
> On Sat, Mar 18, 2023 at 5:33 AM Andreas Enge andr...@enge.fr wrote:
>
> > FAIL:
Hi Andreas,
On Sat, Mar 18, 2023 at 5:33 AM Andreas Enge wrote:
>
> FAIL: strtod_nol_or_err("123") != 123.00
Can you multiply by "1.0" to force a floating-point comparison, or
round the other side to the nearest int?
Kind regards
Felix
Hello Andreas,
Am 18.03.2023 um 13:32 schrieb Andreas Enge:
Has anyone got any explanation for this behaviour? A compiler error?
Nasal daemons are not a compiler error.
Anyway, getting an assembly listing from your gcc version (using the -S
switch) would reduce the guesswork. Pass the same
Am Sat, Mar 18, 2023 at 01:38:48PM -0400 schrieb Leo Famulari:
> I recommend trying the latest upstream version, 4.0.3. The Sourceforge
> download page points to the new canonical location:
I already tried, it does not change anything. If I mess with the package,
I would in any case update the
I recommend trying the latest upstream version, 4.0.3. The Sourceforge
download page points to the new canonical location:
https://gitlab.com/procps-ng/procps
If that doesn't work, I would just disable the test, unless there is
some authoritative upstream opinion about which patch to apply.
