| Summary: | pkg-config tweaks for cross-compiling | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Colin Watson <cjwatson> | ||||
| Component: | Build system | Assignee: | Assigned to nobody <unassigned-bugs> | ||||
| Status: | CLOSED FIXED | ||||||
| Severity: | enhancement | CC: | djm, dtucker | ||||
| Priority: | P2 | ||||||
| Version: | 5.9p1 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 1986 | ||||||
| Attachments: |
|
||||||
applied, thanks. it will be in the next release. Close all resolved bugs after 7.3p1 release |
Created attachment 2142 [details] Allow using a cross-architecture pkg-config When cross-compiling OpenSSH, it's useful to be able to use a cross pkg-config which is configured to return information for the architecture you're building for rather than the architecture you're building on. The standard convention for this is to call it HOST-pkg-config, e.g. "arm-linux-gnueabi-pkg-config", just as is normally done for cross-compilers. This implies that configure.ac should use AC_PATH_TOOL rather than AC_PATH_PROG. (Compare with pkg.m4 shipped by pkg-config itself, which uses AC_PATH_TOOL.) contrib/Makefile has a similar issue, but this file isn't generated by autoconf. Perhaps it should be, but in the meantime a simple non-intrusive change is to make pkg-config a variable so that it can be overridden by the caller. With these two changes, I've been able to cross-compile the Debian openssh package from x86-64 to ARM.