Opened 12 years ago
Last modified 12 years ago
#35443 closed defect
py25-pynifti, py26-pynifti: ld: unknown option: --no-undefined — at Version 1
| Reported by: | ns358@… | Owned by: | jameskyle@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.2 |
| Keywords: | Cc: | ||
| Port: | py25-pynifti, py26-pynifti |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Failure to install.
I've tried
sudo port install py26-pynifti configure.compiler=llvm-gcc-4.2 sudo port install py26-pynifti configure.compiler=apple-gcc-4.2 configure.cxx=g++-apple-4.2
and the patch from Ticket #32268 has been applied.
Change History (2)
Changed 12 years ago by ns358@…
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|---|
| Keywords: | clang added |
| Owner: | changed from macports-tickets@… to jameskyle@… |
| Port: | py25-pynifti py26-pynifti added |
| Summary: | py26-pynifti → py25-pynifti, py26-pynifti: ld: unknown option: --no-undefined |
Note: See
TracTickets for help on using
tickets.
Sounds like the project contains a typo: "--no-undefined" should be "-no-undefined" (one leading hyphen, not two). Sounds like that's what #32268 was supposed to have fixed. Maybe there's more than one occurrence of the problem.
Python modules (e.g. py26-pynifti) ignore configure.compiler and instead use the compiler that was used to compile the corresponding python port (e.g. python26) so manually overriding configure.compiler when building a python module has no effect.
Manually adding configure.cxx when setting the compiler to apple-gcc-4.2 has not been necessary since the release of MacPorts 2.0.4; if we still have documentation somewhere saying this is necessary, please let us know where so that we can correct it.