Re: X 3.3-6
On Fri, 3 Oct 1997, joost witteveen wrote:
> > The problems are easy to summarize:
> > - xlib6 version 3.3-6 has a bug in it that causes a lot of programs not to
> > find files under /usr/X11R6/lib/X11/ . xlib6 version 3.3-5 doesn't have
> > this bug.
> > - the rest of the packages don't seem to have any bugs that break other
> > things (of course they do have bugs).
> Not completely true. fvwm2 (at least) has a "-rpath" bug, that makes
> it always search it's X libraries in /usr/X11R6/lib/. This causes
> it to segfault when you install xlibc6 3.3-5 or higher.
Oops. Very true indeed. There is a script, however, which can patch any
binary that has this bug.
--- cut here ---
# Open file
open IN, "$ARGV" or die "can't find $ARGV: $!";
# Read it in one slurp
# Remove this string
print "Replaced: $count occurences in $ARGV\n";
# Write the file
open OUT, ">$ARGV.out" or die "can't write $ARGV.out: $!";
print OUT $file;
--- cut here ---
This produces a copy of every file with '.out' appended to the file name.
The script should say it has replaced 1 occurence for each file that has
this bug. You can `mv' the .out files to the original names , `chmod
+x' them and you're ready to go.
Note that in the case of fvwm(2|95), you also have to patch all the
modules that are in /usr/X11R6/lib/X11/fvwm(2|95). I am not sure about the
exact directory names (I have only fvwm2), but you get the idea.
 I mostly use quite long command lines to do this for all files at
once, for example in the fvwm-modules directory:
# for i in Fvwm* ; do xlibsbug $i ; mv $i $i.bug ; mv $i.out $i ; chmod -x $i.bug ; chmod +x $i ; done
Of course you can also just `rm' the .bug files but I like to play it safe
"Very funny, Scotty. Now beam up my clothes."
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .
- Re: X 3.3-6
- From: email@example.com (joost witteveen)