[MacPorts] #44079: libgcc: error: 'signed' and 'unsigned' specified together
MacPorts
noreply at macports.org
Sat Jun 21 09:50:49 PDT 2014
#44079: libgcc: error: 'signed' and 'unsigned' specified together
-------------------------------+-------------------
Reporter: creativecommon@… | Owner: mww@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.0
Resolution: | Keywords:
Port: gcc48 |
-------------------------------+-------------------
Comment (by creativecommon@…):
Replying to [comment:3 ryandesign@…]:
> Your output shows that rev-upgrade determined that libgcc was broken,
and then failed to rebuild it. According to the log, the first reasons the
build failed are:
>
> {{{
> :info:build
/macports/var/macports/build/_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/build/x86_64
-apple-darwin11/libstdc++-v3/include/bits/stl_algobase.h:1000:27: error:
'signed' and 'unsigned' specified together for '__n'
> :info:build __lg(unsigned long long __n)
> :info:build ^
> :info:build
/macports/var/macports/build/_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/build/x86_64
-apple-darwin11/libstdc++-v3/include/bits/stl_algobase.h:1000:30: error:
'signed' and 'unsigned' specified together for '__lg'
> :info:build __lg(unsigned long long __n)
> :info:build ^
> }}}
>
> It might be interesting to know why rev-upgrade thinks libgcc is broken.
Is it shown in the output of "`port outdated`"? What does "`sudo port -v
rev-upgrade`" show?
Thanks for your help.
I did a clean all, and then did a "port upgrade outdated". I was
successfully able to upgrade all my outdated ports (including libgcc and
gcc48 @4.8.2 ).
This defect can be closed.
PS: Once again thanks for all your help ryandesign and others.
--
Ticket URL: <https://trac.macports.org/ticket/44079#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list