From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: ld: skipping incompatible /usr/lib/libpthread.so
Date: Fri, 8 Jan 2021 16:59:42 -0000 (UTC) [thread overview]
Message-ID: <rta31u$3h2$1@ciao.gmane.io> (raw)
In-Reply-To: rta2nd$v8v$1@ciao.gmane.io
On 2021-01-08, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> I've noticed that when linking an applicatoin I now get warnings like this:
>
> /usr/lib/gcc/[...]/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching for -lpthread
> /usr/lib/gcc/[...]/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/libpthread.a when searching for -lpthread
> /usr/lib/gcc/[...]/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
> /usr/lib/gcc/[...]/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/libc.a when searching for -lc
>
> Those files appear to be 32-bit versions.
Never mind. I just noticed that the build script is specifying -L
/usr/lib when it should not. That's what's causing the warnings.
prev parent reply other threads:[~2021-01-08 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 16:54 [gentoo-user] ld: skipping incompatible /usr/lib/libpthread.so Grant Edwards
2021-01-08 16:59 ` Grant Edwards [this message]
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='rta31u$3h2$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.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