Repository navigation
Support building without embedded libbacktrace #248
Description
Our python setup requires cross compiling, which isn't working because of ./configure running within setup.py. I have locally patched out the embedded libbacktrace and replaced it with link opts to a cross compiled libbacktrace. It would be nice to not need the patch; perhaps you would accept an patch to have an environment var that drops the libbacktrace embed stuff (and maybe append -lbacktrace)?
I would like to know whether you would accept such a patch before submitting a PR.
Activity
mattip commentedon May 7, 2022
Do you mean you are using the
libbacktracesources in this repo to build a cross compiled version withoutconfigure? Could we adopt the direct call to the compiler/linker for all the builds withoutconfigure?jhance commentedon May 8, 2022
No, I actually built it from upstream source and linked it statically in with some flag (iirc
--extra-link-objectsor something). In my patch tovmprof-pythonI removed all traces of thelibbacktraceembed fromsetup.pyas I no longer need the embedded copy.My specific use case is really just that I'm trying to target a newer glibc than is on the system (so
./configurebails when it realizes it can't run the binaries it compiles)Not running
configureis not really feasible in the general case (in this case am buildinglibbacktracewith a preconfigured output forconfig.hand so forth to suit the cross compilation.mattip commentedon May 9, 2022
The change would be to have a configuration option to use the native
libbacktrace?