[Bug 196143] New: [patch] mail/libmapi - build fix for non c++11 systems (e.g., base compiler on freebsd 9.3)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Dec 19 21:19:31 UTC 2014


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196143

            Bug ID: 196143
           Summary: [patch] mail/libmapi - build fix for non c++11 systems
                    (e.g., base compiler on freebsd 9.3)
           Product: Ports Tree
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: kwm at FreeBSD.org
          Reporter: z7dr6ut7gs at snkmail.com
             Flags: maintainer-feedback?(kwm at FreeBSD.org)
          Assignee: kwm at FreeBSD.org

Created attachment 150791
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=150791&action=edit
specify c++11 lib for libmapi 2.1 build

mail/libmapi-2.1 has two problems on freebsd systems that don't have a default
compiler that support newer c++ standards used by libmapi:

The Makefile has "CXX11FLAGS=-std=c++0x".  When you build on 9.x, you
get:

 .
 .
   Linking libmapi.so.2.0
   Compiling libmapi++/src/attachment.cpp with -fPIC
   cc1plus: error: unrecognized command line option "-std=c++0x"
 .
 .


Adding USES=compiler:c++0x fixes that problem, but libmapi 2.1 also
needs a c++ library that has shared_ptr:

 .
 .
In file included from ./libmapi++/attachment.h:29:
./libmapi++/message.h:47:16: error: no type named 'shared_ptr' in namespace
'std'
                typedef std::shared_ptr<attachment>            
attachment_shared_ptr;
 .
 .


USES=compiler:c++11-lib fixes both issues.


Patch attached.


See also
http://beefy1.isc.freebsd.org/bulk/84i386-default/latest/logs/errors/libmapi-2.1_2.log

--- Comment #1 from Bugzilla Automation <bugzilla at FreeBSD.org> ---
Auto-assigned to maintainer kwm at FreeBSD.org

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list