Created attachment 329960 [details, diff] Patch for screen-4.0.3-r6.ebuild to add the static USE flag. Hello, I often need screen (or tmux) on machines where I don't have root access. Having a static build of screen might be very useful so I wrote a patch for the ebuild. I don't know if it's a good idea to have this in Portage, take a look at the patch and let me know what you think. If it looks good I can do the same for tmux and the other available screen's ebuilds. The only problem is that when I build the static tmux/screen I get these warnings, but as long we're using the same glibc version shouldn't be a problem. screen.o: In function `main': screen.c:(.text+0x302e): warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking screen.c:(.text+0x305f): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking screen.c:(.text+0x2a22): warning: Using 'getspnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking screen.c:(.text+0x2a58): warning: Using 'endspent' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking teln.o: In function `TelConnect': teln.c:(.text+0x428): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
Could you please approach upstream to make the buildsystem properly supporting static builds? As long as we have the fall outs which you described I don't see a chance to bring this into the repo.
Closing as UPSTREAM as per previous comment.
