Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gauche: remove unnecessary files for target, fix a typo
Date: Wed, 11 Nov 2015 14:24:17 +0100	[thread overview]
Message-ID: <20151111142417.76bf1bb7@free-electrons.com> (raw)
In-Reply-To: <201511111311.tABDB5aR013551@ms-omx03.plus.so-net.ne.jp>

Hiroshi,

On Wed, 11 Nov 2015 22:11:04 +0900, Hiroshi Kawashima wrote:

> 2015-11-11 12:36:54	xtensa		gc not ported

Right, exclude this architecture.

> 2015-11-10 23:30:21	powerpc		./libgauche-0.9.so: undefined reference to `getcontext'

This probably only happens with certain C libraries only. Check if this
build failure occurs with uClibc or glibc, probably only with uClibc.

> 2015-11-10 23:11:45	arc		gc not ported

Right, exclude this architecture as well.

> 2015-11-10 22:20:21	powerpc		./libgauche-0.9.so: undefined reference to `getcontext'
> 2015-11-10 17:30:19	arc		gc not ported
> 2015-11-10 14:16:58	sh4		./libgauche-0.9.so: undefined reference to `getcontext'
> 2015-11-10 08:46:51	powerpc		./libgauche-0.9.so: undefined reference to `getcontext'
> 2015-11-10 04:28:00	arm		./libgauche-0.9.so: undefined reference to `AO_pt_lock'

This is what happens when libatomic_ops is built before gauche. In this
case, gauche tries to use the external libatomic_ops instead of its
internal one.

As I already suggested to fix this, you have two options:

 (1) Understand why using the external libatomic_ops doesn't work and
     fix it.

 (2) Pass a configure option to gauche to force it to use its internal
     version of libatomic_ops.

I'd prefer (1), but we can live with (2) if (1) is too complicated.

> 2015-11-10 00:00:05	arm		./include/private/../gc_pthread_redirects.h:37:22: fatal error: dlfcn.h: No such file or directory

Two options here:

 (1) boehm gc in gauche supports the GC_NO_DLOPEN like the official
     boehm gc. In this case, pass -DGC_NO_DLOPEN when
     BR2_STATIC_LIBS=y. See bdwgc.mk for an example.

 (2) Make gauche depend on !BR2_STATIC_LIBS.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-11-11 13:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10  9:22 [Buildroot] [PATCH] package/gauche: remove unnecessary files for target, fix a typo Hiroshi Kawashima
2015-11-10  9:48 ` Thomas Petazzoni
2015-11-10 10:21   ` Hiroshi Kawashima
2015-11-10 10:42     ` Thomas Petazzoni
2015-11-10 11:59       ` Hiroshi Kawashima
2015-11-11 13:11       ` Hiroshi Kawashima
2015-11-11 13:24         ` Thomas Petazzoni [this message]
2015-11-13 10:05           ` Hiroshi Kawashima
2015-11-14  3:05           ` Hiroshi Kawashima
2015-11-17 15:32           ` Hiroshi Kawashima
2015-11-10 20:54 ` Arnout Vandecappelle
2015-11-11 13:59   ` Thomas Petazzoni
2015-11-11 14:14     ` Hiroshi Kawashima
2015-11-11 14:29       ` Arnout Vandecappelle
2015-11-11 14:35         ` Hiroshi Kawashima
2015-11-13 10:52 ` Hiroshi Kawashima
2015-11-27 12:47 ` Hiroshi Kawashima
2015-11-29 20:35 ` Yann E. MORIN
2015-11-30 12:32   ` Hiroshi Kawashima
2015-12-24 11:20 ` Thomas Petazzoni

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=20151111142417.76bf1bb7@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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