OpenWSMAN 2.2

[A_Venkatachalam]

Hi

What is the status of OpenWSMAN 2.2 release? When can we expect its release?

Thanks,

Arun Venkatachalam

Dell R & D Centre,

Bangalore.

Extn - 78973

P Please consider the environment before printing this e-mail.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* A_Venkatachalam@... <A_Venkatachalam@...> [Sep 08. 2009 07:10]:
> Hi
>
> What is the status of OpenWSMAN 2.2 release? When can we expect its
> release?

Have you stress-tested the current svn head (rev 3233) ? If its fine, I
guess I can tag it as final for 2.2.

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[A_Venkatachalam]

Hi Klaus,

 I downloaded the latest revision 3233, when I tried to build it ti Was getting the following error in case of configure

[root@SBI_RHEL5 OPENWSMAN2.2pre_3233]# sh autoconfiscate.sh
[root@SBI_RHEL5 OPENWSMAN2.2pre_3233]# ./configure
checking build system type... i686-redhat-linux-gnu
checking host system type... i686-redhat-linux-gnu
configure: error: cannot find macro directory `m4'


This is caused because of a line in configure.in

AC_CONFIG_MACRO_DIR([m4])

When I comment it everything works fine.


The root cause of this issue was Libtool version. The latest version of libtool (2.2) present on SLES11 recommends that we use the above macro so that we need not carry m4 macros, but older version of libtool(1.5) present in sles10 and rhel 5 does not have this feature and we need to comment the above line and it works.


So what should be the approach to fix this, let the line be, and ask uses to upgrade their libtool or shall this should be removed for now?

Thanks,

Arun Venkatachalam
Dell R & D Centre,
Bangalore.
Extn - 78973

 Please consider the environment before printing this e-mail.


-----Original Message-----
From: Klaus Kaempf [mailto:kkaempf@...]
Sent: Tuesday, September 08, 2009 1:37 PM
To: Venkatachalam, A
Cc: openwsman-devel@...
Subject: Re: [Openwsman-devel] OpenWSMAN 2.2

* A_Venkatachalam@... <A_Venkatachalam@...> [Sep 08. 2009 07:10]:
> Hi
>
> What is the status of OpenWSMAN 2.2 release? When can we expect its
> release?

Have you stress-tested the current svn head (rev 3233) ? If its fine, I
guess I can tag it as final for 2.2.

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* A_Venkatachalam@... <A_Venkatachalam@...> [Sep 08. 2009 10:59]:

> Hi Klaus,
>
>  I downloaded the latest revision 3233, when I tried to build it ti Was getting the following error in case of configure
>
> [root@SBI_RHEL5 OPENWSMAN2.2pre_3233]# sh autoconfiscate.sh
> [root@SBI_RHEL5 OPENWSMAN2.2pre_3233]# ./configure
> checking build system type... i686-redhat-linux-gnu
> checking host system type... i686-redhat-linux-gnu
> configure: error: cannot find macro directory `m4'
>
>
> This is caused because of a line in configure.in
>
> AC_CONFIG_MACRO_DIR([m4])
>
> When I comment it everything works fine.
>
>
> The root cause of this issue was Libtool version. The latest version of
> libtool (2.2) present on SLES11 recommends that we use the above macro
> so that we need not carry m4 macros,

That was the reason I put this line in.

> but older version of libtool(1.5) present in sles10 and rhel 5 does not
> have this feature and we need to comment the above line and it works.

What if you leave the line in but run "mkdir m4" before ? The error
message above seems to indicate a missing directory only.

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel