Return to BSD News archive
Newsgroups: comp.os.386bsd.apps
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!mcsun!Germany.EU.net!cat-ufg.de!root
From: wiserner@informatik.tu-muenchen.de
Subject: misc apps available for NetBSD ( with sharedlibs)
Message-ID: <CEA7K6.79r@cat-ufg.de>
Sender: root@cat-ufg.de (Charlie Root)
Nntp-Posting-Host: blurps
Organization: TU-Muenchen
Date: Sat, 2 Oct 1993 18:04:54 GMT
Lines: 200
Hi all.
I compiled misc apps for NetBSD with shared-libs.
I used Dr.Joerg Lohse's shared-libs .
( Please no war on these,I know Sun-style shared-libs are better ...)
I have the following items :
shared-libs-package :
- libs : libX11 libXmu libXt libXext libxview libc
- crt0_s.o : modified crt0.o capable of loading the libs.
- gcc : gcc capable of making shared-executables.
usr.bin-package :
- everything in /usr/bin compiled with shared-libs +
gdb 4.10,tcsh,kermiti,term ( runs multiple sessions over
one Modem-Line ) ( also compiled with shared-libs. )
( tn3270 is missing ... )
some files are not built with shared-libs ( gzip,tar ... )
for allowing you to unpack your distribution if something
goes wrong ..., and some files aren't compiled with
shared-libs ( gcc ... because they use almost nothing
from libc. )
usr.X386.bin-package:
-"standard" : most X11-apps (xterm,xconsole,twm,xload,xclock
... )compiled with shared-libs.
( some are missing, so you must keep some of the old ones. )
-window- : tvtwm,olvwm ( including olvwmslave, textedit and props ),
managers fvwm ( Try it out it's real nice and saves lots of mem )
-rxvt-stuff : rxvt ( xterm-replacement, saves mem. ),rclock
-xxgdb : X-frontend for gdb ( works with 3.5 and 4.10 )
Stability :
- libs : They are working quite well as long as you don't acess
symbols from the common data-segment. ( The linker doesn't
find them. ( I hacked some libs ( libc,libX11,libxview ))
to move the symbols into the data-segment, but it wasn't
always possible.)( Hmm.. the better way would be to
the shared-lib-loader. Maybe the Jolitzs have done it?! )
: libXaw. there is a libXaw but it doesn't work, so I won't
supply it.
: You can't analyse a core dumped by an shared binary
because gdb doesn't know anything about the extra address-
space .. ( You will have to actually run the binaries to
debug it.)
- usr.bin-package.
: I use this stuff since last year and no problems so far.
: The gdb is verry new and if there are bugs blame them on
me and not on the peoble from the gdb-staff. This is only
an interims-solution,get gdb 4.11 when it's ready , it has
NetBSD 0.9 support builtin.
: The term-package works only in sevenbit-mode. Don't know
why.
- usr.X386.bin, wmgrs
: The binaries work ( using them since ~ 2 month. )
:fvwm has a small bug when setting auto-raise to True. (
popups disappearing sometimes. ) else everything Ok.
:olvwm crashes the X-server in some rare-cases.
:tvtwm is Ok.
:rxvt : The terminal works ( I changed some ioctl's .. )
but ^u in vi doesn't work ?! . Job control is available.
I use a few rxvt's for commands and one X-Term for editing.
- the source for building the whole stuff ..
Why use them ?
- less disk-space needed.
( usr.bin = ~4 Mb w/o gdb,kermit ,xterm = 126 kb,xload = 24 kb. etc.)
- less memory used.
I can run a system with all the normal daemons + nfs + X + 2 xterms +
xload + fvwm + xload + xclock + 2 tcsh's in 8 Mb w/ swapping ..
- link-time decreases tremendously. ( only a few seconds for an x-app )
problems at link-time :
- the shared-libraries have dependencies on eachother.
Because of that you can't use eg libX11-shared and libc not shared.
- the shared libs must be fully resolved so that one can't build
libraries with cross-references or symbols with the same name.
- There is no program like "ldd" use : strings "programname" | grep shlib
HOWEVER NO WARRANTY !
So if you are interested in some/all of this stuff drop me a Mail so I can
find a place on some ftp-server to put it on , and write an README-file.
If you are not interested please excuse the blurb ...
BTW I also have a Motif1.2-shared-lib,and mwm ..
( Of course I can't put it on a ftp-server,but I can give you some
hints about building one. )
mfg B.Wiserner
Newsgroups: comp.os.386bsd.apps
Sender: root@cat-ufg.de (Charlie Root)
From: wiserner@informatik.tu-muenchen.de
Path: root
Distribution: world
Followup-To:
Organization: TU-Muenchen
Subject:misc available apps for NetBSD ( with sharedlibs)
Keywords:
Hi all.
I compiled misc apps for NetBSD with shared-libs.
I used Dr.Joerg Lohse's shared-libs .
( Please no war on these,I know Sun-style shared-libs are better ...)
I have the following items :
shared-libs-package :
- libs : libX11 libXmu libXt libXext libxview libc
- crt0_s.o : modified crt0.o capable of loading the libs.
- gcc : gcc capable of making shared-executables.
usr.bin-package :
- everything in /usr/bin compiled with shared-libs +
gdb 4.10,tcsh,kermiti,term ( runs multiple sessions over
one Modem-Line ) ( also compiled with shared-libs. )
( tn3270 is missing ... )
usr.X386.bin-package:
-"standard" : most X11-apps (xterm,xconsole,twm,xload,xclock
... )compiled with shared-libs.
( some are missing, so i must keep the old ones. )
-games : some game-stuff ( xmris , xsol, xmahjongg,xmines )
-window- : tvtwm,olvwm ( including olvwmslave and props ),
managers fvwm ( Try it out it's real nice and saves lot's of mem )
-rxvt-stuff : rxvt ( xterm-replacement, saves mem. ),rclock
-xxgdb : X-frontend for gdb ( works with 3.5 and 4.10 )
Stability :
- libs : They are working quite well as long as you don't acess
symbols from the common data-segment. ( The linker doesn't
find them. ( I hacked some libs ( libc,libX11,libxview ))
to move the symbols into the data-segment, but it wasn't
always possible.)
: Good link-times. e.g. 3 sec. linking for xload.
: Becaiuse of an old bug I changed some code in gcrt0_s.o so
that you must chmod 777 all shared-libs ( Yuck ?! )
This is a major security-hole but I didn't care at home.
I will fix this in about one-two weeks.
: You can't analyse a core dumped by an shared-lib binary
because gdb doesn't know anything about the extra address-
space .. ( You will have to actually run the binaries to
debug it.)
- usr.bin-package.
: I use this stuff since ~2 month and no problems so far.
: The gdb is verry new and if there are bugs blame them on
me and not on the peoble from the gdb-staff.
: The term-package works only in sevenbit-mode. Don't know
why.
- usr.X386.bin
: The binaries work ( using them since ~ 2 month. )
:fvwm has a small bug when setting auto-raise to True. (
popups disappearing sometimes. ) else everything Ok.
:olvwm crashes the X-server in some rare-cases.
:tvtwm is Ok.
:rxvt : The terminal works ( I changed some ioctl's .. )
but ^u in vi doesn't work ?! . Job control is available.
I use a few rxvt's for commands and one X-Term for editing.
:games ? I played xmahjongg a few times .. it worked.
Why use them ?
- less disk-space needed.
( usr.bin = ~4 Mb w/o gdb,kermit ,xterm = 126 kb,xload = 24 kb. etc.)
- less memory used.
I can run a system with all the normal daemons + nfs + X + 2 xterms +
xload + fvwm + xload + xclock + 2 tcsh's in 8 Mb w/ swapping ..
- link-time decreases tremendously. ( only a few seconds for an x-app )
HOWEVER NO WARRANTY !
So if you are interested in some/all of this stuff drop me a Mail so I can
find a place on some ftp-server to put it on , and write an README-file.
If you are not interested please excuse the blurb ...
BTW I also have a Motif1.2-shared-lib,and mwm ..
( Of course I can't put it on a ftp-server,but I can give you some
hints about building one. )
mfg B.Wiserner
Keywords: