Re: Trouble building 2.49.60 beta on Fedora

[Jerry J. <log...@gm...>]

Thanks again, Bruno, for the patches.  They don't apply cleanly to
either the 2.49.60 beta release or to current mercurial head, though.
What version of the code are those patches against?

Sadly, the patches have not improved the situation.  The 32- and
64-bit x86 and 32-bit ARM builds still succeed, and all of the others
segfault now.  I'm not sure if you can follow this link or not, but if
you can, build logs will be here for a few days:

https://koji.fedoraproject.org/koji/taskinfo?taskID=21412890

That build was against mercurial revision 820ad4b724cb, with the
following patches:

- A patch to fix the ARM build:
http://sourceforge.net/tracker/?func=detail&aid=3529615&group_id=1355&atid=301355
- A patch to fix configure detection of Berkeley DB:
http://sourceforge.net/tracker/?func=detail&aid=3572516&group_id=1355&atid=301355
- A patch to add definitions for ERFKILL and EHWPOISON, and to remove
the definition of cfree, which has been dropped from recent versions
of glibc (attached).
- The gdbm patch I sent with the initial email
- The ppc64 and aarch64 patches you have sent in this thread, adapted
to apply to the mercurial revision noted above.

Also, Fedora builds with -Werror=format-security, so I had to change
one line in the aarch64 patch.  That patch modifies spvw_allocate.d
and in one place issues a warning.  I had to change this line:

fprintf(stderr, GETTEXTL("Warning: "));

to:

fputs(GETTEXTL("Warning: "),stderr);

since the string is non-constant, and therefore triggers the format
security error.

I just noticed that we add these flags when building for ppc64/ppc64le:

-DNO_GENERATIONAL_GC -DNO_MULTIMAP_FILE -DNO_SINGLEMAP

That part of the spec file predates my involvement, so I don't know
why they are in there.  Should we be using those flags?

Please let me know if there is anything I can do to help debug these
segfaults further.  Regards,
-- 
Jerry James
http://www.jamezone.org/