Opened 13 years ago
Closed 13 years ago
#3021 closed Enhancement (invalid)
Statically linked version
| Reported by: | raster | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | None Set |
| Component: | Transmission | Version: | 1.91 |
| Severity: | Normal | Keywords: | |
| Cc: |
Description
I'm maintaining a version of Transmission specific for the Multimedia hard disk MemUp? LX (with a MipsEL processor). Since I had problems to compile things using the native buildchain (cross compiling), I'm compiling locally the binaries; and to avoid problems with libraries, I'm compiling it statically linked.
To do this, I have to manually link the code, which is always hard to do. Is possible to add an option to CONFIGURE to compile all the binaries statically linked?
Change History (1)
comment:1 Changed 13 years ago by charles
- Resolution set to invalid
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
In general most maintainers are pushing Transmission in the other direction, to eliminate static linking (such as our bundling of libevent) due to security issues. (See: http://people.redhat.com/drepper/no_static_linking.html)
If you want to come up with an autoconf/automake patch for this I'd take a look at it, but it's not something I'm going to spend much time working on.