Re: [AD] 4.0.2 releasei/CVS

["Eric Botcazou" <ebotcazou@xxxxxxxxxx>]

> Ok, I tried building the CVS version of Allegro under Solaris (version
> number is indeed 8, btw), assuming the patches went there.

Two remarks:
- you checked out the CVS trunk, while the 4.0.2 release will be made from
the allegro_4_0_branch branch,
- the Unix über-patch has not yet been installed.

> I still get a few grep error messages when running configure, but these
> don't appear to disrupt things. I also think there is some confusion with
> identifying make (make != gmake), but this doesn't seem to be a problem.

Nothing is corrected at all.

> Conterary to 4.0.2 RC1 though, I cannot build the library! I get the
> following:
>
> (eglebbk@xxxxxxxxxx) eglebbk/Program/alleg-cvs/allegro>gmake
> rm -f lib/unix/liballeg.a
> ld -r -keep_private_externs -o lib/unix/liballeg.a
> obj/unix/alleg/allegro.o
> ... [snip list of object files] ...
> ld: illegal option -- k
>
> The RC1 used ar instead of ld, which works fine (double checked).

These are results of the Darwin changes: 'ld -r -keep_private_externs' is a
Darwin pattern, which isn't supposed to be used elsewhere. The culprit is
again a 'grep -q' invocation, in aclocal.m4:

@@ -469,3 +469,20 @@
 fi
 ])
 AC_MSG_RESULT($allegro_cv_support_fomit_frame_pointer)])
+
+dnl
+dnl Test for custom Darwin library archiver.
+dnl
+dnl Variables:
+dnl  allegro_cv_support_ar
+dnl
+AC_DEFUN(ALLEGRO_ACTEST_AR_SUPPORT,
+[AC_MSG_CHECKING(whether GNU ar is installed)
+AC_CACHE_VAL(allegro_cv_support_ar,
+[if ar -V | grep -q 'GNU'; then
+  allegro_cv_support_ar=yes
+else
+  allegro_cv_support_ar=no
+fi
+])
+AC_MSG_RESULT($allegro_cv_support_ar)])

Try this line instead:
+[if ar -V | grep -i "gnu" >/dev/null; then

> On a side note, would it be possible to have the TARGET_ARCH_EXCL and
> TARGET_ARCH_COMPAT flags do anything on Unix? I'd like to see how Allegro
> performs if I tell gcc to optimize for Sparc.

Yes, I think we could add these options on Unix too.

--
Eric Botcazou
ebotcazou@xxxxxxxxxx