Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Massimiliano Marretta <max@marretta.com>
To: buildroot@busybox.net
Subject: [Buildroot] Xterm: undefined reference to __longjmp_chk
Date: Fri, 08 Oct 2010 10:13:59 +0200	[thread overview]
Message-ID: <4CAED2C7.6010607@marretta.com> (raw)
In-Reply-To: <4CAE0F33.5000305@marretta.com>

  I resolved the problem by add to the makefile.in the CPPFLAGS 
-U_FORTIFY_SOURCE.
There is possibility to add this flag by xterm.mk or is necessary to 
create a patch ?


On 10/07/10 20:19, Massimiliano Marretta wrote:
>  Hi,
>
> I'm using the buildroot 2010.08 version with crosstool-ng toolchain. 
> The target is an x86 i686.
> I receive this error wit xterm compilation:
>
> charproc.o: In function `VTReset':
> charproc.c:(.text+0x2623): undefined reference to `__longjmp_chk'
> main.o: In function `hungtty':
> main.c:(.text+0x867): undefined reference to `__longjmp_chk'
> misc.o: In function `end_vt_mode':
> misc.c:(.text+0x3a3): undefined reference to `__longjmp_chk'
> misc.o: In function `end_tek_mode':
> misc.c:(.text+0x3c7): undefined reference to `__longjmp_chk'
> Tekproc.o: In function `Tinput':
> Tekproc.c:(.text+0x1336): undefined reference to `__longjmp_chk'
> collect2: ld returned 1 exit status
> make[1]: *** [xterm] Error 1
> make[1]: Leaving directory 
> `/srv/source/buildroot-2010.08/output/build/xterm-259'
> make: *** 
> [/srv/source/buildroot-2010.08/output/build/xterm-259/.stamp_built] 
> Error 2
>
>


-- 

Massimiliano Marretta
Via Zuccola 11
41015 Nonantola (Mo) - Italy
tel: +39 347 5340305
skype: mmarretta
/mailto:max at marretta.com/
/web:www.marretta.com/ <http://www.marretta.com>

      parent reply	other threads:[~2010-10-08  8:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 18:19 [Buildroot] Xterm: undefined reference to __longjmp_chk Massimiliano Marretta
2010-10-08  8:13 ` Massimiliano Marretta
2010-10-08  8:13 ` Massimiliano Marretta [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=4CAED2C7.6010607@marretta.com \
    --to=max@marretta.com \
    --cc=buildroot@busybox.net \
    /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