[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [autoconf] 32/64-bit systems
From: |
Ben Taylor |
Subject: |
Re: [autoconf] 32/64-bit systems |
Date: |
Mon, 14 Jul 2008 12:24:31 -0400 |
On Mon, Jul 14, 2008 at 11:46 AM, <address@hidden> wrote:
> Hi,
>
> On Mon, 14 Jul 2008 08:32:44 -0400
> "Ben Taylor" <address@hidden> wrote:
>>so i have something like prefix/lib and prefix/lib/sparcv9 for sparc
>>and prefix/lib and prefix/lib/amd64 for x64.
>
> This naming convention is standard among Solaris developers?
That's the standard Sun uses for their 64-bit libraries on Sparc
and X86-64. Normal 32-bit follows ${prefix}/lib
>>To be quite honest, I cannot fathom why configure itself
>>generates a full path to the library, instead of "-liconv"
>>which would work because I'm passing the right
>>include and ldflags to configure. Seems like a bug to
>>me.
>
> Hmm, autoconf's AC_CHECK_LIB([NAME], [FUNC], [...]) provides
> the feature what you want, I guess. It would not search the
> pathname of libNAME, but it would execute
> ${CC} ${CFLAGS} ${LDFLAGS} conftest.c -lNAME
> conftest.c refers FUNC. Do you think you found the bug of
> autoconf?
I think so. Mainly because it's returning the full path of the
32-bit library on a 64-bit system. If it was returning -liconv
(in this instance) I'm pretty sure the test would pass.
Ben