Opened 16 months ago

Closed 16 months ago

Last modified 16 months ago

#66512 closed defect (fixed)

rb-eventmachine @0.12.10_1: rb-eventmachine is using libstdc++ (this installation is configured to use libc++)

Reported by: cooljeanius (Eric Gallager) Owned by: kimuraw (kimura wataru)
Priority: Normal Milestone:
Component: ports Version: 2.8.0
Keywords: Cc:
Port: rb-eventmachine

Description

--->  No broken files found.
rb-eventmachine is using libstdc++ (this installation is configured to use libc++)
Error: Port rb-eventmachine is still broken (cxx_stdlib mismatch) after rebuilding it more than 3 times.
DEBUG: rev-upgrade failed: Port rb-eventmachine still broken after rebuilding 3 times
    while executing
"error "Port $portname still broken after rebuilding $rebuild_tries time${s}""
    (procedure "revupgrade_scanandrebuild" line 315)
    invoked from within
"revupgrade_scanandrebuild broken_port_counts $opts"
Error: rev-upgrade failed: Port rb-eventmachine still broken after rebuilding 3 times
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.

I'm on Big Sur (x86_64) with Xcode 13.2.1.

Change History (3)

comment:1 Changed 16 months ago by ryandesign (Ryan Carsten Schmidt)

Cc: kimuraw removed
Owner: set to kimuraw
Status: newassigned
Summary: rb-eventmachine @0.12.10_1: still broken (cxx_stdlib mismatch) after rebuilding more than 3 times.rb-eventmachine @0.12.10_1: rb-eventmachine is using libstdc++ (this installation is configured to use libc++)

comment:2 Changed 16 months ago by kimura wataru <kimuraw@…>

Resolution: fixed
Status: assignedclosed

In fb00ab529a7adbb90a55e326b8d8efd3413a5603/macports-ports (master):

ruby/rb-eventmachine: delete old unmaintained ports with its dependencies

closes #66512

  • rb-eventmachine

-> rb-twitter-stream

-> rb-tweetstream

  • rb19-eventmachine

-> rb-em-websocket

-> rb-guard-livereload

-> rb-thin

comment:3 Changed 16 months ago by cooljeanius (Eric Gallager)

aw man that's not exactly the outcome I was hoping for... oh well, I guess it works...

Note: See TracTickets for help on using tickets.