uns version 3.2.0.24-0ubuntu5 failed to build on i386

Bug #756096 reported by Matthias Klose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
uns (Ubuntu)
Confirmed
High
Unassigned
Oneiric
Won't Fix
High
Unassigned

Bug Description

uns version 3.2.0.24-0ubuntu5 failed to build on i386
Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110329/+buildjob/2412788

Direct link to the build log: https://launchpad.net/ubuntu/+archive/test-rebuild-20110329/+buildjob/2412788/+files/buildlog_ubuntu-natty-i386.uns_3.2.0.24-0ubuntu5_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 1347 lines into the build log:

                 from BaseWSManClient.h:45,
                 from UNSWSManClient.h:53,
                 from UserNotificationThread.h:54,
                 from UserNotificationServiceLinux.h:54,
                 from UNSMainLinux.cpp:59:
/usr/include/openwsman/cpp/WsmanEPR.h:5:23: fatal error: wsman-epr.h: No such file or directory
compilation terminated.
make[3]: *** [uns-UNSMainLinux.o] Error 1
make[3]: Leaving directory `/build/buildd/uns-3.2.0.24'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/build/buildd/uns-3.2.0.24'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/buildd/uns-3.2.0.24'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110408-1758
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/uns-3.2.0.24

Matthias Klose (doko)
Changed in uns (Ubuntu):
importance: Undecided → High
tags: added: oneiric
Changed in uns (Ubuntu):
milestone: none → oneiric-alpha-1
Changed in uns (Ubuntu Oneiric):
milestone: oneiric-alpha-1 → oneiric-alpha-2
Changed in uns (Ubuntu Oneiric):
milestone: oneiric-alpha-2 → none
status: New → Confirmed
tags: added: universe
Revision history for this message
Andy Whitcroft (apw) wrote :

Ok so the error of record is as below:

    In file included from /usr/include/openwsman/cpp/WsmanFilter.h:6:0,
                 from /usr/include/openwsman/cpp/WsmanClient.h:18,
                 from /usr/include/openwsman/cpp/OpenWsmanClient.h:14,
                 from BaseWSManClient.h:45,
                 from UNSWSManClient.h:53,
                 from UserNotificationThread.h:54,
                 from UserNotificationServiceLinux.h:54,
                 from UNSMainLinux.cpp:59:
    /usr/include/openwsman/cpp/WsmanEPR.h:5:23: fatal error: wsman-epr.h: No such file or directory

The application itself just includes the header as below:

    #include <openwsman/cpp/OpenWsmanClient.h>

We then chain through a number of headers using #include "" syntax:

    OpenWsmanClient.h: #include "WsmanClient.h"
    WsmanClient.h: #include "WsmanFilter.h"
    WsmanFilter.h: #include "WsmanEPR.h"
    WsmanEPR.h: #include "wsman-epr.h"

The final one above is bound to fail as the include file is in the /usr/include/openwsman directory.

Revision history for this message
Matthias Klose (doko) wrote :

2011-09-29 10:19:43 INFO Removing candidates:
2011-09-29 10:19:43 INFO uns 3.2.0.24-0ubuntu5 in oneiric amd64
2011-09-29 10:19:43 INFO uns 3.2.0.24-0ubuntu5 in oneiric armel
2011-09-29 10:19:43 INFO uns 3.2.0.24-0ubuntu5 in oneiric i386
2011-09-29 10:19:43 INFO uns 3.2.0.24-0ubuntu5 in oneiric powerpc
2011-09-29 10:19:43 INFO Removed-by: Matthias Klose
2011-09-29 10:19:43 INFO Comment: FTFBS in oneiric, see LP: #756096, remove binary package
2011-09-29 10:19:43 INFO 4 packages successfully removed.

Matthias Klose (doko)
Changed in uns (Ubuntu Oneiric):
status: Confirmed → Won't Fix
Revision history for this message
Ilya Barygin (randomaction) wrote :

I was able to fix and this and several other errors, but the build still fails with:

g++ -DHAVE_CONFIG_H -I. -I. -I. -I. -I. -I./SyncLib/Include -I./WSMAN_Common/MofCppFiles/Include -I./WSMAN_Common/Include -I./AMTStatus -I./AMTStatus/heci/StatusStrings -I./AMTStatus/heci/Linux -I./SoapServer -I./SoapServer/gSOAP/plugin -I./SoapServer/gSoapGeneratedCode -D_SYS_SYSMACROS_H=1 -I/usr/include/openwsman -I/usr/include/openwsman/cpp -D_FORTIFY_SOURCE=2 -DWITH_IPV6 -DWITH_OPENSSL -DWITH_DOM -DWITH_COOKIES -DWITH_GZIP -D_LINUX -fPIC -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -fpermissive -c -o uns-soapC.o `test -f 'SoapServer/gSoapGeneratedCode/soapC.cpp' || echo './'`SoapServer/gSoapGeneratedCode/soapC.cpp
SoapServer/gSoapGeneratedCode/soapC.cpp: In function 'void soap_markelement(soap*, const void*, int)':
SoapServer/gSoapGeneratedCode/soapC.cpp:1228:79: error: 'soap_serialize_sai__ProvisioningOTPType' was not declared in this scope
SoapServer/gSoapGeneratedCode/soapC.cpp:1243:67: error: 'soap_serialize_cmn__GuidBuf' was not declared in this scope
SoapServer/gSoapGeneratedCode/soapC.cpp: At global scope:
SoapServer/gSoapGeneratedCode/soapC.cpp:4989:6: error: redefinition of 'void xsd__base64Binary::soap_default(soap*)'
SoapServer/gSoapGeneratedCode/soapC.cpp:4660:6: error: 'virtual void xsd__base64Binary::soap_default(soap*)' previously defined here
SoapServer/gSoapGeneratedCode/soapC.cpp:4999:6: error: redefinition of 'void xsd__base64Binary::soap_serialize(soap*) const'
SoapServer/gSoapGeneratedCode/soapC.cpp:4670:6: error: 'virtual void xsd__base64Binary::soap_serialize(soap*) const' previously defined here
SoapServer/gSoapGeneratedCode/soapC.cpp:13195:6: error: redefinition of 'void xsd__base64Binary::soap_default(soap*)'
SoapServer/gSoapGeneratedCode/soapC.cpp:4660:6: error: 'virtual void xsd__base64Binary::soap_default(soap*)' previously defined here
SoapServer/gSoapGeneratedCode/soapC.cpp:13205:6: error: redefinition of 'void xsd__base64Binary::soap_serialize(soap*) const'
SoapServer/gSoapGeneratedCode/soapC.cpp:4670:6: error: 'virtual void xsd__base64Binary::soap_serialize(soap*) const' previously defined here
make[4]: *** [uns-soapC.o] Error 1

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.