This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Relocation Truncated to Fit: R_X86_64_PC32
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: R0b0t1 <r030t1 at gmail dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, gcc-help <gcc-help at gcc dot gnu dot org>
- Date: Tue, 21 Aug 2018 20:09:27 +0100
- Subject: Re: Relocation Truncated to Fit: R_X86_64_PC32
- References: <CAAD4mYiFabBRH78HYMO+py7RHWnS1q4rTyHZr7eSX3wbXGn0_g@mail.gmail.com> <CAAD4mYhpYdL=QMbiH9Crb18vVxbrJT1Cne3gytWevoEFJFPVtw@mail.gmail.com> <CAH6eHdT4Znc3TiiN=d6eiabweUFu0ENWkMfgrK_uSC6YamyBYA@mail.gmail.com> <CAAD4mYhZn=mCMMxT+zENtDqMBRSDAaVE=Y3VejsA7zqe=-aSiw@mail.gmail.com>
On Tue, 21 Aug 2018 at 19:43, R0b0t1 wrote:
> Hello everyone, I'm adding a message to the gcc-devel list because I'd
> appreciate some help figuring out if this is a bug. The issue was that
> I was missing a linking directive to a library (-lwinpr). The message
> does not seem to be reasonable in this context. I've also encountered
> it when supplying potentially nonsensical arguments (e.g. link in this
> dynamic library statically).
So wouldn't that be a linker error, not one that comes from GCC, and
so still off-topic?