Opened 14 years ago

Closed 13 years ago

#22776 closed defect (worksforme)

cadaver-0.23.2 ld: symbol(s) not found

Reported by: pj_mfc@… Owned by: landonf (Landon Fuller)
Priority: Normal Milestone:
Component: ports Version: 1.8.1
Keywords: Cc:
Port: cadaver

Description

Cadaver fails to build once I upgraded to Snow Leopard. I'm using a macbook 5.1 running 10.6.2 and Xcode 3.2.

em-macbook:~ # sudo port install cadaver
--->  Computing dependencies for cadaver
--->  Building cadaver
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_cadaver/work/cadaver-0.23.2" && /usr/bin/make -j2 all " returned error 2
Command output:       _steal_result in commands.o
      _execute_lock in commands.o
      _execute_edit in edit.o
  "_ne_buffer_create", referenced from:
      _execute_label in version.o
      _execute_history in version.o

<snip - about 20 lines similar to above> 

  "_ne_has_support", referenced from:
      _open_connection in cadaver.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make: *** [cadaver] Error 1

Error: Status 1 encountered during processing.

Change History (8)

comment:1 Changed 14 years ago by pj_mfc@…

Cc: pj_mfc@… added

Cc Me!

comment:2 Changed 14 years ago by jmroot (Joshua Root)

Cc: pj_mfc@… removed
Keywords: cadaver build removed
Owner: changed from macports-tickets@… to landonf@…

comment:3 Changed 14 years ago by pj_mfc@…

Cc: pj_mfc@… added

Cc Me!

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

Cc: pj_mfc@… removed

comment:5 Changed 14 years ago by pj_mfc@…

Cc: pj_mfc@… added

Cc Me!

comment:6 in reply to:  4 Changed 14 years ago by pj_mfc@…

Replying to jmr@…:

Why am I getting removed from CC?

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

Cc: pj_mfc@… removed

The ticker reporter is automatically Cc'ed.

comment:8 Changed 13 years ago by jmroot (Joshua Root)

Resolution: worksforme
Status: newclosed

In the absence of a complete log, I'm going to guess that this was due to incorrect migration.

Note: See TracTickets for help on using tickets.