Pushed changes, so you should be good now on a mock rebuild for EL7 from 
f23.spec file. 

I still need to do the housekeeping work around cleaning logging etc, but I'll 
post back when that is done. 

Cheers, 
Tim 

----- Original Message -----

> From: "Jeff Schroeder" <[email protected]>
> To: [email protected]
> Sent: Tuesday, August 4, 2015 9:42:15 PM
> Subject: Re: Problem building 0.23.0 under mock for RHEL7

> I made no changes. The mesos Makefile did this! It is a non-modified RHEL7.1
> install.

> This is likely an issue. I'll work with Tim tomorrow to hopefully fix it and
> can send a patch to the docs to fix it.

> Text by Jeff, typos by iPhone

> On Tuesday, August 4, 2015, haosdent < [email protected] > wrote:

> > No, I think this should use g++
> 
> > ```
> 
> > gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
> > -Wp,-D_FORTIFY_SOURCE=2
> > -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
> > -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv
> > -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> > -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches
> > -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC
> > -I/builddir/build/BUILD/mesos-0.23.0/include
> > -I/builddir/build/BUILD/mesos-0.23.0/include
> > -I/builddir/build/BUILD/mesos-0.23.0/include/mesos
> > -I/builddir/build/BUILD/mesos-0.23.0/src
> > -I/builddir/build/BUILD/mesos-0.23.0/src/python/native/src/mesos/native
> > -I/builddir/build/BUILD/mesos-0.23.0/3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
> > -I/usr/include/python2.7 -c
> > src/mesos/native/mesos_scheduler_driver_impl.cpp
> > -o
> > build/temp.linux-x86_64-2.7/src/mesos/native/mesos_scheduler_driver_impl.o
> 
> > In file included from
> > src/mesos/native/mesos_scheduler_driver_impl.hpp:22:0,
> 
> > from src/mesos/native/mesos_scheduler_driver_impl.cpp:25:
> 
> > /builddir/build/BUILD/mesos-0.23.0/include/mesos/scheduler.hpp:486:15:
> > error:
> > 'function' in namespace 'std' does not name a type
> 
> > const std::function<void(void)>& connected,
> 
> > ^
> 
> > /
> 
> > ```
> 

> > On Wed, Aug 5, 2015 at 10:21 AM, Jeff Schroeder <
> > [email protected]
> > > wrote:
> 

> > > Because gcc can compile mesos?
> > 
> 

> > > On Tuesday, August 4, 2015, haosdent < [email protected] > wrote:
> > 
> 

> > > > Why the compiler in your log is gcc?
> > > 
> > 
> 

> > > > On Wed, Aug 5, 2015 at 9:58 AM, Tim St Clair < [email protected] >
> > > > wrote:
> > > 
> > 
> 

> > > > > I'll take a look in the a.m. feel free to ping me on irc.
> > > > 
> > > 
> > 
> 

> > > > > Cheers,
> > > > 
> > > 
> > 
> 
> > > > > Tim
> > > > 
> > > 
> > 
> 

> > > > > > From: "Jeff Schroeder" < [email protected] >
> > > > > 
> > > > 
> > > 
> > 
> 
> > > > > > To: "Mesos Users" < [email protected] >
> > > > > 
> > > > 
> > > 
> > 
> 
> > > > > > Sent: Tuesday, August 4, 2015 6:21:39 PM
> > > > > 
> > > > 
> > > 
> > 
> 
> > > > > > Subject: Problem building 0.23.0 under mock for RHEL7
> > > > > 
> > > > 
> > > 
> > 
> 

> > > > > > I'm trying to build Mesos 0.23.0, using a lightly modified spec
> > > > > > file
> > > > > > from
> > > > > > Fedora 23[1] with a few dependencies added for RHEL7. The build
> > > > > > fails
> > > > > > when
> > > > > > gcc is trying to build the mesos.native._mesos python bits.
> > > > > 
> > > > 
> > > 
> > 
> 

> > > > > > The full log is as a gist[2]. I don't recall ever seeing this
> > > > > > error,
> > > > > > and
> > > > > > was
> > > > > > curious if it has been seen before.
> > > > > 
> > > > 
> > > 
> > 
> 

> > > > > > [1] http://pkgs.fedoraproject.org/cgit/mesos.git/tree/?h=f23
> > > > > 
> > > > 
> > > 
> > 
> 
> > > > > > [2]
> > > > > > https://gist.githubusercontent.com/SEJeff/7c01db2704a1352c8d7e/raw/b606fa77b73984cfa02d62cc1c90f4ae736fae0a/build.log
> > > > > 
> > > > 
> > > 
> > 
> 

> > > > > > --
> > > > > 
> > > > 
> > > 
> > 
> 
> > > > > > Jeff Schroeder
> > > > > 
> > > > 
> > > 
> > 
> 

> > > > > > Don't drink and derive, alcohol and analysis don't mix.
> > > > > 
> > > > 
> > > 
> > 
> 
> > > > > > http://www.digitalprognosis.com
> > > > > 
> > > > 
> > > 
> > 
> 

> > > > > --
> > > > 
> > > 
> > 
> 
> > > > > Cheers,
> > > > 
> > > 
> > 
> 
> > > > > Timothy St. Clair
> > > > 
> > > 
> > 
> 
> > > > > Red Hat Inc.
> > > > 
> > > 
> > 
> 

> > > > --
> > > 
> > 
> 
> > > > Best Regards,
> > > 
> > 
> 
> > > > Haosdent Huang
> > > 
> > 
> 

> > > --
> > 
> 
> > > Text by Jeff, typos by iPhone
> > 
> 

> > --
> 
> > Best Regards,
> 
> > Haosdent Huang
> 

> --
> Text by Jeff, typos by iPhone

-- 
Cheers, 
Timothy St. Clair 
Red Hat Inc. 

Reply via email to