[Xastir] install question

[Rob Neece]

Thanks again, Curt.  I started this update before i saw your second 
message, so that info is not below.  I will try again to get the latest 
version, and the gcc problems still seem to be a sticking point (see below).

Rob


Update -- the gcc problem was nagging me, so I reinstalled it.  Possibly 
there was a problem with dependencies that got resolved, but gcc is now 
at /usr/bin/gcc.  The results of ./configure are now different:

[rtn at hawk xastir]$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes

Configuring xastir 1.9.9

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.

Excerpt from config.log:

Thread model: posix
gcc version 4.3.2 (Debian 4.3.2-1.1)
configure:2747: $? = 0
configure:2754: gcc -V >&5
gcc: '-V' option must have argument
configure:2757: $? = 1
configure:2780: checking for C compiler default output file name
configure:2807: gcc    conftest.c  >&5
/usr/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
configure:2810: $? = 1
configure:2848: result:
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME "xastir"
| #define PACKAGE_TARNAME "xastir"
| #define PACKAGE_VERSION "1.9.9"
| #define PACKAGE_STRING "xastir 1.9.9"
| #define PACKAGE_BUGREPORT "xastir at xastir.org"
| #define PACKAGE "xastir"
| #define VERSION "1.9.9"
| #define XASTIR_TOCALL "APX199"
| #define _GNU_SOURCE 1
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:2855: error: C compiler cannot create executables
See `config.log' for more details.

Rob


Rob Neece wrote:
> Thanks for the help, Curt.  Based on your advice, I'm trying to use 
> cvs to install the release version, which should be 2.0.1.
>
> Unfortunately my wheels are spinning.  Here is the situation.
>
> The xastir directory is at ~/src/xastir, and .xastir is at ~/.xastir.
>
> less .cvsrc provides:
> cvs -z3
> update -P -d
> status -v
> diff -u
>
> Update attempt:
> cd ~/src/xastir
> cvs -d:pserver:anonymous at xastir.cvs.sourceforge.net:/cvsroot/xastir co 
> -r RELEASE xastir
> cd xastir
> cvs update
> ./bootstrap.sh
> ./configure
> (make clean;make -j3 2>&1) | tee make.log
> su
> make install
> exit
> xastir
>
> Things start to go wrong at ./configure, which goes like this:
>
> [rtn at hawk xastir]$ ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
>
> Configuring xastir 1.9.9
>
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for gcc... no
> checking for cc... no
> checking for cl.exe... no
> configure: error: no acceptable C compiler found in $PATH
> See `config.log' for more details.
>
> The first question is why didn't cvs pull down version 2.0.1?  The 
> second question is why is gcc not being found, since I just installed 
> it with synaptic?  I may have messed up earlier in the process, and 
> these questions are irrelevant.
>
> Thanks for your help,
> Rob
>
> Curt, WE7U wrote:
>> On Sat, 1 Jan 2011, Rob Neece wrote:
>>
>>> Version 1.9.9 was installed under the previous OS, so I still have 
>>> the .xastir directory structure in my home directory associated with 
>>> that. Question 1 is can I keep .xastir and just proceed to install?
>>
>> Yes.  Assuming that you're not going to change the install location
>> of the Xastir executables from what you had before.  If you
>> installed from a packaged binary before, the package maintainers
>> might have decided to change the install directory on you.
>>
>>
>>> Assuming that will work, should I install 1.9.9 or just go for the 
>>> latest version on CVS?
>>
>> You'd be best served by downloading the 2.0.0 release from
>> Sourceforge and compiling that, or building from the latest CVS
>> which will give you 2.0.1.  We were in the middle of OpenStreetMaps
>> integration during the 1.9.9 timeframe, so by snagging 2.0.0 or
>> later you'll have all the bug-fixes and efficiencies that the latest
>> code gives you for OpenStreetMaps.
>>
> _______________________________________________
> Xastir mailing list
> Xastir at lists.xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
>