configure scripts, libtool.m4, etc...

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

configure scripts, libtool.m4, etc...

Post by Alain Bonnefoy » Wed Aug 27, 2003 9:16 am

Hi,
We still download recent unix source code where configure scripts don't
allow to build shared libraries correctly on qnx.
It seems that libtool.m4 doesn't well know qnx-nto system to produce
necessary building commands.
Could any QNX people contact gnu to complete these build scripts for
future projects and tell us what do we have to change and to do to
rebuild correct configure script on existing projetcs?

thanks in advance
Alain.

Chris McKillop

Re: configure scripts, libtool.m4, etc...

Post by Chris McKillop » Wed Aug 27, 2003 3:16 pm

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
Hi,
We still download recent unix source code where configure scripts don't
allow to build shared libraries correctly on qnx.
It seems that libtool.m4 doesn't well know qnx-nto system to produce
necessary building commands.
Could any QNX people contact gnu to complete these build scripts for
future projects and tell us what do we have to change and to do to
rebuild correct configure script on existing projetcs?
libtoolize -f -c
automake -a -c
aclocal
autoconf

Run those in order on a QNX machine and it will update the project to build
on QNX with shared library support.

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: configure scripts, libtool.m4, etc...

Post by Alain Bonnefoy » Thu Aug 28, 2003 6:23 am

Thanks a lot Chris but it seems that aclocal must be invoked before
automake.

I still deplore that Unix projects don't know QNX platform and if we
only do like you suggest in this message, that won't change.

Alain.

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


Hi,
We still download recent unix source code where configure scripts don't
allow to build shared libraries correctly on qnx.
It seems that libtool.m4 doesn't well know qnx-nto system to produce
necessary building commands.
Could any QNX people contact gnu to complete these build scripts for
future projects and tell us what do we have to change and to do to
rebuild correct configure script on existing projetcs?




libtoolize -f -c
automake -a -c
aclocal
autoconf

Run those in order on a QNX machine and it will update the project to build
on QNX with shared library support.

chris


Chris McKillop

Re: configure scripts, libtool.m4, etc...

Post by Chris McKillop » Thu Aug 28, 2003 5:23 pm

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
Thanks a lot Chris but it seems that aclocal must be invoked before
automake.

I still deplore that Unix projects don't know QNX platform and if we
only do like you suggest in this message, that won't change.
What actually has to happen is many-fold. We need to get our changes
to libtool into the main GNU repo. Then, there needs to be a new release
of libtool. Then, that new release has to be used by developers on the
projects you want to compile. Fact is, auto* projects include the pre-made
files as a short-cut for people since most platforms (Linux) don't change
very often.

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: configure scripts, libtool.m4, etc...

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

I understand that Chris, but the fact is that many if not all Unix
projects know VxWorks, pSos, even Amiga or Atari!
QNX should be as known as them I think.

I t would be very easier for everybody (because that's no so obvious) to
take advantage of the pletora of Unix apps as QNX is a posix system.

Regards,
Alain.

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


Thanks a lot Chris but it seems that aclocal must be invoked before
automake.

I still deplore that Unix projects don't know QNX platform and if we
only do like you suggest in this message, that won't change.




What actually has to happen is many-fold. We need to get our changes
to libtool into the main GNU repo. Then, there needs to be a new release
of libtool. Then, that new release has to be used by developers on the
projects you want to compile. Fact is, auto* projects include the pre-made
files as a short-cut for people since most platforms (Linux) don't change
very often.

chris


Chris McKillop

Re: configure scripts, libtool.m4, etc...

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

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
I understand that Chris, but the fact is that many if not all Unix
projects know VxWorks, pSos, even Amiga or Atari!
QNX should be as known as them I think.

I t would be very easier for everybody (because that's no so obvious) to
take advantage of the pletora of Unix apps as QNX is a posix system.
Yep, just don't expect it to be an instant thing when our changes get sent
back to GNU is all. It will take a couple of years.

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”