Opened 5 years ago
Closed 5 years ago
#58541 closed defect (fixed)
build error at libuv
Reported by: | ClausKlein | Owned by: | michaelld (Michael Dickens) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.5.4 |
Keywords: | Cc: | michaelld (Michael Dickens) | |
Port: | libuv |
Description
:info:build Undefined symbols for architecture i386: :info:build "_close$NOCANCEL", referenced from: :info:build _uv__close_nocancel in libuv_la-core.o :info:build _uv__close_nocheckstdio in libuv_la-core.o :info:build ld: symbol(s) not found for architecture i386 :info:build clang: error: linker command failed with exit code 1 (use -v to see invocation) :info:build make: *** [libuv.la] Error 1 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libuv/libuv/work/libuv-1.29.1' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libuv/libuv/work/libuv-1.29.1" && /usr/bin/make -j2 -w all :info:build Exit code: 2 :error:build Failed to build libuv: command execution failed
Attachments (1)
Change History (17)
Changed 5 years ago by ClausKlein
comment:1 Changed 5 years ago by kencu (Ken)
comment:2 Changed 5 years ago by michaelld (Michael Dickens)
@kencu: this is 10.11 ... and +universal ... let me try this on my equivalent OSX boot bot & see what happens ...
comment:3 Changed 5 years ago by michaelld (Michael Dickens)
@ClausKlein : If you don't require +universal, I'd advise you to not use it ...
comment:4 Changed 5 years ago by michaelld (Michael Dickens)
Cc: | michaelld added |
---|
comment:5 Changed 5 years ago by kencu (Ken)
yes, but i set the patch to apply there as well. I did test it universal on several systems.
comment:6 Changed 5 years ago by michaelld (Michael Dickens)
FYI I see the exact same error when I build as +universal on 10.11.
I don't generally do +universal, since it's such a can of worms! Luckily, libuv doesn't have a lot of dependencies ...
comment:7 Changed 5 years ago by kencu (Ken)
perhaps check then that patch is actually being applied? it should be calling for the 32b symbol as per the patch.
comment:8 Changed 5 years ago by kencu (Ken)
looks like the devel port is not using the patch...the PR btw is still being reviewed upstream
comment:9 Changed 5 years ago by michaelld (Michael Dickens)
Yeah I think I was trying the devel port. I'm rechecking with the release version, and verified that the patch is definitely applied (yes, it is!).
comment:11 Changed 5 years ago by mf2k (Frank Schima)
Cc: | michaelld removed |
---|---|
Owner: | set to michaelld |
Status: | new → assigned |
comment:12 Changed 5 years ago by michaelld (Michael Dickens)
Cc: | michaelld added |
---|
OK the release version builds as +universal for me. Guessing I was trying the devel before.
comment:13 Changed 5 years ago by michaelld (Michael Dickens)
Thus, I think the solution is for @ClausKlein to do:
sudo port clean libuv sudo port selfupdate sudo port install libuv +universal
and, that should work & allow more updating / progress installing / whatever use of MacPorts is going on.
comment:14 Changed 5 years ago by kencu (Ken)
upstream pr <https://github.com/libuv/libuv/pull/2309>
comment:16 Changed 5 years ago by michaelld (Michael Dickens)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
@ClausKlein: Great! Thanks for reporting back!
hmmmm. I fixed this already, I thought. the fix has also been sent upstream. <https://github.com/macports/macports-ports/commit/1735bb1417aa634f94d7127c4c127f3d5f50e8e9#diff-64e1498b68963c990f644d9dd9ed1f29>.
perhaps selfupdate and try again.