From: "Lluís Batlle" <viriketo@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] opera under linuxemu
Date: Thu, 3 Jan 2008 11:54:27 +0100 [thread overview]
Message-ID: <45219fb00801030254y72b5ac1fjd5100c4dd6888e4c@mail.gmail.com> (raw)
In-Reply-To: <20080103083708.GA826@shodan.homeunix.net>
I agree on this.
On the other hand, I seem to remember that any program using the
glibc's network name resolver can be totally statically linked in
Linux.
That has probably something to do with those dynamic /lib/libnss*
modules for name resolution, specified in /etc/nsswitch.conf.
Maybe a special compilation of glibc with those modules in static form
can produce static binaries, but I don't think any distribution comes
with a precompiled glibc like that.
2008/1/3, Martin Neubauer <m.ne@gmx.net>:
> For one, I think opera-static doesn't mean it's a static binary but qt is
> linked in statically. On the other hand, until just a couple years ago
> static linking in linux was no problem at all. But around the time linux 2.6
> came out, the glibc guys apparently decided nobody used static linking
> anyway and merrily bollocksed it up. Great, now I'm depressed.
>
> * Federico G. Benavento (benavento@gmail.com) wrote:
> > hola,
> >
> > getting real static binaries in linux is a bit tricky and no one seems to
> > be doing so, they always need ld-linux.so, libnss and others.
> > cinap creates some kind of bundles that create a fake ns in /tmp/$lbun
> > with this (http://9hal.ath.cx/usr/cinap_lenrek/lbun/mklbun) or something
> > like, but I know he got opera running in Plan 9.
> > http://9hal.ath.cx/usr/cinap_lenrek/plan9opera.png
>
next prev parent reply other threads:[~2008-01-03 10:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 0:55 ron minnich
2008-01-03 2:54 ` Iruata Souza
2008-01-03 3:29 ` Federico G. Benavento
2008-01-03 3:39 ` John Floren
2008-01-03 3:58 ` Federico G. Benavento
2008-01-03 4:03 ` Uriel
2008-01-03 4:02 ` Uriel
2008-01-03 5:26 ` ron minnich
2008-01-03 7:45 ` Uriel
2008-01-03 22:12 ` cinap_lenrek
2008-01-03 22:24 ` John Floren
2008-01-03 22:43 ` Francisco J Ballesteros
2008-01-03 22:50 ` [9fans] contrib(1) (was: opera under linuxemu) Federico G. Benavento
2008-01-03 23:09 ` Pietro Gagliardi
2008-01-03 23:22 ` Federico G. Benavento
2008-01-03 23:39 ` Pietro Gagliardi
2008-01-04 4:08 ` marina
2008-01-03 23:26 ` Federico G. Benavento
2008-01-04 4:28 ` marina
2008-01-03 23:08 ` [9fans] opera under linuxemu cinap_lenrek
2008-01-03 8:37 ` Martin Neubauer
2008-01-03 10:54 ` Lluís Batlle [this message]
2008-01-03 10:55 ` Lluís Batlle
2008-01-03 21:07 ` csant
2008-01-04 2:34 Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45219fb00801030254y72b5ac1fjd5100c4dd6888e4c@mail.gmail.com \
--to=viriketo@gmail.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).