> And no, it doesn't help to state "the bug is still there" without addressing it.
And your reply to my 5 month old comment serves no purpose and in no way helps either. I am not in a position to do anything about this, so suggesting that I should is not helpful. I am not familiar with the process, nor am I paid to develop Ubuntu. They have people for that and I do not have the time. I have done my part as a user by reporting the bug. Most active projects do appreciate and address bug reports. It does seem strange to me that the exception to that often seems to be commercially backed projects. Source and pre-rolled packages are available to address the issue if they so wish. If they want to keep distributing broken packages, then it is frustrating for users but it is not my problem. If the package is not going to be fixed, and given that as it stands it is completely non- functional, it would actually be better from a user experience perspective for it to simply be removed than to keep it live, in my opinion. In any case, why would I spend my time trying to get this fixed when I have been using the compiler distribution directly from ARM reasonably comfortably every day since I reported this bug? I need an arm-none compiler for work, and I will take the fastest route to get one, anything else is a waste of time when I have deadlines to meet. The fastest and thus most optimal route for any user is to find an alternative provider for the package, especially given that in this case the next OS release will likely have fixed the issue anyway. And yes, expressing my surprise that the completely broken package has not been replaced with the fully working package is not particularly helpful, but it is certainly not damaging. On the other hand, successive experiences of broken packages and this type of interaction may move some users away from Ubuntu in the longer term. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767223 Title: multilib selects wrong start files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-arm-none-eabi/+bug/1767223/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
