[Bug libbacktrace/114941] libbacktrace build is broken for FDPIC uclibc targets by r14-5173-g2b64e4a54042

2024-05-27 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114941 --- Comment #4 from jcmvbkbc at gcc dot gnu.org --- Proposed fix: https://gcc.gnu.org/pipermail/gcc-patches/2024-May/652798.html

[Bug libbacktrace/114941] libbacktrace build is broken for FDPIC uclibc targets by r14-5173-g2b64e4a54042

2024-05-04 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114941 --- Comment #3 from jcmvbkbc at gcc dot gnu.org --- (In reply to Ian Lance Taylor from comment #2) > What is the correct way to get the address at which the shared library was > loaded when using FDPIC? There's no single base address in case of

[Bug libbacktrace/114941] libbacktrace build is broken for FDPIC uclibc targets by r14-5173-g2b64e4a54042

2024-05-03 Thread ian at airs dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114941 Ian Lance Taylor changed: What|Removed |Added CC||ian at airs dot com --- Comment #2

[Bug libbacktrace/114941] libbacktrace build is broken for FDPIC uclibc targets by r14-5173-g2b64e4a54042

2024-05-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114941 --- Comment #1 from Andrew Pinski --- So a patch like what was done in r0-56719-g34208acf14fa02 needs to be done to libbacktrace . Basically this has always been broken.