From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Missing obstack symbols for arduino-cli binaries on musl
Date: Sat, 08 Aug 2020 16:23:36 +0200 [thread overview]
Message-ID: <20200808142336.V7D6YZRm0AsGuSS6_Agkwk_m-AxlDVeHTzmTFSAxr2w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22616@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2353 bytes --]
Closed issue by kqo on void-packages repository
https://github.com/void-linux/void-packages/issues/22616
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
* Void 5.6.2 x86_64-musl GenuineIntel uptodate rrFFFF
* package:
* arduino-cli
* gcompat
* musl-obstack
### Expected behavior
Binaries pulled in by `arduino-cli` which are linked against `glibc` should hopefully work on musl after #22237 (which fixed other missing symbols, thank you for that!).
### Actual behavior
The `arm-none-eabi-g++` binary pulled in by the `arduino:sam` core is still missing symbols from obstack, namely:
```
Error relocating [...]/arduino/packages/arduino/tools/arm-none-eabi-gcc/4.8.3-2014q1/bin/arm-none-eabi-g++: _obstack_newchunk: symbol not found
Error relocating [...]/arduino/packages/arduino/tools/arm-none-eabi-gcc/4.8.3-2014q1/bin/arm-none-eabi-g++: obstack_free: symbol not found
Error relocating [...]/arduino/packages/arduino/tools/arm-none-eabi-gcc/4.8.3-2014q1/bin/arm-none-eabi-g++: _obstack_begin: symbol not found
Error relocating [...]/arduino/packages/arduino/tools/arm-none-eabi-gcc/4.8.3-2014q1/bin/arm-none-eabi-g++: _obstack_memory_used: symbol not found
```
`gcompat` seems to support building with `musl-obstack`, so I [tried enabling support](https://github.com/void-linux/void-packages/compare/master...kqo:gcompat-arduino) in the template. I can see that `musl-obstack` gets linked in with `-lobstack`, but the binary still can't find the symbols, nor can I with `nm`.
I'm really out of my depth with this, so I'm not sure if this is a `gcompat` problem, something I'm doing wrong with `xbps`, or if I'm just misunderstanding how things are supposed to work.
### Steps to reproduce the behavior
This will bump into the binary needing obstack symbols:
```
$ arduino-cli core update-index
$ arduino-cli core install arduino:sam
$ arduino-cli sketch new test_sketch
$ arduino-cli compile test_sketch --fqbn arduino:sam:arduino_due_x_dbg
```
It's probably quicker to run:
```
$ LD_PRELOAD=/usr/lib/libgcompat.so.0 ldd ~/.local/share/arduino/packages/arduino/tools/arm-none-eabi-gcc/4.8.3-2014q1/bin/arm-none-eabi-g++
```
next parent reply other threads:[~2020-08-08 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22616@inbox.vuxu.org>
2020-08-08 14:23 ` Johnnynator [this message]
2022-03-17 18:38 ` 4ntoine
2022-03-17 18:39 ` 4ntoine
2022-03-17 18:40 ` 4ntoine
2022-03-17 18:43 ` 4ntoine
2022-03-17 18:48 ` 4ntoine
2022-03-17 18:49 ` 4ntoine
2022-03-17 22:58 ` Johnnynator
2022-03-17 23:19 ` Johnnynator
2022-03-18 6:20 ` 4ntoine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200808142336.V7D6YZRm0AsGuSS6_Agkwk_m-AxlDVeHTzmTFSAxr2w@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).