Opened 11 years ago

Closed 5 years ago

Last modified 5 years ago

#37001 closed defect (worksforme)

smpeg @0.4.4: error: invalid conversion from 'const char*' to 'char*'

Reported by: two4juan@… Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc: silverdr@…, alex.tek@…
Port: smpeg

Description

First time submitting a ticket. I cannot properly install smpeg, which tells me it's a broken port and fails to install in my system. I'm running 10.6.8 with Xcode 3.2.6. First error that shows is "Error: org.macports.build for port smpeg returned: command execution failed". I'm attaching the log to this ticket.

Attachments (2)

main.log (12.2 KB) - added by two4juan@… 11 years ago.
main.2.log (6.6 KB) - added by two4juan@… 11 years ago.

Download all attachments as: .zip

Change History (14)

Changed 11 years ago by two4juan@…

Attachment: main.log added

comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to mww@…

The log is not from a clean build attempt. Please "sudo port clean smpeg", then try again, then attach the new main.log if it fails again.

comment:2 Changed 11 years ago by mf2k (Frank Schima)

Type: submissiondefect

comment:3 in reply to:  2 Changed 11 years ago by two4juan@…

Replying to macsforever2000@…:

Sorry about that. It failed to build again with a clean build. I will now attach the new log.

Changed 11 years ago by two4juan@…

Attachment: main.2.log added

comment:4 Changed 11 years ago by jmroot (Joshua Root)

That still isn't a complete log; you can tell because it has lines like "Skipping completed org.macports.configure (smpeg)".

comment:5 Changed 11 years ago by jmroot (Joshua Root)

Summary: smpeg failed to buildsmpeg @0.4.4 +universal failed to build

It also looks like you're building with +universal. It's good to mention that up front.

comment:6 Changed 11 years ago by two4juan@…

Maybe I am missing something, but I performed "sudo port install smpeg" and the log I posted is under "/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_smpeg/smpeg/main.log". The log says I was not running root which is confusing because I used sudo.

I don't necessarily want to install +universal. I will try to install smpeg without +universal and see if that fixes it, once I figure out how to do that.

comment:7 Changed 11 years ago by two4juan@…

Tried the install without +universal and it gave me the same result. I am still not sure what the problem is, but hopefully a fresh install of 10.6 or later on 10.8 might fix this issue. Thanks anyway.

comment:8 in reply to:  7 Changed 11 years ago by alex.tek@…

Replying to two4juan@…:

Tried the install without +universal and it gave me the same result. I am still not sure what the problem is, but hopefully a fresh install of 10.6 or later on 10.8 might fix this issue. Thanks anyway.

8 months later, I have the same problem (same system, same log and no +universal). I couldn't find a fix. It is really annoying because it is a dependency for netcdf...

comment:9 Changed 10 years ago by mf2k (Frank Schima)

Cc: silverdr@… added

Cc'ing reporter of duplicate #39758.

comment:10 Changed 7 years ago by mf2k (Frank Schima)

Owner: mww@… deleted
Status: newassigned

See #53012.

comment:11 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: alex.tek@… added
Resolution: worksforme
Status: assignedclosed
Summary: smpeg @0.4.4 +universal failed to buildsmpeg @0.4.4: error: invalid conversion from 'const char*' to 'char*'

We haven't seen this problem on any macOS version on our automated build system, so I'm going to close the ticket, assuming it is something unusual about the systems of those who have experienced the problem. For example, one possibility might be that you have a rogue copy of libsdl in /usr/local/{lib,include} or /Library/Frameworks that differs from the one provided by MacPorts.

If you're still experiencing this problem today, please re-open the ticket and attach a main.log file of a clean build; neither of the main.logs that have been attached so far are from clean builds (they both contain the phrase "Skipping completed") so they lack enough context for us to diagnose the problem.

comment:12 Changed 5 years ago by jmroot (Joshua Root)

Could have been due to building against libsdl-devel, which is long gone.

Note: See TracTickets for help on using tickets.