Opened 13 months ago

Closed 11 months ago

Last modified 11 months ago

#67217 closed defect (fixed)

protobuf3-cpp @3.19.3: libtool: error: 'google/protobuf/compiler/cpp/cpp_message.lo' is not a valid libtool object

Reported by: barracuda156 Owned by: mascguy (Christopher Nielsen)
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: snowleopard Cc:
Port: protobuf3-cpp

Description

  CXXLD    libprotobuf-lite.la
/opt/local/bin/ranlib: file: .libs/libprotobuf-lite.a(io_win32.o) has no symbols
ranlib: file: .libs/libprotobuf-lite.a(io_win32.o) has no symbols
  CXXLD    libprotoc.la
libtool:   error: 'google/protobuf/compiler/cpp/cpp_message.lo' is not a valid libtool object
make[2]: *** [libprotoc.la] Error 1
make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_protobuf3-cpp/protobuf3-cpp/work/protobuf-3.19.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_protobuf3-cpp/protobuf3-cpp/work/protobuf-3.19.3'
make: *** [all] Error 2

Change History (10)

comment:1 Changed 13 months ago by barracuda156

Summary: protobuf3-cpp fails to build on 10.6.8: libtool: error: 'google/protobuf/compiler/cpp/cpp_message.lo' is not a valid libtool objectprotobuf3-cpp fails to build on 10.6.8 (Rosetta): libtool: error: 'google/protobuf/compiler/cpp/cpp_message.lo' is not a valid libtool object

comment:2 Changed 13 months ago by barracuda156

UPD. Builds fine on 10.6 PPC, only Rosetta fails.

comment:3 Changed 11 months ago by ryandesign (Ryan Carsten Schmidt)

Summary: protobuf3-cpp fails to build on 10.6.8 (Rosetta): libtool: error: 'google/protobuf/compiler/cpp/cpp_message.lo' is not a valid libtool objectprotobuf3-cpp @3.19.3: libtool: error: 'google/protobuf/compiler/cpp/cpp_message.lo' is not a valid libtool object

The port was just updated to a newer version; you might try again.

comment:4 Changed 11 months ago by mascguy (Christopher Nielsen)

Can you try building again, once the latest update (the switch to using CMake) comes through?

comment:5 Changed 11 months ago by mascguy (Christopher Nielsen)

Owner: set to mascguy
Status: newassigned

comment:6 Changed 11 months ago by mascguy (Christopher Nielsen)

Of note, I've built the latest version of protobuf3-cpp successfully all the way back to 10.5, without any issues. Including today's update, which migrated the port from autotools to cmake.

comment:7 in reply to:  6 Changed 11 months ago by mascguy (Christopher Nielsen)

Replying to mascguy:

Of note, I've built the latest version of protobuf3-cpp successfully all the way back to 10.5, without any issues. Including today's update, which migrated the port from autotools to cmake.

Update: All of those builds were Intel, including 32-bit. Just installed it on my old 10.5 PPC machine too, again with no issue.

comment:8 in reply to:  6 ; Changed 11 months ago by barracuda156

Replying to mascguy:

Of note, I've built the latest version of protobuf3-cpp successfully all the way back to 10.5, without any issues. Including today's update, which migrated the port from autotools to cmake.

I will try Rosetta now. Thank you. (Native PPC was consistently fine.)

UPD. Awesome, it builds in Rosetta now with no issues! Thanks again.

Last edited 11 months ago by barracuda156 (previous) (diff)

comment:9 in reply to:  8 Changed 11 months ago by mascguy (Christopher Nielsen)

Resolution: fixed
Status: assignedclosed

Replying to barracuda156:

I will try Rosetta now. Thank you. (Native PPC was consistently fine.)

UPD. Awesome, it builds in Rosetta now with no issues! Thanks again.

Great, glad the issue is resolved!

comment:10 Changed 11 months ago by mascguy (Christopher Nielsen)

p.s. When providing an update, be sure to reply with a new comment, rather than editing an existing one. Reason being, we don't receive any notifications via Trac, when an edit occurs. (Edit is fine for fixing typos and such, but be sure to post a new comment otherwise.)

I wouldn't have known the issue was fixed, if I hadn't brought up this ticket. Lol

Note: See TracTickets for help on using tickets.