Page 1 of 2

CVS-help

Posted: 11.10.2002, 07:31
by Guest
To CWeissbrod (or others!) :
minor point
Where are the new icons *.bmp introduced 2 weeks ago in the ressource. At least theyare not in my version of MSDEV

To Fridger :
More important for me
I would really try the CVS linux 125 version. The "configure" file is missing, How to create such file,
the one associated with celestia 124 does not fit.
Thank
MB

Posted: 11.10.2002, 17:18
by Christophe
To create the configure script you need to do:

Code: Select all

> aclocal -I macros
> autoheader
> automake
> autoconf

Posted: 13.10.2002, 14:41
by Guest
Merci Christophe, Ca ne marche tout de meme pas
Voici le code

[root@localhost celestia]# aclocal -I macros
[root@localhost celestia]# autoheader
configure.in:216: warning: AC_TRY_RUN called without default to allow cross compiling
[root@localhost celestia]# automake
automake: Makefile.am: required file `./INSTALL' not found
automake: Makefile.am: required file `./NEWS' not found
automake: Makefile.am: required file `./README' not found
automake: Makefile.am: required file `./COPYING' not found
automake: Makefile.am: required file `./AUTHORS' not found
[root@localhost celestia]# autoconf
configure.in:216: warning: AC_TRY_RUN called without default to allow cross compiling
[root@localhost celestia]# ./configure
loading cache ./config.cache
: command not found
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
: command not found
: command not found
: command not found
: command not found
'/configure: line 1595: syntax error near unexpected token `do
'/configure: line 1595: ` do
[root@localhost celestia]#

MB

Posted: 13.10.2002, 23:27
by Christophe
Apparemment il y a un vieux fichier de cache qui traine...
rm -f config.cache

Et essaye aussi de faire un automake -a, ?a supprimera les erreurs sur les fichiers manquants.

Posted: 18.10.2002, 06:44
by MB
To Christophe and Fridger:
I tried again to create the configure with autoheader as both of you indicate to me.
I previously suppressed th "old" configure and config.cache (actually it was empty. )
I got the same results as above. I tried to identify the version : automake 1.4 , autoconf v2???
I then decided to check these tools on celestia 124 for which I have the configure script from the
downloaded .tar.gz package. I suppressed this configure script and success! I can with your commnd lines
succesfully create the correct 124 configure. This seems to indicate that I have the good tools
Is the CVS version different?
Thanks
MB

Posted: 19.10.2002, 08:22
by Christophe
MB wrote:This seems to indicate that I have the good tools Is the CVS version different?


No, you should be able to build the CVS version using automake 1.4 and autoconf 2.13. There's probably something wrong with your installation, what distribution are you using and what's in the config.log file?

Posted: 21.10.2002, 06:27
by MB
Christophe,
I use Mandrake 8.1. I will look at the config.log this evening at home. I have not the information here, at work. However I look at it and did not found any information. May be I have one of the file ( as e.g. configure.in) corrupted?
MB

Posted: 21.10.2002, 06:31
by MB
Christophe
I forgot, another information. My CVS link is made through "Windows" because we use it at work. May be a problem of LF-CR?
MB

Posted: 21.10.2002, 19:41
by t00fri
MB wrote:Christophe
I forgot, another information. My CVS link is made through "Windows" because we use it at work. May be a problem of LF-CR?
MB


MB:

In any case, I do a CVS update whenever there is something new, i.e. often every few days under a well installed and reasonably modern Linux. With the commands Christophe and I told you, the compilation proceeds usually without the slightest problems.

Your particular problems must be due to your installation which, unfortunately, we do not see as a whole and thus can hardly judge...

I do not have the slightest idea how well CVS works under Windows and how well it is compatible with the UNIX one. Since as scientists, we largely operate with tax payer's money, we avoid commercial software and notably commercial compilers unless it is unavoidable...

Good luck,

Bye Fridger

Posted: 22.10.2002, 15:02
by MB
To Christophe
Here is my config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:598: checking for a BSD compatible install
configure:651: checking whether build environment is sane
configure:708: checking whether make sets ${MAKE}
configure:754: checking for working aclocal
configure:767: checking for working autoconf
configure:780: checking for working automake
configure:793: checking for working autoheader
configure:806: checking for working makeinfo

nothing else!!


To Fridger

As I already told you I fully agree with your philosophy. I also am a scientist. Unfortunately our lab and more than 50% of the french lab, as far as I know , still use Windows. I dont yet have enough time, power and knowledge to persue our hierarchy to switch to
linux.
Coming back to my problem, I don't think it is a question of installation, I don't have any problem with compilation of celestia under linux.
I will look again when time permits
T one of you:
Can you send me a copy of the celestia125 files (as config.in etc) necessary to build the configure file. This can help me to find the problem. Thank you . My adress
barat@lcam.u-psud.fr
Bye
MB

Posted: 22.10.2002, 19:24
by Christophe
I've packaged the current cvs version in a tarball (including the configure script).

You can get it here.

That should solve your problem.

Posted: 23.10.2002, 06:39
by MB
Thanks a lot, Christophe, I will try to compile that this evening, and also compare with my files to find the root of my problem.
MB.

Posted: 24.10.2002, 14:22
by MB
Christophe:
J'ai honte, donc c'est en Francais!
Je n'arrive pas ? d?zipper le fichier. Ni via l'archivage "automatique de Mandrake, ni en console. Certes je n'ai pas l'habitude des .tgz. J'ai beau lire le man tar, J'ai beau consulter mes collegues UNIX, J'ai essay? plusieures fois de telecharger si mauvais chargement c'est tres rapide pour moi,mais pas de succes : il cr? un dossier vide + 1 fichier .h!!
D?sol? de redemander de l'aide.
Merci
MB

Posted: 24.10.2002, 17:31
by Christophe
tar xvzf celestia-1.2.5-cvs20021022.tgz

x - extract
v - verbose (liste les fichiers extraits)
z - le fichier est compress? avec gzip
f - les donn?es sont dans le fichier

J'ai v?rifi?, le fichier est bon.

Bonne chance !

Posted: 28.10.2002, 09:17
by MB
Christophe:
I was away for two days, the reason of my late reply. Back, I urgently try your unzip procedure, No succes yet. Actually I was not so surprised since with Mandrake, the console is not required to unzip.
Here is what I got:

root@localhost celestia-cvs]# tar xvzf celestia-1_2_5-cvs20021022.tgz

gzip: stdin: not in gzip format
tar: Le processus enfant a retourn? le statut 1
tar: Statut d'erreur report? d'erreurs pr?c?dentes.

So??? Of course I use windows for the fast internet connection available in my working place. I already has some Pb with the _ and . But I checked that it is not the case here.

BTW I found in another place of this forum that another guy had similar problems with CVS. I still don't understand why the configure file is not include in the cvs. I repeat, I never had any problem with the celestia .gz package.
Thank again
MB

Posted: 28.10.2002, 18:20
by selden
MB,

If you used Microsoft Internet Explorer to download the .tgz file,
then MSIE automatically expanded the file but did not properly change the name. I just downloaded the file now and that's what it did for me.

If that is what happened, you can rename the downloaded file to be celestia-1.2.5-cvs20021022.tar and then use tar to extract the files. By default, tar will create the files in a subdirectory named celestia, so be sure to extract the files into a folder that does not already contain that directory.

I hope this helps.

Posted: 29.10.2002, 09:24
by Guest
Selden and others
Your suggestion did not work either:
I got the same answer : one file is untar + one empty folder :celestia.
BUT, finally I got a net connection through Linux and I download again the file. As expected no problem to extract the files.
Just one strange stuff : the lenght of the download file:
21468k with windows
14200k with Linux !!??
So I hope my problems with Linux ended.
MB

Posted: 29.10.2002, 09:29
by MB
Small Pb, Previous message sent with Linux, I am registered under Windows!
MB

Posted: 29.10.2002, 21:20
by selden
MB,

For what it's worth, after downloading Christophe's .tgz using Internet Explorer v6.0 sp1 under Windows NT4 and renaming the result to be .tar, here is what is reported under Cygwin (the free Unix environment for Windows):

$ ls -l *.tar
-rwxrwxrwx 1 seb 512 21739520 Oct 28 13:09 celestia-1.2.5-cvs20021022.tar
$ cksum celestia-1.2.5-cvs20021022.tar
3557760634 21739520 celestia-1.2.5-cvs20021022.tar

If your copy of the file has a different size or checksum, then it didn't get downloaded properly.

Posted: 29.10.2002, 22:41
by t00fri
Anonymous wrote:Selden and others
Your suggestion did not work either:
I got the same answer : one file is untar + one empty folder :celestia.
BUT, finally I got a net connection through Linux and I download again the file. As expected no problem to extract the files.
Just one strange stuff : the lenght of the download file:
21468k with windows
14200k with Linux !!??
So I hope my problems with Linux ended.
MB


MB: I really have trouble following that discussion. If in doubt about the actual file type, it is trivial to find out. Just inspect the 'magic number' with an editor. If you are unexperienced and do not know these numbers by heart, use
the command 'file <file>' and it tells you the file type independent of the file's ending.

This is elementary UNIX wisdom indeed...

Bye Fridger