Carolyn

It broke with this morning's checkin. This is the standard g++ on
CentOS5
--martin


-----Original Message-----
From: Beeton, Carolyn (CAR:9D60) 
Sent: Friday, October 31, 2008 12:22 PM
To: Steinmann, Martin (BL60:2500); [EMAIL PROTECTED]
Subject: RE: [sipX-dev] portlib fails to build, svn 13863, CentOS 5 64
bit

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Steinmann, Martin (BL60:2500)
> Sent: Friday, October 31, 2008 11:16 AM
> To: [EMAIL PROTECTED]
> Subject: [sipX-dev] portlib fails to build, svn 13863, CentOS 5 64 bit
> 
> 
> os/linux/OsProcessLinux.cpp: In member function 'virtual 
> OsStatus OsProcessLinux::launch(UtlString&, UtlString*, 
> OsPath&, OsProcessBase::OsProcessPriorityClass, UtlBoolean, 
> UtlBoolean)':
> os/linux/OsProcessLinux.cpp:272: warning: ignoring return 
> value of 'int pipe(int*)', declared with attribute warn_unused_result
> os/linux/OsProcessLinux.cpp:273: warning: ignoring return 
> value of 'int pipe(int*)', declared with attribute warn_unused_result
> make[6]: *** [libsipXport_la-OsProcessLinux.lo] Error 1
> make[6]: Leaving directory
> `/home/sipxbuild/rpmbuild/BUILD/sipxportlib-3.11.7/src'
> make[5]: *** [all-recursive] Error 1
> make[5]: Leaving directory
> `/home/sipxbuild/rpmbuild/BUILD/sipxportlib-3.11.7/src'
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory
> `/home/sipxbuild/rpmbuild/BUILD/sipxportlib-3.11.7'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory
> `/home/sipxbuild/rpmbuild/BUILD/sipxportlib-3.11.7'
> error: Bad exit status from /var/tmp/rpm-tmp.3950 (%build)
> 
> 
> RPM build errors:
>     Bad exit status from /var/tmp/rpm-tmp.3950 (%build)
> make[2]: *** [build-rpm] Error 1
> make[2]: Leaving directory
> `/home/sipxbuild/src/main/RPMBUILD/sipXportLib'
> make[1]: *** [recurse] Error 1
> make[1]: Leaving directory `/home/sipxbuild/src/main/RPMBUILD'
> make: *** [rpm] Error 2
> 
> 

Looks like your platform/version of g++ sets some flag that makes
ignoring return codes a warning (and hence a failure in projects with
-Werror).  It doesn't fail on either of my platforms (SuSE 10.3 64bit or
FC8 64bit)  Is this level of warning reasonable?  I see lots of existing
code in this same file which does not handle the return values.

Carolyn
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to