LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Emmanuel STAPF" <manu@stapf.org>
To: "'Kaoru Fukui'" <k_fukui@highway.ne.jp>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: RE: Error when linking
Date: Sat, 20 Oct 2001 09:27:41 -0700	[thread overview]
Message-ID: <001901c15984$23b05b80$f5732c0c@venice2> (raw)
In-Reply-To: <20011020162513.Postino-002980@smtp01.highway.ne.jp>


I should add that they occur only when I have my 1000 files. A similar
project using those C function but smaller compiles without any problem.

Any idea why and what are the possible solutions?
Manu

> -----Original Message-----
> From: Kaoru Fukui [mailto:k_fukui@highway.ne.jp]
> Sent: Saturday, October 20, 2001 00:25
> To: manu@stapf.org
> Cc: linuxppc-dev@lists.linuxppc.org
> Subject: Re: Error when linking
>
>
> From: "Emmanuel STAPF" <manu@stapf.org>
> To: <linuxppc-dev@lists.linuxppc.org>
> Subject: Error when linking
> Date: Sat, 20 Oct 2001 00:03:44 -0700
>
> >
> > Hi,
> >
> > When compiling a big system composed of about 1000 c files,
> I get a lot
> > of errors such as reproduced below. Is there a solution to
> this problem?
> >
> > Thanks,
> > Manu
> >
> > /usr/lib/crt1.o: In function `_start':
> > /usr/lib/crt1.o(.text+0x20): relocation truncated to fit:
> R_PPC_REL24
> > __libc_start_main@@GLIBC_2.0
> >
> /usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/3.0.1/crtbegin.o: In
> > function `__do_global_dtors_aux':
> >
> /usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/3.0.1/crtbegi
> n.o(.text+
> > 0x94): relocation truncated to fit: R_PPC_PLTREL24
> > __deregister_frame_info@@GLIBC_2.0
> >
> /usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/3.0.1/crtbegin.o: In
> > function `frame_dummy':
> >
> /usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/3.0.1/crtbegi
> n.o(.text+
> > 0x12c): relocation truncated to fit: R_PPC_PLTREL24
> > __register_frame_info@@GLIBC_2.0
> > C1/Cobj1.o: In function `Facss3c':
> > C1/Cobj1.o(.text+0x1480c): relocation truncated to fit: R_PPC_REL24
> > __sigsetjmp@@GLIBC_2.0
>
> Glibc has those rabel.
> You can check with nm command
>
> Kaoru
>
>
>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-10-20 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-20  7:03 Error when linking Emmanuel STAPF
2001-10-20  7:25 ` Kaoru Fukui
2001-10-20 16:27   ` Emmanuel STAPF [this message]
2001-10-20 18:47     ` Brad Boyer
2001-10-20 21:28       ` Emmanuel STAPF
2001-10-21  4:26         ` Brad Boyer
2001-10-25 15:55           ` Emmanuel STAPF
2001-11-06  8:55             ` Strange warning during C compilation Emmanuel STAPF
2001-11-06  9:55               ` Franz Sirl

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='001901c15984$23b05b80$f5732c0c@venice2' \
    --to=manu@stapf.org \
    --cc=k_fukui@highway.ne.jp \
    --cc=linuxppc-dev@lists.linuxppc.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