building libiconv

bridged with qdn.public.qnxrtp.porting
Post Reply
Alain Bonnefoy

building libiconv

Post by Alain Bonnefoy » Fri Aug 29, 2003 7:45 am

Hi, I tried to build libiconv-1.9 but I encounter some problems.

It seems that I need automake-1.7 so, I invoked the following commands
(thanks Chris):

#> libtoolize -f -c
#> aclocal-1.7
#> automake-1.7 -a -c
#> autoconf

I don't know how all that work but it seems that some definitions are
missing somewhere.
I get the following messages while executing configure script:

../configure[10349]: AC_MBSTATE_T: not found
....
../configure[10590]: AC_EILSEQ: not found
../configure[10592]: CL_WORDS_LITTLEENDIAN: not found
../configure[10594]: gl_FUNC_ALLOCA: not found
../configure[10595]: gl_CANONICALIZE: not found
../configure[10596]: jm_FUNC_GLIBC_UNLOCKED_IO: not found
../configure[10597]: gt_FUNC_ERROR_AT_LINE: not found
../configure[10598]: gl_PATHMAX: not found
../configure[10599]: gt_FUNC_SETENV: not found
../configure[10600]: gt_STDBOOL_H: not found
../configure[10601]: gl_FUNC_STRERROR: not found
../configure[10602]: gl_XREADLINK: not found

does anyone know what does it mean??

regards,
Alain.

Chris McKillop

Re: building libiconv

Post by Chris McKillop » Fri Aug 29, 2003 5:30 pm

Do they have an m4 directory in the project? If so, you may have to
add an include to aclocal to pull in thier local m4 scripts.

chris


Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
Hi, I tried to build libiconv-1.9 but I encounter some problems.

It seems that I need automake-1.7 so, I invoked the following commands
(thanks Chris):

#> libtoolize -f -c
#> aclocal-1.7
#> automake-1.7 -a -c
#> autoconf

I don't know how all that work but it seems that some definitions are
missing somewhere.
I get the following messages while executing configure script:

./configure[10349]: AC_MBSTATE_T: not found
...
./configure[10590]: AC_EILSEQ: not found
./configure[10592]: CL_WORDS_LITTLEENDIAN: not found
./configure[10594]: gl_FUNC_ALLOCA: not found
./configure[10595]: gl_CANONICALIZE: not found
./configure[10596]: jm_FUNC_GLIBC_UNLOCKED_IO: not found
./configure[10597]: gt_FUNC_ERROR_AT_LINE: not found
./configure[10598]: gl_PATHMAX: not found
./configure[10599]: gt_FUNC_SETENV: not found
./configure[10600]: gt_STDBOOL_H: not found
./configure[10601]: gl_FUNC_STRERROR: not found
./configure[10602]: gl_XREADLINK: not found

does anyone know what does it mean??

regards,
Alain.
--
Chris McKillop <cdm@qnx.com> "The faster I go, the behinder I get."
Software Engineer, QSSL -- Lewis Carroll --
http://qnx.wox.org/

Alain Bonnefoy

Re: building libiconv

Post by Alain Bonnefoy » Tue Sep 02, 2003 9:30 am

There is a m4 directory but I don't understand what you want me to do :-[ !

Alain.

Chris McKillop a écrit:
Do they have an m4 directory in the project? If so, you may have to
add an include to aclocal to pull in thier local m4 scripts.

chris


Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:


Hi, I tried to build libiconv-1.9 but I encounter some problems.

It seems that I need automake-1.7 so, I invoked the following commands
(thanks Chris):

#> libtoolize -f -c
#> aclocal-1.7
#> automake-1.7 -a -c
#> autoconf

I don't know how all that work but it seems that some definitions are
missing somewhere.
I get the following messages while executing configure script:

./configure[10349]: AC_MBSTATE_T: not found
...
./configure[10590]: AC_EILSEQ: not found
./configure[10592]: CL_WORDS_LITTLEENDIAN: not found
./configure[10594]: gl_FUNC_ALLOCA: not found
./configure[10595]: gl_CANONICALIZE: not found
./configure[10596]: jm_FUNC_GLIBC_UNLOCKED_IO: not found
./configure[10597]: gt_FUNC_ERROR_AT_LINE: not found
./configure[10598]: gl_PATHMAX: not found
./configure[10599]: gt_FUNC_SETENV: not found
./configure[10600]: gt_STDBOOL_H: not found
./configure[10601]: gl_FUNC_STRERROR: not found
./configure[10602]: gl_XREADLINK: not found

does anyone know what does it mean??

regards,
Alain.





Chris McKillop

Re: building libiconv

Post by Chris McKillop » Tue Sep 02, 2003 11:31 pm

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
There is a m4 directory but I don't understand what you want me to do :-[ !
aclocal -I m4/

Telling aclocal to use the m4/ dir as an include path search.

chris


--
Chris McKillop <cdm@qnx.com> "The faster I go, the behinder I get."
Software Engineer, QSSL -- Lewis Carroll --
http://qnx.wox.org/

Alain Bonnefoy

Re: building libiconv

Post by Alain Bonnefoy » Wed Sep 03, 2003 8:55 am

prefect!!!
Thanks a lot Chris,
Alain.

Chris McKillop a écrit:
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:


There is a m4 directory but I don't understand what you want me to do :-[ !




aclocal -I m4/

Telling aclocal to use the m4/ dir as an include path search.

chris



Alain Bonnefoy

Re: building libiconv Not so perfect in fact!

Post by Alain Bonnefoy » Wed Sep 03, 2003 12:30 pm

Hi Chris,
When I build the shared lib, the name is libiconv.2.2.0 instead of
libiconv.so.2.2.0
the soname is libiconv.2 instead of libiconv.so.2.2.0

If I look in the configure script I can see:

shrext=".so"
....
...
....

library_names_spec='${libname}${release}${shared_ext}$versuffix
${libname}${release}${shared_ext}$major $libname${shared_ext}'
soname_spec='${libname}${release}${shared_ext}$major'


So, you can see the problem, it defines 'shrext' and use 'shared_ext'

Do you have any idea.

As I don't know anything about that part, I don't know who can help me!

Do I have to ask to GNU ?!?

Thanks,
Alain.

Chris McKillop a écrit:
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:


There is a m4 directory but I don't understand what you want me to do :-[ !




aclocal -I m4/

Telling aclocal to use the m4/ dir as an include path search.

chris



Chris McKillop

Re: building libiconv Not so perfect in fact!

Post by Chris McKillop » Wed Sep 03, 2003 4:10 pm

Take a look at configure.in. Does it do the same thing or is this from
a macro expansion?

chris

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
Hi Chris,
When I build the shared lib, the name is libiconv.2.2.0 instead of
libiconv.so.2.2.0
the soname is libiconv.2 instead of libiconv.so.2.2.0

If I look in the configure script I can see:

shrext=".so"
...
..
...

library_names_spec='${libname}${release}${shared_ext}$versuffix
${libname}${release}${shared_ext}$major $libname${shared_ext}'
soname_spec='${libname}${release}${shared_ext}$major'


So, you can see the problem, it defines 'shrext' and use 'shared_ext'

Do you have any idea.

Alain Bonnefoy

Re: building libiconv Not so perfect in fact!

Post by Alain Bonnefoy » Thu Sep 04, 2003 8:10 am

It seems that the problem comes from libtool.m4, I found the following
lines:
1085 4:shrext=".so"
1119 52:
library_names_spec='${libname}${release}${shared_ext}$versuffix $libname.a'
1123 45: soname_spec='${libname}${release}${shared_ext}$major'

Alain.

Chris McKillop a écrit:
Take a look at configure.in. Does it do the same thing or is this from
a macro expansion?

chris

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:


Hi Chris,
When I build the shared lib, the name is libiconv.2.2.0 instead of
libiconv.so.2.2.0
the soname is libiconv.2 instead of libiconv.so.2.2.0

If I look in the configure script I can see:

shrext=".so"
...
..
...

library_names_spec='${libname}${release}${shared_ext}$versuffix
${libname}${release}${shared_ext}$major $libname${shared_ext}'
soname_spec='${libname}${release}${shared_ext}$major'


So, you can see the problem, it defines 'shrext' and use 'shared_ext'

Do you have any idea.


Alain Bonnefoy

Re: building libiconv Not so perfect in fact!

Post by Alain Bonnefoy » Fri Sep 05, 2003 11:35 am

Ok, libtool.m4 seems to be good but there is a difference between
original ltmain.sh and the one I have now, after libtoolize, aclocal,
etc....

In the original one, there is the following line:
2756 eval shared_ext=\"$shrext\"

In the new one, there is no more 'eval shared_ext''.

Any idea???

Alain.

Alain Bonnefoy a écrit:
It seems that the problem comes from libtool.m4, I found the following
lines:
1085 4:shrext=".so"
1119 52:
library_names_spec='${libname}${release}${shared_ext}$versuffix
$libname.a'
1123 45: soname_spec='${libname}${release}${shared_ext}$major'

Alain.

Chris McKillop a écrit:

Take a look at configure.in. Does it do the same thing or is this from
a macro expansion?

chris

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:


Hi Chris,
When I build the shared lib, the name is libiconv.2.2.0 instead of
libiconv.so.2.2.0
the soname is libiconv.2 instead of libiconv.so.2.2.0

If I look in the configure script I can see:

shrext=".so"
...
..
...

library_names_spec='${libname}${release}${shared_ext}$versuffix
${libname}${release}${shared_ext}$major $libname${shared_ext}'
soname_spec='${libname}${release}${shared_ext}$major'


So, you can see the problem, it defines 'shrext' and use 'shared_ext'

Do you have any idea.



Chris McKillop

Re: building libiconv Not so perfect in fact!

Post by Chris McKillop » Fri Sep 05, 2003 6:03 pm

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
Ok, libtool.m4 seems to be good but there is a difference between
original ltmain.sh and the one I have now, after libtoolize, aclocal,
etc....

In the original one, there is the following line:
2756 eval shared_ext=\"$shrext\"

In the new one, there is no more 'eval shared_ext''.

Any idea???
Looks like they have a version dependancy in thier project. This happens.
Just update one or the other to match.

chris

--
Chris McKillop <cdm@qnx.com> "The faster I go, the behinder I get."
Software Engineer, QSSL -- Lewis Carroll --
http://qnx.wox.org/

Post Reply

Return to “qdn.public.qnxrtp.porting”