[Bug c/84173] Support glibc multiarch interpreter names

2018-02-11 Thread javier--1JjCLmwH3DOs1h35RYKsyJrkQzDNHN at jasp dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84173 Javier Serrano Polo changed: What|Removed |Added Resolution|INVALID |WONTFIX --- Comment #15 from Javi

[Bug c/84173] Support glibc multiarch interpreter names

2018-02-08 Thread javier--1JjCLmwH3DOs1h35RYKsyJrkQzDNHN at jasp dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84173 --- Comment #14 from Javier Serrano Polo --- (In reply to Adam Conrad from comment #13) > Please stop speaking as if you speak for the Debian toolchain maintainers, > or Debian as a whole. You don't. I do not represent Debian, but I state fact

[Bug c/84173] Support glibc multiarch interpreter names

2018-02-07 Thread javier--1JjCLmwH3DOs1h35RYKsyJrkQzDNHN at jasp dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84173 --- Comment #12 from Javier Serrano Polo --- Created attachment 43357 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43357&action=edit Initial support for multiarch interpreters (In reply to Marc Glisse from comment #11) > If you intend t

[Bug c/84173] Support glibc multiarch interpreter names

2018-02-04 Thread javier--1JjCLmwH3DOs1h35RYKsyJrkQzDNHN at jasp dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84173 --- Comment #10 from Javier Serrano Polo --- (In reply to Joseph S. Myers from comment #9) > Not a bug. The appropriate time to raise such an issue is if in future > there is otherwise consensus to have a major libc ABI break and move to > libc

[Bug c/84173] Support glibc multiarch interpreter names

2018-02-03 Thread javier--1JjCLmwH3DOs1h35RYKsyJrkQzDNHN at jasp dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84173 Javier Serrano Polo changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|IN

[Bug c/84173] Support glibc multiarch interpreter names

2018-02-02 Thread javier--1JjCLmwH3DOs1h35RYKsyJrkQzDNHN at jasp dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84173 --- Comment #6 from Javier Serrano Polo --- > As long as the new behavior is optional (not the default), the patch stands a > chance of being accepted. Thank you. I will change the status of the report if you do not mind. > the discussion about

[Bug c/84173] Support glibc multiarch interpreter names

2018-02-01 Thread javier--1JjCLmwH3DOs1h35RYKsyJrkQzDNHN at jasp dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84173 --- Comment #3 from Javier Serrano Polo --- Upstream wants to make multiarch harder; the patch will not be posted here. Nevertheless, Adam, please answer to my previous question.

[Bug c/84173] Support glibc multiarch interpreter names

2018-02-01 Thread javier--1JjCLmwH3DOs1h35RYKsyJrkQzDNHN at jasp dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84173 Javier Serrano Polo changed: What|Removed |Added CC||adconrad at 0c3 dot net --- Comme

[Bug c/84173] New: Support glibc multiarch interpreter names

2018-02-01 Thread javier--1JjCLmwH3DOs1h35RYKsyJrkQzDNHN at jasp dot net
Assignee: unassigned at gcc dot gnu.org Reporter: javier--1JjCLmwH3DOs1h35RYKsyJrkQzDNHN at jasp dot net Target Milestone: --- Preferred multiarch names refer to the /lib directory and are unique, e.g. /lib/ld-linux-x86-64.so.2. Please consider accepting a future patch that