Hi Frank, > Sure. Transcribing: > >> One generic issue came up with the port: enabling or disabling >> libmudflap depends on a factor (linker support for --wrap/-z wrap) >> that is best checked dynamically, thus doesn't really seem to belong >> at the toplevel. Is there any precedent for performing such a test >> in the target library and enabling or disabling depending on the >> outcome? [...] > > I don't know.
perhaps one of the build maintainers has a suggestion. For the time being, I'll juts continue with --enable-libmudflap. >> It seems the failures fall into only a few categories. It's >> probably best to analyse and fix those before checking in the patch. >> Where should we continue discussing the failures? Here or rather in >> the PR? > > Separate PRs would be best. I've now filed libmudflap/49549 Use of --noinhibit-exec is unportable libmudflap/49550 Many libmudflap tests fail on Solaris 11/x86 The second one almost certainly covers a couple of different issues, but I cannot identify them yet, so any help is appreciated. Rainer -- ----------------------------------------------------------------------------- Rainer Orth, Center for Biotechnology, Bielefeld University