Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Fixing Allegro CL 3.1.20 to work under NS 3.0

4 views
Skip to first unread message

Bill Vrotney

unread,
Oct 9, 1992, 12:27:38 AM10/9/92
to

I though it was going to take me longer to get a method out for doing this
but the ucl.o file that I had was not the Franz patched file, so it is
actually pretty simple as long as you update to the Franz patched ucl.o.

The following is a procedure for fixing Allegro CL 3.1.20 so that it works
under NeXTstep 3.0. I don't have 3.0 so I need someone to try this out and
report back to this news group.

Warning!!! (from Franz) This procedure results in creating a new ucl.o
binary file. You may distribute this method but not the resulting ucl.o
file.

You should find all of the files mentioned here on your ACL distribution
floppies. If you do not have the Franz patch mentioned below you will
have to ask Franz for it.

1. You need to patch your existing ucl.o file, if it is not
already patched, with an existing patch from Franz. This is
done with an existing shell script called

install_patch.sh

and an existing patch file called

patch.uu

To verify that you have done the right thing, after this patch
is installed the ucl.o file should be 612364 bytes.

2. Then you edit the binary file in emacs and save the results.
You are going to edit your existing ucl.o file so that you might
want to save the existing ucl.o to ucl.orig.o. Then run emacs
and do:

find-file ucl.o
replace-string _rld _jld
replace-string __bcopy _bcopy^@
save-buffer

The ^@ above is the null character (000 byte) and can be
entered in emacs using

C-q C-<space>

and will look in an emacs buffer as a single character ^@
and NOT two characters.


3. You then reinstall ACL as usual.

--
Bill Vrotney
BAH/Advanced Decision Systems

Bill Vrotney

unread,
Oct 9, 1992, 7:15:47 AM10/9/92
to

I am reposting some of this for clarification:

> I though it was going to take me longer to get a method out for doing this
> but the ucl.o file that I had was not the Franz patched file, so it is
> actually pretty simple as long as you update to the Franz patched ucl.o.
>
> The following is a procedure for fixing Allegro CL 3.1.20 so that it works
> under NeXTstep 3.0. I don't have 3.0 so I need someone to try this out and
> report back to this news group.
>
> Warning!!! (from Franz) This procedure results in creating a new ucl.o
> binary file. You may distribute this method but not the resulting ucl.o
> file.
>
> You should find all of the files mentioned here on your ACL distribution
> floppies. If you do not have the Franz patch mentioned below you will
> have to ask Franz for it.
>
> 1. You need to patch your existing ucl.o file, if it is not
> already patched, with an existing patch from Franz. This is
> done with an existing shell script called
>
> install_patch.sh
>
> and an existing patch file called
>
> patch.uu
>
> To verify that you have done the right thing, after this patch
> is installed the ucl.o file should be 612364 bytes.

For step (1.), I believe for most of you if you go to your distribution
directory called ACL there is a file called

dumplispPatch

this is a shell archive file and if you follow the instructions there you
should get the same results, ie. a new ucl.o file resulting in 612364 bytes.
If your existing ucl.o file is already 612364 bytes it probably already had
been patched with the "dump lisp" patch.

Bill Vrotney

unread,
Oct 9, 1992, 6:56:32 PM10/9/92
to

I am reposting and reformulating these instructions for fixing Allegro CL
3.1.20 to work under NeXTstep 3.0. Since my original posting some people
have tried and succeeded to get a running ACL under 3.0 but only after
including some fixes for the dsp library references that I include below
(thanks people and thanks to the originators of the emacs hack that wish to
remain anonymous). I also clarify the "dump lisp" patch.

The following is a procedure for fixing Allegro CL 3.1.20 so that it works

under NeXTstep 3.0. You should find all of the files mentioned here on your
ACL distribution. We refer to the top level directory of this distribution
as ACL/ and the build directory ACL/build.

Warning!!! (from Franz) This procedure results in creating a new ucl.o
binary file. You may distribute this method but not the resulting ucl.o
file.

1. First look at the byte size of the file ACL/build/ucl.o, if the size
is 612364 bytes then skip to step 2. Otherwise look at the file
ACL/dumplispPatch. This is a shell archive that will patch ucl.o with
the "dump lisp" patch. More precisely

cd ACL
cp dumplispPatch build
cd build
/bin/sh dumplispPatch
/bin/sh install_patch.sh

Now ucl.o should be 612364 bytes long. (the original ucl.o will be
saved in a file called ucl_orig.o).

2. Next edit the file ACL/build/config (you might want to save the orginal
config file). In that file you will see two statements:

LIBRARIES = -lNeXT_s -ldsp_s -lsys_s
USYMS = -u libsys_s -u libNeXT_s -u libdsp_s

In the LIBRARIES statement, change -ldsp_s to -ldsp
In the USYMS statement, delete the -u libdsp_s


3. Next you edit the new binary file ACL/build/ucl.o in emacs and
save the results. Go to ACL/build directory, run emacs and

find-file ucl.o
replace-string _rld _jld
replace-string __bcopy _bcopy^@
save-buffer

The ^@ above is the null character (000 byte) and can be
entered in emacs using

C-q C-<space>

and will look in an emacs buffer as a single character ^@
and NOT two characters.


4. Finally reinstall ACL as usual. You do this by going to the
ACL/build directory and

/bin/sh config

0 new messages