[Pkg-electronics-devel] gcc-arm-none-eabi: I need help

John Scott jscott at posteo.net
Sat Aug 12 19:02:57 BST 2023


Okay, I've run into a problem and I need help. By the way, I think it'd be cool if we got an IRC channel for this sort of thing.

If you read the GCC and GNU Toolchain documentation, you will find that building in a subdirectory of the source tree, like Debhelper likes to do and like the package currently does, is forbidden. I guess at the moment it just so happens to work by sheer luck.

However, I think the way the package currently does things is causing my Newlib build to fail. I'm trying to make changes that are not invasive, but I don't know how to fix this without totally reworking the source package. So I ask again: what's the difference between the ARM GCC and upstream GCC? If using upstream GCC were okay, we could just yank the tarball out of gcc-13-source, make the package be a native package with just a Debian directory, and call it a day.

Also, if you read https://gcc.gnu.org/legacy-ml/gcc/2013-04/msg00171.html you will find that Debhelper's tricks tend to cause GCC and GNU Toolchain builds to fail. Again, I guess it's working right now by sheer luck. In gcc-sh-elf and similar packages, we have to work around this by calling all of the build steps by hand, which isn't as bad as it sounds, since dpkg's build flags and the like are inappropriate for embedded and cross compile work.

Please let me know how I can resolve this. If you want, I can push what I have to Git and you can investigate the build failures, if they might have an alternative resolution.

If a combined tree build isn't the right way to go, maybe someone who actually uses the ARM toolchain could introduce a newlib-arm-none-eabi source package that builds the libnewlib-arm-none-eabi-dev binary package?

Thanks,
John
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-electronics-devel/attachments/20230812/185014b4/attachment.sig>


More information about the Pkg-electronics-devel mailing list