[
https://issues.apache.org/jira/browse/MESOS-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013173#comment-14013173
]
Timothy St. Clair commented on MESOS-1385:
------------------------------------------
Follow up thread :
https://lists.fedoraproject.org/pipermail/devel/2014-May/199477.html
If you're building RPMs locally, you can drop your own definition of
__global_cflags into '~/.rpmmacros':
%__global_cflags -O2 -g ..etc..
If you are building a package that uses an autoconf-generated
configure script, then simply setting CFLAGS before running configure
should be enough, eg:
CFLAGS="$(
rpm --eval '%{__global_cflags}' |
sed 's/-fstack-protector-strong//'
)" \
./configure
> clang: error: unknown argument: '-fstack-protector-strong'
> ----------------------------------------------------------
>
> Key: MESOS-1385
> URL: https://issues.apache.org/jira/browse/MESOS-1385
> Project: Mesos
> Issue Type: Bug
> Components: build
> Environment: Fedora 20
> clang 3.4
> Reporter: Vinson Lee
> Assignee: Timothy St. Clair
> Priority: Blocker
>
> {noformat}
> checking consistency of all components of python development environment...
> yes
> checking whether we can build usable Python eggs... clang: error: unknown
> argument: '-fstack-protector-strong'
> clang: error: unknown argument: '-fstack-protector-strong'
> error: command 'clang' failed with exit status 1
> configure: error: no
> -------------------------------------------------------------------
> It appears we were unable to build a usable native Python egg.
> There are two possible workarounds for this issue:
> 1. Disable python bindings by configuring with --disable-python.
> 2. Use an alternative Python installation that was built using
> the same build setup as Mesos.
> -------------------------------------------------------------------
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
