From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [BUG] Broken .so generation since dbbd33f50d
Date: Thu, 29 Oct 2009 11:26:27 +0100 [thread overview]
Message-ID: <4AE96DD3.2020608@domain.hid> (raw)
In-Reply-To: <4AE96CBF.3030401@domain.hid>
Jan Kiszka wrote:
> Hi Philippe,
>
> your commit dbbd33f50d (nios2: introduce architecture support) broke any
> .so generation, at least for x86. Not sure why, but it is related to
> moving AC_PROG_LIBTOOL around in configure.in. You had to push it after
> nios2's AC_DISABLE_SHARED, right?
>
diff --git a/configure.in b/configure.in
index 71bad26..5e88d57 100644
--- a/configure.in
+++ b/configure.in
@@ -66,6 +66,8 @@ else
build_for=$host_alias
fi
+AC_ENABLE_SHARED
+
use__thread=yes
case "$build_for" in
i*86*-*)
solves it. I just need to find out if AC_DISABLE_SHARED after enable is
allowed (for the nios2 case).
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2009-10-29 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 10:21 [Xenomai-core] [BUG] Broken .so generation since dbbd33f50d Jan Kiszka
2009-10-29 10:26 ` Jan Kiszka [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=4AE96DD3.2020608@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=rpm@xenomai.org \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.