New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #32318 (new defect)

Opened 3 years ago

Last modified 3 years ago

pythia @8.135_0 conflicts with libevent on Event.h

Reported by: martin.zeman@… Owned by: mattiafrancescomoro@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: brett@…
Port: pythia

Description (last modified by ryandesign@…) (diff)

sudo port install pythia fails on activation due to a conflict in the includes: Event.h I believe this is connected to my installation of ROOT / libevent? I can provide a list of my installed ports, but I am not sure how to find to which port the conflicting event.h belongs. Is there a way to find out?

Cheers,

Martin

--->  Activating pythia @8.135_0
Error: Target org.macports.activate returned: Image error: /Ports/include/Event.h already exists and does not belong to a registered port.  Unable to activate port pythia. Use 'port -f activate pythia' to force the activation.
Log for pythia is at: /Ports/var/macports/logs/_Ports_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_pythia/pythia/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Change History

comment:1 Changed 3 years ago by ryandesign@…

  • Owner changed from macports-tickets@… to mattiafrancescomoro@…
  • Cc brett@… added
  • Summary changed from Installing Pythia @8.135_0 conflicts on Event.h to pythia @8.135_0 conflicts with libevent on Event.h
  • Port set to pythia
  • Description modified (diff)

The error message is a little misleading: "/Ports/include/Event.h already exists and does not belong to a registered port." It's true, no port provides Event.h, but libevent provides ${prefix}/include/event.h, which, on a case-insensitive filesystem like most of us use, is just as conflicting.

pythia and libevent should either be marked as conflicting with one another, or ideally, pythia should install its files somewhere else so it does not conflict.

Note: See TracTickets for help on using tickets.