Opened 14 years ago
Closed 12 years ago
#46 closed Feature Wish (fixed)
Some way of supporting static compilation
| Reported by: | Dirkjan Ochtman | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | beta 2.3 |
| Component: | Building / Compiling | Version: | OpenVPN 2.1.0 / 2.1.1 (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
| Cc: |
Description
In Gentoo, we support static compilation using a USE flag that essentially translates to running sed -i -e '/^LIBS/s/LIBS = /LIBS = -static /' Makefile. It would be nice if there was some supported way of doing this right, as apparently the current approach has some problems.
Change History (4)
comment:1 Changed 14 years ago by
comment:4 Changed 12 years ago by
| Milestone: | → beta 2.3 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
I presume this has been fixed in 2.3-alpha2, as the whole build tool chain was revamped from alpha1 to alpha2.
Please re-open if this is not the case.
Note: See
TracTickets for help on using
tickets.
We discussed this issue on yesterday's IRC meeting. We tried to build a statically linked OpenVPN binary on a Ubuntu 9.10 and Gentoo boxes (from tarball/git repo) and failed. That said, it _should_ be relatively(?) easy to allow building of static binaries by editing the autoconf files.
However, first we'd like to understand why you need a static binary in Gentoo? Isn't this something that can be controlled with USE flags?