New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #28317 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

aircrack-ng does not obey build_arch

Reported by: ironstorm@… Owned by: ryandesign@…
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc:
Port: aircrack-ng

Description

This is a note for anyone trying to build aircrack-ng and getting undefined symbols during linking (see attached build log).

:info:build ld: warning: in /opt/local/lib/libssl.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
:info:build ld: warning: in /opt/local/lib/libcrypto.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
:info:build Undefined symbols:
:info:build   "_SHA1_Final", referenced from:
...

This can be resolved by rebuilding openssl with +universal variant

sudo port install openssl +universal

Attachments

main.log (21.7 KB) - added by ironstorm@… 2 years ago.
aircrack-ng full build log with openssl undefined symbols

Change History

Changed 2 years ago by ironstorm@…

aircrack-ng full build log with openssl undefined symbols

comment:1 Changed 2 years ago by jmr@…

  • Keywords aircrack-ng openssl removed
  • Summary changed from aircrack-ng requires openssl be built +universal to aircrack-ng does not obey build_arch

comment:2 Changed 2 years ago by macsforever2000@…

I don't think this is required at all.

$ port installed aircrack-ng openssl
The following ports are currently installed:
  aircrack-ng @1.1_0 (active)
  openssl @1.0.0c_0 (active)

comment:3 Changed 2 years ago by jmr@…

There's only a problem if you use a non-default build_arch.

comment:4 Changed 2 years ago by ryandesign@…

  • Owner changed from macports-tickets@… to ryandesign@…
  • Status changed from new to assigned

comment:5 Changed 2 years ago by ryandesign@…

  • Status changed from assigned to closed
  • Resolution set to fixed

Fixed in r75790.

Note: See TracTickets for help on using tickets.