This bug was fixed in the package newlib - 2.4.0.20160527-3ubuntu0.1
---
newlib (2.4.0.20160527-3ubuntu0.1) bionic; urgency=medium
* Change build dep from libisl-dev to libisl-0.18-dev,
as libcloog-isl-dev depends on that older version (LP: #1767223)
-- Dan Streetman Tue,
** Bug watch removed: github.com/bbcmicrobit/micropython/issues #514
https://github.com/bbcmicrobit/micropython/issues/514
--
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
I tested with libnewlib-arm-none-eabi and libnewlib-dev from bionic-
proposed:
bionic-proposed/universe amd64 libnewlib-arm-none-eabi all
2.4.0.20160527-3ubuntu0.1
bionic-proposed/universe amd64 libnewlib-dev all 2.4.0.20160527-3ubuntu0.1
I am pleased to report that the bug is fixed.
"readelf
Hello Ed, or anyone else affected,
Accepted newlib into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/newlib/2.4.0.20160527-3ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
fixed newlib package uploaded to bionic unapproved queue.
--
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
** Tags removed: verification-needed
--
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:
** Changed in: newlib (Ubuntu)
Status: Confirmed => Fix Released
** No longer affects: newlib (Ubuntu Cosmic)
** No longer affects: newlib (Ubuntu Disco)
** Changed in: newlib (Ubuntu Bionic)
Status: Fix Committed => Triaged
--
You received this bug notification because you are
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
--
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
Dear Adam and/or Simon,
I would like to test the new package. However, the page at
https://launchpad.net/ubuntu/+source/newlib/2.4.0.20160527-3build1
does not show any binaries available, and there is an icon
visible which is captioned "Failed to Build".
It's been 22 hours since the change was
I dug a little deeper and found that that the build failed with
the following error message:
"""
The following packages have unmet dependencies:
sbuild-build-depends-newlib-dummy : Depends: libcloog-isl-dev but it is not
going to be installed
E: Unable to correct problems, you have held broken
Hello Ed, or anyone else affected,
Accepted newlib into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/newlib/2.4.0.20160527-3build1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Uploaded to Bionic, it is now awaiting review by the SRU team.
** Changed in: newlib (Ubuntu Cosmic)
Status: Confirmed => Fix Released
** Changed in: newlib (Ubuntu Disco)
Status: Confirmed => Fix Released
** Changed in: newlib (Ubuntu Bionic)
Status: Triaged => In Progress
This issue is present in Bionic only. (Looking back at the discussion on
this bug, the package was confirmed working on Cosmic as of 2018-07-16.)
Best,
David
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi David!
Is this only an issue on Bionic, or Cosmic and Disco as well?
Thanks for the quick response.
--
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
Hi Simon, thank you very much for your attention to this bug as it has a
major impact for many of us users!
My understanding is that the diff required to fix this bug is the empty
diff. As Thomas said -- "This bug is due to newlib built against an
older version of gcc-arm-none-eabi. It will be
Hello Thomas, thank you for your work on this and I apologize for the
delay on this.
The Ubuntu Sponsors Team reviews packages which have a diff already
attached to the bug. Even if the solution is to just upgrade to the
package in Cosmic, in order to sponsor this, that's what we need.
Taking my
** Changed in: newlib (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: newlib (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: newlib (Ubuntu Disco)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: newlib (Ubuntu)
Status: New => Confirmed
--
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:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: newlib (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767223
** Also affects: newlib (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: newlib (Ubuntu Disco)
Importance: Undecided
Status: Confirmed
** Also affects: newlib (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: newlib (Ubuntu Bionic)
@ubuntu-sru and @ubuntu-sponsors: would you mind doing a new upload of
this package to bionic using the same source as in the last build? This
bug will be solved by rebuilding from the same source using the gcc-arm-
none-eabi package currently in bionic.
Best regards.
** Description changed:
+
This bug is due to newlib built against an older version of gcc-arm-
none-eabi. It will be fixed by rebuilding newlib using the same source.
** Package changed: gcc-arm-none-eabi (Ubuntu) => newlib (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
the universe section of the archive is mostly maintained by the Ubuntu
community. Non-paid, non-commercially. So you either work with them to
fix the issue, or live with it. No, I'm not willing to spend my free
time on this issue, and apparently you aren't either.
--
You received this bug
> 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
> but I don't understand why fixed packages are not available for
bionic.
because nobody stepped up to do the work?
See https://wiki.ubuntu.com/StableReleaseUpdates
See https://wiki.ubuntu.com/UbuntuBackports
And no, it doesn't help to state "the bug is still there" without
addressing it.
--
The bug is still present (2018-12-17).
Package version: 15:6.3.1+svn253039-1build1
--
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
I can confirm that this bug is still present in Bionic. The libnewlib-
arm-none-eabi package is unusable. Pulling in the fixed version from
upstream, or switching to the gcc-arm-embedded ppa, fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think they just don't care enough about the "universe" packages (or
don't have the time/resources to care), they are just importing them
from Debian's repos "as is" and very rarely update them, if ever.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That's good, but I don't understand why fixed packages are not available
for bionic. It's been almost 3 months! For now I will continue using the
cross compiler builds provided by ARM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upstream Debian has fixed the issue and Cosmic already has the new
packages. If you are on Bionic you can install the Cosmic packages to
temporarily fix the issue, see
https://github.com/bbcmicrobit/micropython/issues/514#issuecomment-404759614
** Bug watch added:
(The work around mentioned in my opening post only partially helps, my
code eventually crashes, presumably executing a libc or other stdlib
function)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, I think aside from building your own libc (and I'm not even certain
that would fix it) the only alternative at present is to use a different
toolchain or build your own. The binary toolchains from ARM
(https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads)
do however work fine.
There is more broken, thumb/libc.a contains strcmp for the wrong
architecture. So unless you don't need strcmp, there is no workaround.
--
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:
I'm also affected by this (Cortex M3).
My workaround:
cd /usr/lib/arm-none-eabi/lib/thumb/v7-m
sudo ln -s ../* .
(for cortex m4, you need to go to v7e-m).
The real fix would be to fix the default library paths for arm-none-eabi-gcc,
to also include the thumb directory. I have no
Encountered the same issue. Is there a workaround/patch?
--
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
The same issue here. Needed to uninstall from apt and download from ARM
website.
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gcc-arm-none-eabi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767223
I am having that issue also (using mbed-cli) after upgrading to 18.04.
(Used to work on 17.10).
quote >> (Also, what happened to gdb-arm-none-eabi?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note: I do not think it is an upstream problem, since I downloaded gcc-
arm-none-eabi-6-2017-q2-update from ARM which contains a very similar
version (both 6.3.1 20170620) and it does not exhibit the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
39 matches
Mail list logo
