From: beuc@beuc.net
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: libunistring test
Date: Sun, 22 Jun 2014 17:42:04 +0200 [thread overview]
Message-ID: <20140622154204.GA5065@mail.beuc.net> (raw)
In-Reply-To: <874mzeeylh.fsf@gnu.org>
On Sat, Jun 21, 2014 at 11:34:18PM +0200, Ludovic Courtès wrote:
> beuc@beuc.net skribis:
> > On Fri, Jun 20, 2014 at 12:16:41PM +0200, Ludovic Courtès wrote:
> >> beuc@beuc.net skribis:
> >> > First important note: I had to move "AC_CHECK_LIB(m, cos)" (which btw
> >> > could be rewritten at LT_LIB_M()) before gl_INIT in configure.ac,
> >> > otherwise libunistring would fail to be detected.
> >>
> >> Could you send the config.log of the failing thing?
> >
> > Selected bits:
> >
> > configure:14688: checking for libunistring
> > configure:14710: arm-linux-androideabi-gcc -o conftest -g -O2 -I/usr/src/ndk-standalone-12/sysroot/usr/include conftest.c /usr/src/ndk-standalone-12/sysroot/usr/lib/libunistring.so -Wl,-rpath -Wl,/usr/src/ndk-standalone-12/sysroot/usr/lib >&5
> > /usr/src/ndk-standalone-12/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-linux-androideabi/bin/ld: /usr/src/ndk-standalone-12/sysroot/usr/lib/libunistring.so: error: undefined reference to 'frexp'
> > collect2: ld returned 1 exit status
>
> It looks like a libunistring issue no? Namely, libunistring assumed
> frexp to be available in libc, and it isn’t.
Incidentally, do you know why the test is referencing the .so directly?
That seems to be the cause of the problem
I'm trying to isolate the issue with a basic gnulib project and I have
a much simpler test:
configure:7110: checking for libunistring
configure:7132: arm-linux-androideabi-gcc -o conftest -g -O2 conftest.c -lunistring >&5
configure:7132: $? = 0
configure:7142: result: yes
--
Sylvain
next prev parent reply other threads:[~2014-06-22 15:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 21:54 Compiling for Android beuc
2014-06-20 10:16 ` Ludovic Courtès
2014-06-21 20:06 ` beuc
2014-06-21 21:34 ` Ludovic Courtès
2014-06-22 14:08 ` beuc
2014-06-23 7:59 ` Ludovic Courtès
2014-06-23 18:59 ` beuc
2014-06-24 7:56 ` Ludovic Courtès
2014-06-25 21:23 ` beuc
2014-06-25 22:04 ` Ludovic Courtès
2014-06-24 14:04 ` Mark H Weaver
2014-07-04 14:00 ` Ludovic Courtès
2014-07-04 14:01 ` Ludovic Courtès
2014-06-22 15:42 ` beuc [this message]
2014-06-23 8:04 ` libunistring test Ludovic Courtès
2014-06-23 16:48 ` beuc
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140622154204.GA5065@mail.beuc.net \
--to=beuc@beuc.net \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).