On Fri, Oct 21, 2022 at 2:32 PM Florian Weimer <fwei...@redhat.com> wrote:
>
> * Jun Aruga:
>
> > When I was trying to use binaries built on the Ubuntu environment, on
> > Fedora 36, I couldn't use it due to the missing the `.gnu.version_d
> > section`.[1] I tried to run Ruby's configure referring to the binary
> > (wasi-sdk). And I got the errors below.
> >
> > ```
> > $ ./configure LDFLAGS="-Xlinker -zstack-size=16777216" \
> >   --host wasm32-unknown-wasi \
> >   --with-destdir=./ruby-wasm32-wasi \
> >   --with-static-linked-ext \
> >   --with-ext=ripper,monitor
> > ...
> > /usr/local/wasi-sdk-16.0/bin/clang: /lib64/libtinfo.so.6: no version
> > information available (required by /usr/local/wasi-sdk-16.0/bin/clang)
> > /usr/local/wasi-sdk-16.0/bin/clang: /lib64/libtinfo.so.6: no version
> > information available (required by /usr/local/wasi-sdk-16.0/bin/clang)
> > /usr/local/wasi-sdk-16.0/bin/clang: /lib64/libtinfo.so.6: no version
> > information available (required by /usr/local/wasi-sdk-16.0/bin/clang)
> > ...
> > ```
>
> See this bug for details:
>
>   ncurses: Please enable symbol versioning
>   <https://bugzilla.redhat.com/show_bug.cgi?id=1875587>
>
> The stub object creator mentioned in comment 2 is still vaporware,
> unfortunately, so there is no easy way to fix this right now.
>
> Thanks,
> Florian
>

Hi,
Thanks for the info. OK. It is a known ncurses RPM package specific
issue. I commented there.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See <https://www.worldtimebuddy.com/czech-republic-prague-to-utc> for
the timezone.
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to