Celestia Forums

Celestia users who build the svn version of Celestia may want to try to build the new svn version. There had been some changes to the admin folder that may break building Celestia on some build systems. Probably newer build systems. The more who get involved in this now may be better for most Linux users in the future.

I can build with my older system, openSuse 10.2 (autoreconf (GNU Autoconf) 2.60) but as of 4589, openSuse 11.1 and (autoreconf (GNU Autoconf) 2.63), it doesn't.
Also building with "make -f Makefile.cvs" probably will not work anymore.
I suggest saving a copy of your old admin folder before running "svn up".
cartrite

OpenSuse 11.1 has a package called gettext-runtime. If that is installed, there is an admin folder in /usr/share/doc/packages/gettext-runtime/examples/hello-c++-kde.
There are also similar files to the original admin files in /usr/share/libtool/config.
So I am able to use the admin folder from the gettext example and I also copy/overwrite these files with the libtool files.
Then I can use acinclude.m4.in from the new admin folder to overwrite the original acinclude.m4 and run autoreconf -vi.
This will reconfigure without many warnings at all. There is a warning about GETTEXT though. It wants an additional statement "AM_GNU_GETTEXT_VERSION" I used "AM_GNU_GETTEXT_VERSION(0.15)". When I use that line, I have to run autoreconf -vif. I guess this might be important for users who use a language other than English and want to use the po files for translations.
cartrite

Steve,

it would be good to communicate your findings also in the dev list, since Pat does NOT read the forum!

Fridger

After I got an email from Pat, I did some further checking and found out that all I had to do was replace acinclude.m4 from the top directory with admin/acinclude.m4.in. It was then renamed to acinclude.m4. This gave me the same good results.
cartrite

After some further research, I found that acinclude.m4 is basically acinclude.m4.in + libtool.m4.
I sent this message to Pat and tried to cc it to the developers list but the message was too big because of the attatchments so I had to cancel it.
Here is what the message said.

Pat,
I compared the 2 files and they are identical until line 6000. Then libtool.m4 is inserted in acinclude.m4. I have a copy libtool.m4.in. /usr/share/doc/packages/gettext-runtime/examples/hello-c++-kde/admin/libtool.m4.in. This is a lot different than the libtool.m4 section in acinclude.m4.

I tried to combine acinclude.m4.in and libtool.m4.in and that failed.

But I took the celestia/macros/libtool.m4 file that was produced during that failed run and I combined that with acinclude.m4.in. This worked. I attached the file so you or others can give it a try. I also attached the patch so you can see what changed.
St

Here is the file
Here is the patch
I get the same results with this file as I did when I used only acinclude.m4.in. I would like to see if this works on other systems. I'm going to try it later on Suse 10.2.
Bummer The acinclude.m4 file above didn't work on Suse 10.2 but using acinclude.m4.in does. Do we really need the libtool.m4 section. This seems to be version dependent. A lot more systems would be compatible if the libtool section is left out.
cartrite