9

On Macintosh, to allow some symbols to go unlinked, it is necessary to pass -C link-args='-Wl,-undefined,dynamic_lookup' to the Rust compiler. One needs to do this when building Postgres plugins, because some of the Postgres intrinsics are only compiled into the Postgres server, and not available for linking from shared libs.

At present, the project's process is as follows:

  • Build is run with cargo build -v.
  • Failing call to rustc is copied and -C link-args='-Wl,-undefined,dynamic_lookup' added to it.
  • Success!

This seems like a hard sell for automation. What options are available for adding codegen flags to Rust builds through cargo?

Shepmaster
  • 388,571
  • 95
  • 1,107
  • 1,366
solidsnack
  • 1,631
  • 16
  • 26

1 Answers1

9

cargo provides rustc command which allows one to pass arbitrary compiler flags. The following should do it:

% cargo rustc -- -C link-args='-Wl,-undefined,dynamic_lookup'
Vladimir Matveev
  • 120,085
  • 34
  • 287
  • 296
  • 3
    This is helpful, thanks. I'm not sure about accepting this, though, because it doesn't provide a way to document and automate the build process. – solidsnack Jan 07 '16 at 00:19
  • This is really the only way to do anything close, so time to accept. – solidsnack Feb 15 '16 at 08:02
  • No way to put it to toml file? At all? – MajesticRa Jun 10 '16 at 13:36
  • @MajesticRa, nope, and Cargo is explicitly designed [against it](https://github.com/rust-lang/cargo/issues/60#issuecomment-51705597). Access to a subset of compiler configuration controlled by the flags is provided via [`[profile]`](http://doc.crates.io/manifest.html#the-profile-sections) section in the manifest. – Vladimir Matveev Jun 10 '16 at 14:52
  • 1
    Ah... It was 2 years ago. The times when Rust had classes and garbage collector as I recall))) I mean... Rust concepts where changing rapidly before 1.0 – MajesticRa Jun 10 '16 at 15:51