Re: [AD] [molhanec@xxxxxxxxxx: Re: [AL] big problems]

[Eric Botcazou <ebotcazou@xxxxxxxxxx>]

> The following was posted on [AL] (once again). I suggest we add a new
> FAQ entry, in the section Unix problems:

Good idea.

> The wording is probably not perfect, but I think this is worth a FAQ
> entry. It's definitely a question that keeps returning every now and
> then. It may also be worth adding the exact error message to
> build/unix.txt, the current description may be overlooked because the
> error message isn't there. The FAQ could also just point to
> build/unix.txt for the answer.

I chose the latter solution. Here's the patch I commited to trunk and branch.

-- 
Eric Botcazou

Index: docs/build/unix.txt
===================================================================
RCS file: /cvsroot/alleg/allegro/docs/build/unix.txt,v
retrieving revision 1.10
diff -u -r1.10 unix.txt
--- docs/build/unix.txt	7 Feb 2003 18:50:46 -0000	1.10
+++ docs/build/unix.txt	21 Jun 2003 08:03:43 -0000
@@ -35,7 +35,7 @@
 
    Since you are using a Real Operating System, the chances are that you 
    already have all the necessary development tools, at least for compiling 
-   and installing the library. However, you may also need autoconf if you 
+   and installing the library. However, you may also need GNU autoconf if you 
    make any changes that require you to regenerate the configure script.
 
 
@@ -90,15 +90,19 @@
    --enable-static but not --disable-shared, you will get both shared and 
    statically linked versions of Allegro.
 
-   By default, Allegro will probably install into the /usr/local 
-   filesystem. If this hasn't already been set up on your machine, you may 
-   have trouble with programs being unable to find the Allegro shared 
-   library. You can fix this by adding "/usr/local/lib" to your 
-   /etc/ld.so.conf file, and then running ldconfig.
+   By default, Allegro will probably install into the /usr/local filesystem.
+   If this hasn't already been set up on your machine, you may have trouble
+   with programs being unable to find the Allegro shared library. On some
+   Unices (for example Linux), you can fix this by adding "/usr/local/lib" to
+   your /etc/ld.so.conf file and then running 'ldconfig' as root. On others
+   (for example Solaris), you can hardcode the location of the library into
+   the executables by passing "-R/usr/local/lib" to the compiler or linker.
+   Alternatively, you can add the path to your LD_LIBRARY_PATH environment
+   variable.
 
    If you are compiling a CVS version of Allegro, you need to generate the
    configure header and script prior to doing anything else. Make sure that
-   autoconf 2.53 or newer is installed on your system and type:
+   GNU autoconf 2.53 or newer is installed on your system and type:
 
       autoheader   
       autoconf
Index: docs/src/faq._tx
===================================================================
RCS file: /cvsroot/alleg/allegro/docs/src/faq._tx,v
retrieving revision 1.28
diff -u -r1.28 faq._tx
--- docs/src/faq._tx	15 Apr 2003 09:49:44 -0000	1.28
+++ docs/src/faq._tx	21 Jun 2003 08:03:49 -0000
@@ -347,6 +347,13 @@
       Bourne-style shell like bash, try <tt>make 2> logfile.txt</tt>
 
 
+@\   When I try to run Allegro programs, I get "error while loading shared libraries:
+@@   liballeg.so.4.1: cannot open shared object file: No such file or directory".
+
+      You need to teach the dynamic linker where to find the Allegro shared library.
+      See docs/build/unix.txt, near the end of the 'Installing Allegro' section.
+
+
 @\   When I try to use DGA2, I get "resolution not supported", but the
 @@   X server does actually support that resolution !