You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Manuel Teira Paz <mt...@tid.es> on 2009/02/24 12:37:02 UTC
Solaris Port. Project dependencies
Hello everybody. Finally, I've got some spare time and would be nice to
spend it helping the project a while.
I've seen lots of changes happened, and was trying to put everything in
place again, porting uncommited changes to the trunk, and so on, to have
the solaris port working again.
The first issue I ran into is the way SSL support is intended to be
detected in configure.ac. I'm not sure about the roots of the problem,
but after getting:
checking for infiniband/verbs.h... no
checking rdma/rdma_cma.h usability... no
checking rdma/rdma_cma.h presence... no
checking for rdma/rdma_cma.h... no
./configure: line 25092: syntax error near unexpected token `SSL,'
./configure: line 25092: ` PKG_CHECK_MODULES(SSL,
nspr,,AC_MSG_ERROR([nspr not found]))'
I found that SSL is the only library to be detected using pkgconfig (I
guess I'm missing the macros and hence they're not expanded). While
pkgconfig is shipped (I think) with most of linux flavours, and provides
a helpful way to check for dependencies, that is not the case for other
unix environments. Don't know what happens with windows, I suppose it
doesn't even use this kind of configuration.
Question here is, should we use an homogeneus way to check for
dependencies, like the AC_CHECK_LIB/AC_CHECK_HEADERS , or perhaps allow
the use of pkg-config stuff, but I think that at least, we should
provide an updated list of dependencies for the project to be build.
Best regards.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Manuel Teira Paz <mt...@tid.es>.
Gordon Sim escribió:
> Manuel Teira Paz wrote:
>
>> Following with this issue, I've made some changes to the SSL section of
>> the configure.ac file. Do you think this could be a valid approach (I
>> can only check now the negative case (no nspr/nss in my solaris system),
>> but I think it should work. Note that I'm running AC_SUBST on SSL_CFLAGS
>> and SSL_LDFLAGS that could be used later wherever the ssl libraries are
>> needed. If you agree with this approach, I will commit the change soon:
>>
>
>
> Looks good to me and works when nss/nspr exist.
>
Thanks for the checking, Gordon. I'm going to commit this change. It's
not I'm against pkgconfig, and I think that it would be a good solution
if at least packagers used it in other environments than linux: It's
supported by freedesktop.org and known to support also win32 and MSVC
flags syntax. But I think it doesn't make too much sense to have only
one library detected using pkgconfig.
Best regards.
--
Manuel.
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Gordon Sim <gs...@redhat.com>.
Manuel Teira Paz wrote:
> Following with this issue, I've made some changes to the SSL section of
> the configure.ac file. Do you think this could be a valid approach (I
> can only check now the negative case (no nspr/nss in my solaris system),
> but I think it should work. Note that I'm running AC_SUBST on SSL_CFLAGS
> and SSL_LDFLAGS that could be used later wherever the ssl libraries are
> needed. If you agree with this approach, I will commit the change soon:
Looks good to me and works when nss/nspr exist.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Manuel Teira Paz <mt...@tid.es>.
Gordon Sim escribió:
> Manuel Teira Paz wrote:
>
>> At least on Ubuntu, the dev packages for nss3 and nspr4 provide a
>> nss-config and nspr-config executables, returning:
>>
>>
>> mteira@colossus:~$ nspr-config --cflags
>> -I/usr/include/nspr
>> mteira@colossus:~$ nss-config --cflags
>> -I/usr/include/nss
>>
>> Does your system packages provide something similar returning the right
>> path?
>>
>
> Yes, it does.
>
> > I think that could be used to configure properly CFLAGS and/or
>
>> LIBS before running the AC_CHECK_LIB macro?
>>
>
> I think you're right.
>
Following with this issue, I've made some changes to the SSL section of
the configure.ac file. Do you think this could be a valid approach (I
can only check now the negative case (no nspr/nss in my solaris system),
but I think it should work. Note that I'm running AC_SUBST on SSL_CFLAGS
and SSL_LDFLAGS that could be used later wherever the ssl libraries are
needed. If you agree with this approach, I will commit the change soon:
Index: configure.ac
===================================================================
--- configure.ac (revision 752019)
+++ configure.ac (working copy)
@@ -313,14 +313,19 @@
AM_CONDITIONAL([RDMA], [test x$with_RDMA = xyes])
# Setup --with-ssl/--without-ssl as arguments to configure
-tmp_LIBS=$LIBS
+SSL_CFLAGS=""
+SSL_LDFLAGS=""
AC_ARG_WITH([ssl],
[AS_HELP_STRING([--with-ssl], [Build with support for SSL])],
[case ${withval} in
yes)
with_SSL=yes
- PKG_CHECK_MODULES([SSL], [nspr],,[AC_MSG_ERROR([nspr not found])])
- PKG_CHECK_MODULES([SSL], [nss],,[AC_MSG_ERROR([nss not found])])
+ AC_PATH_PROG([NSPR_CONFIG], [nspr-config])
+ AS_IF([test x$NSPR_CONFIG = x], [AC_MSG_ERROR([libnspr not
found])], [])
+ AC_PATH_PROG([NSS_CONFIG], [nss-config])
+ AS_IF([test x$NSS_CONFIG = x], [AC_MSG_ERROR([libnss not found])], [])
+ SSL_CFLAGS="`$NSPR_CONFIG --cflags` `$NSS_CONFIG --cflags`"
+ SSL_LDFLAGS="`$NSPR_CONFIG --libs` `$NSS_CONFIG --libs`"
;;
no)
with_SSL=no
@@ -331,13 +336,18 @@
esac],
[
with_SSL=yes
- PKG_CHECK_MODULES([SSL], [nspr],,[with_SSL=no])
- PKG_CHECK_MODULES([SSL], [nss],,[with_SSL=no])
+ AC_PATH_PROG([NSPR_CONFIG], [nspr-config])
+ AS_IF([test x$NSPR_CONFIG = x], [with_SSL=no],
+ [AC_PATH_PROG([NSS_CONFIG], [nss-config])
+ AS_IF([test x$NSS_CONFIG = x], [with_SSL=no],
+ [SSL_CFLAGS="`$NSPR_CONFIG --cflags` `$NSS_CONFIG --cflags`"
+ SSL_LDFLAGS="`$NSPR_CONFIG --libs` `$NSS_CONFIG --libs`"])])
]
)
# Remove from LIBS, we will link it explicitly in make files.
-LIBS=$tmp_LIBS
AM_CONDITIONAL([SSL], [test x$with_SSL = xyes])
+AC_SUBST([SSL_CFLAGS])
+AC_SUBST([SSL_LDFLAGS])
poller=no
Regards.
--
Manuel.
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Gordon Sim <gs...@redhat.com>.
Manuel Teira Paz wrote:
> At least on Ubuntu, the dev packages for nss3 and nspr4 provide a
> nss-config and nspr-config executables, returning:
>
>
> mteira@colossus:~$ nspr-config --cflags
> -I/usr/include/nspr
> mteira@colossus:~$ nss-config --cflags
> -I/usr/include/nss
>
> Does your system packages provide something similar returning the right
> path?
Yes, it does.
> I think that could be used to configure properly CFLAGS and/or
> LIBS before running the AC_CHECK_LIB macro?
I think you're right.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Ján Sáreník <js...@redhat.com>.
Manuel Teira Paz <mt...@tid.es> wrote:
> At least on Ubuntu, the dev packages for nss3 and nspr4 provide a
> nss-config and nspr-config executables, returning:
>
>
> mteira@colossus:~$ nspr-config --cflags
> -I/usr/include/nspr
> mteira@colossus:~$ nss-config --cflags
> -I/usr/include/nss
>
> Does your system packages provide something similar returning the right
> path? I think that could be used to configure properly CFLAGS and/or
> LIBS before running the AC_CHECK_LIB macro?
Arch Linux does contain the same {nspr,nss}-config which
give the same results when called with '--cflags'.
BTW, nspr-config is contained in upstream source package,
but for nss I am not able to find it even in current CVS
checkout. Package maintainers add nss-config manually, see:
http://repos.archlinux.org/viewvc.cgi/nss/repos/extra-i686/nss-config.in
Best regards, Jasan
--
Red Hat Czech, MRG Quality Assurance Associate
""" Looking to carve out IT costs?
www.europe.redhat.com/promo/carveoutcosts/ """
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Manuel Teira Paz <mt...@tid.es>.
Gordon Sim escribió:
> Manuel Teira Paz wrote:
>
>> Hello everybody. Finally, I've got some spare time and would be nice to
>> spend it helping the project a while.
>>
>> I've seen lots of changes happened, and was trying to put everything in
>> place again, porting uncommited changes to the trunk, and so on, to have
>> the solaris port working again.
>>
>> The first issue I ran into is the way SSL support is intended to be
>> detected in configure.ac. I'm not sure about the roots of the problem,
>> but after getting:
>>
>> checking for infiniband/verbs.h... no
>> checking rdma/rdma_cma.h usability... no
>> checking rdma/rdma_cma.h presence... no
>> checking for rdma/rdma_cma.h... no
>> ./configure: line 25092: syntax error near unexpected token `SSL,'
>> ./configure: line 25092: ` PKG_CHECK_MODULES(SSL,
>> nspr,,AC_MSG_ERROR([nspr not found]))'
>>
>> I found that SSL is the only library to be detected using pkgconfig (I
>> guess I'm missing the macros and hence they're not expanded). While
>> pkgconfig is shipped (I think) with most of linux flavours, and provides
>> a helpful way to check for dependencies, that is not the case for other
>> unix environments. Don't know what happens with windows, I suppose it
>> doesn't even use this kind of configuration.
>>
>> Question here is, should we use an homogeneus way to check for
>> dependencies, like the AC_CHECK_LIB/AC_CHECK_HEADERS , or perhaps allow
>> the use of pkg-config stuff, but I think that at least, we should
>> provide an updated list of dependencies for the project to be build.
>>
>
> Certainly the intention is that if you don't have nss/nspr then the
> build proceeds but the SSL modules are not built.
>
> The reason I ended up using PKG_CHECK_MODULES was due to the fact that
> the nss header files refer to the nspr4 headers without using the full
> path under which they were installed (at least on my system). [I dug out
> the original patch I created that did not use pkg-config, see blow if
> interested]
>
> I'm no expert on autotools, but am happy to go with any suggestions that
> work as widely (and cleanly) as possible.
>
Neither I am, unfortunately. :-(
At least on Ubuntu, the dev packages for nss3 and nspr4 provide a
nss-config and nspr-config executables, returning:
mteira@colossus:~$ nspr-config --cflags
-I/usr/include/nspr
mteira@colossus:~$ nss-config --cflags
-I/usr/include/nss
Does your system packages provide something similar returning the right
path? I think that could be used to configure properly CFLAGS and/or
LIBS before running the AC_CHECK_LIB macro?
Regards.
>
>
> Index: configure.ac
> ===================================================================
> --- configure.ac (revision 703347)
> +++ configure.ac (working copy)
> @@ -292,6 +292,50 @@
> LIBS=$tmp_LIBS
> AM_CONDITIONAL([RDMA], [test x$with_RDMA = xyes])
>
> +# Setup --with-ssl/--without-ssl as arguments to configure
> +tmp_LIBS=$LIBS
> +AC_ARG_WITH([ssl],
> + [AS_HELP_STRING([--with-ssl], [Build with support for SSL])],
> + [case ${withval} in
> + yes)
> + with_SSL=yes
> + AC_CHECK_LIB([nspr4],[PR_Read],,[AC_MSG_ERROR([libnspr4 not found])])
> + AC_CHECK_LIB([nss3],[NSS_Init],,[AC_MSG_ERROR([libnss3 not found])])
> + AC_CHECK_LIB([ssl3],[SSL_ImportFD],,[AC_MSG_ERROR([libssl3 not
> found])])
> + AC_CHECK_HEADERS([nspr4/nspr.h],,[AC_MSG_ERROR([nspr header files
> not found])])
> + #TODO: is there a better way to do this? have to include nspr4 in
> + #order for configure to pick up the installed nss headers correctly as
> + #they refer to the nspr headers without the nspr4 prefix:
> + tmp_CPPFLAGS=$CPPFLAGS
> + CPPFLAGS=-I/usr/include/nspr4
> + AC_CHECK_HEADERS([nss3/nss.h nss3/ssl.h],,[AC_MSG_ERROR([nss
> header files not found])])
> + CPPFLAGS=$tmp_CPPFLAGS
> + ;;
> + no)
> + with_SSL=no
> + ;;
> + *)
> + AC_MSG_ERROR([Bad value for --with-ssl: ${withval}])
> + ;;
> + esac],
> + [
> + with_SSL=yes
> + AC_CHECK_LIB([nspr4],[PR_Read],,[with_SSL=no])
> + AC_CHECK_LIB([nss3],[NSS_Init],,[with_SSL=no])
> + AC_CHECK_LIB([ssl3],[SSL_ImportFD],,[with_SSL=no])
> + AC_CHECK_HEADERS([nspr4/nspr.h],,[with_SSL=no])
> + #TODO: is there a better way to do this?:
> + tmp_CPPFLAGS=$CPPFLAGS
> + CPPFLAGS=-I/usr/include/nspr4
> + AC_CHECK_HEADERS([nss3/nss.h nss3/ssl.h],,[with_SSL=no])
> + CPPFLAGS=$tmp_CPPFLAGS
> + ]
> +)
> +# Remove from LIBS, we will link it explicitly in make files.
> +LIBS=$tmp_LIBS
> +AM_CONDITIONAL([SSL], [test x$with_SSL = xyes])
> +
> +
> poller=no
> AC_ARG_WITH([poller],
> [AS_HELP_STRING([--with-poller], [The low level poller
> implementation: poll/solaris-ecf/epoll])],
>
>
>> Best regards.
>>
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Gordon Sim <gs...@redhat.com>.
Manuel Teira Paz wrote:
> Hello everybody. Finally, I've got some spare time and would be nice to
> spend it helping the project a while.
>
> I've seen lots of changes happened, and was trying to put everything in
> place again, porting uncommited changes to the trunk, and so on, to have
> the solaris port working again.
>
> The first issue I ran into is the way SSL support is intended to be
> detected in configure.ac. I'm not sure about the roots of the problem,
> but after getting:
>
> checking for infiniband/verbs.h... no
> checking rdma/rdma_cma.h usability... no
> checking rdma/rdma_cma.h presence... no
> checking for rdma/rdma_cma.h... no
> ./configure: line 25092: syntax error near unexpected token `SSL,'
> ./configure: line 25092: ` PKG_CHECK_MODULES(SSL,
> nspr,,AC_MSG_ERROR([nspr not found]))'
>
> I found that SSL is the only library to be detected using pkgconfig (I
> guess I'm missing the macros and hence they're not expanded). While
> pkgconfig is shipped (I think) with most of linux flavours, and provides
> a helpful way to check for dependencies, that is not the case for other
> unix environments. Don't know what happens with windows, I suppose it
> doesn't even use this kind of configuration.
>
> Question here is, should we use an homogeneus way to check for
> dependencies, like the AC_CHECK_LIB/AC_CHECK_HEADERS , or perhaps allow
> the use of pkg-config stuff, but I think that at least, we should
> provide an updated list of dependencies for the project to be build.
Certainly the intention is that if you don't have nss/nspr then the
build proceeds but the SSL modules are not built.
The reason I ended up using PKG_CHECK_MODULES was due to the fact that
the nss header files refer to the nspr4 headers without using the full
path under which they were installed (at least on my system). [I dug out
the original patch I created that did not use pkg-config, see blow if
interested]
I'm no expert on autotools, but am happy to go with any suggestions that
work as widely (and cleanly) as possible.
Index: configure.ac
===================================================================
--- configure.ac (revision 703347)
+++ configure.ac (working copy)
@@ -292,6 +292,50 @@
LIBS=$tmp_LIBS
AM_CONDITIONAL([RDMA], [test x$with_RDMA = xyes])
+# Setup --with-ssl/--without-ssl as arguments to configure
+tmp_LIBS=$LIBS
+AC_ARG_WITH([ssl],
+ [AS_HELP_STRING([--with-ssl], [Build with support for SSL])],
+ [case ${withval} in
+ yes)
+ with_SSL=yes
+ AC_CHECK_LIB([nspr4],[PR_Read],,[AC_MSG_ERROR([libnspr4 not found])])
+ AC_CHECK_LIB([nss3],[NSS_Init],,[AC_MSG_ERROR([libnss3 not found])])
+ AC_CHECK_LIB([ssl3],[SSL_ImportFD],,[AC_MSG_ERROR([libssl3 not
found])])
+ AC_CHECK_HEADERS([nspr4/nspr.h],,[AC_MSG_ERROR([nspr header files
not found])])
+ #TODO: is there a better way to do this? have to include nspr4 in
+ #order for configure to pick up the installed nss headers correctly as
+ #they refer to the nspr headers without the nspr4 prefix:
+ tmp_CPPFLAGS=$CPPFLAGS
+ CPPFLAGS=-I/usr/include/nspr4
+ AC_CHECK_HEADERS([nss3/nss.h nss3/ssl.h],,[AC_MSG_ERROR([nss
header files not found])])
+ CPPFLAGS=$tmp_CPPFLAGS
+ ;;
+ no)
+ with_SSL=no
+ ;;
+ *)
+ AC_MSG_ERROR([Bad value for --with-ssl: ${withval}])
+ ;;
+ esac],
+ [
+ with_SSL=yes
+ AC_CHECK_LIB([nspr4],[PR_Read],,[with_SSL=no])
+ AC_CHECK_LIB([nss3],[NSS_Init],,[with_SSL=no])
+ AC_CHECK_LIB([ssl3],[SSL_ImportFD],,[with_SSL=no])
+ AC_CHECK_HEADERS([nspr4/nspr.h],,[with_SSL=no])
+ #TODO: is there a better way to do this?:
+ tmp_CPPFLAGS=$CPPFLAGS
+ CPPFLAGS=-I/usr/include/nspr4
+ AC_CHECK_HEADERS([nss3/nss.h nss3/ssl.h],,[with_SSL=no])
+ CPPFLAGS=$tmp_CPPFLAGS
+ ]
+)
+# Remove from LIBS, we will link it explicitly in make files.
+LIBS=$tmp_LIBS
+AM_CONDITIONAL([SSL], [test x$with_SSL = xyes])
+
+
poller=no
AC_ARG_WITH([poller],
[AS_HELP_STRING([--with-poller], [The low level poller
implementation: poll/solaris-ecf/epoll])],
>
> Best regards.
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Manuel Teira Paz <mt...@tid.es>.
Manuel Teira Paz escribió:
> Andrew Stitcher escribió:
>
>> On Tue, 2009-02-24 at 12:37 +0100, Manuel Teira Paz wrote:
>>
>>
>>> Hello everybody. Finally, I've got some spare time and would be nice to
>>> spend it helping the project a while.
>>>
>>>
>> Great to hear from you again.
>>
>> Can you tell us exactly what your development environment is?
>>
>> I have set up an OpenSolaris environment (2008/11). But I'd like to
>> replicate what you have.
>>
>> So what Sun compiler are you using?
>> What versions of autotools/boost etc. and from which repositories?
>>
>>
>>
> Hello Andrew.
>
> I'm using a Solaris 10 machine (ultra sparc), with the Sun Studio 10
> compiler suite (and last patches from Sun):
>
Mistake here, it is Sun Studio 12, not 10.
> CC: Sun C++ 5.9 SunOS_sparc Patch 124863-09 2008/12/16
>
>
> I've compiled boost with it, using boost-jam (boost is 1.35.0 and
> boost-jam is 3.1.16), configuring as:
>
> ../boost-jam-3.1.16/bin.solaris/bjam --build-type=minimal
> --layout=system --prefix=/opt/qpid --without-python toolset=sun
> stdlib=sun-stlport address-model=64 stage
>
> ../boost-jam-3.1.16/bin.solaris/bjam --prefix=/opt/qpid
> --build-type=minimal --layout=system --without-python toolset=sun
> stdlib=sun-stlport address-model=64 install
>
> As you can see, I'm using /opt/qpid as the basedir for the qpid stuff.
>
> About the --without-python flag. I've run into problems derived from the
> fact that I installed a 32 bits python package, whereas the qpid I'm
> trying to generate is 64 bits. So, some headers complain.
>
> Next thing was cppunit 1.12.0, using this configuration line:
>
> CC="cc -m64 -mt" CXX="CC -m64 -mt" LD="CC -m64" LDFLAGS="-lm"
> ../cppunit-1.12.0/configure --prefix=/opt/qpid
>
> The other pieces of software I need, were downloaded from sunfreeware:
>
> automake 1.10.1
> libtool 1.5.24
> autoconf 2.60
> python 2.5.1
> ruby 1.8.6 (2008-03-03 patchlevel 114)
>
> I'm using native Sun make and linker (in Solaris 10 located in
> /usr/ccs/bin). Don't know what's the layout of OpenSolaris.
>
>
> About qpid itself, I'm configuring it this way:
>
> CC="cc -g -m64" CXX="CC -g -m64" CXXFLAGS="-I/opt/qpid/include"
> LDFLAGS="-L/opt/qpid/lib" ./configure --prefix=/opt/qpid
> --with-cppunit-prefix=/opt/qpid --with-ssl=no --enable-dependency-tracking
>
> Please note that in the current state, it won't compile. I have multiple
> changes ready to improve the situation, but some problems like the
> socklen_t are still work in progress. Also, refactoring of the poller to
> match the current model is on the way.
>
>
> Regards.
>
>
>
>
>
>
>
>
>
>
>
>
>
>> Andrew
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Manuel Teira Paz <mt...@tid.es>.
Andrew Stitcher escribió:
> On Tue, 2009-02-24 at 12:37 +0100, Manuel Teira Paz wrote:
>
>> Hello everybody. Finally, I've got some spare time and would be nice to
>> spend it helping the project a while.
>>
>
> Great to hear from you again.
>
> Can you tell us exactly what your development environment is?
>
> I have set up an OpenSolaris environment (2008/11). But I'd like to
> replicate what you have.
>
> So what Sun compiler are you using?
> What versions of autotools/boost etc. and from which repositories?
>
>
Hello Andrew.
I'm using a Solaris 10 machine (ultra sparc), with the Sun Studio 10
compiler suite (and last patches from Sun):
CC: Sun C++ 5.9 SunOS_sparc Patch 124863-09 2008/12/16
I've compiled boost with it, using boost-jam (boost is 1.35.0 and
boost-jam is 3.1.16), configuring as:
../boost-jam-3.1.16/bin.solaris/bjam --build-type=minimal
--layout=system --prefix=/opt/qpid --without-python toolset=sun
stdlib=sun-stlport address-model=64 stage
../boost-jam-3.1.16/bin.solaris/bjam --prefix=/opt/qpid
--build-type=minimal --layout=system --without-python toolset=sun
stdlib=sun-stlport address-model=64 install
As you can see, I'm using /opt/qpid as the basedir for the qpid stuff.
About the --without-python flag. I've run into problems derived from the
fact that I installed a 32 bits python package, whereas the qpid I'm
trying to generate is 64 bits. So, some headers complain.
Next thing was cppunit 1.12.0, using this configuration line:
CC="cc -m64 -mt" CXX="CC -m64 -mt" LD="CC -m64" LDFLAGS="-lm"
../cppunit-1.12.0/configure --prefix=/opt/qpid
The other pieces of software I need, were downloaded from sunfreeware:
automake 1.10.1
libtool 1.5.24
autoconf 2.60
python 2.5.1
ruby 1.8.6 (2008-03-03 patchlevel 114)
I'm using native Sun make and linker (in Solaris 10 located in
/usr/ccs/bin). Don't know what's the layout of OpenSolaris.
About qpid itself, I'm configuring it this way:
CC="cc -g -m64" CXX="CC -g -m64" CXXFLAGS="-I/opt/qpid/include"
LDFLAGS="-L/opt/qpid/lib" ./configure --prefix=/opt/qpid
--with-cppunit-prefix=/opt/qpid --with-ssl=no --enable-dependency-tracking
Please note that in the current state, it won't compile. I have multiple
changes ready to improve the situation, but some problems like the
socklen_t are still work in progress. Also, refactoring of the poller to
match the current model is on the way.
Regards.
> Andrew
>
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Andrew Stitcher <as...@redhat.com>.
On Tue, 2009-02-24 at 12:37 +0100, Manuel Teira Paz wrote:
> Hello everybody. Finally, I've got some spare time and would be nice to
> spend it helping the project a while.
Great to hear from you again.
Can you tell us exactly what your development environment is?
I have set up an OpenSolaris environment (2008/11). But I'd like to
replicate what you have.
So what Sun compiler are you using?
What versions of autotools/boost etc. and from which repositories?
Andrew
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Manuel Teira Paz <mt...@tid.es>.
Gordon Sim escribió:
> Manuel Teira Paz wrote:
>
>> Hello everybody. Finally, I've got some spare time and would be nice to
>> spend it helping the project a while.
>>
>
> Welcome back; good to hear from you again
>
Thanks a lot, Gordon!
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Solaris Port. Project dependencies
Posted by Gordon Sim <gs...@redhat.com>.
Manuel Teira Paz wrote:
> Hello everybody. Finally, I've got some spare time and would be nice to
> spend it helping the project a while.
Welcome back; good to hear from you again!
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org