[GRASS-user] Build Grass62!

Hi to everbody, I have some problems while i am compiling grass-6.2.0 stable
version.....
After having launched the ./configure
--with-cxx \
  --with-gdal=/usr/local/bin/gdal-config \
  --with-postgres-includes=/usr/local/pgsql/include \
--with-postgres-libs=/usr/local/pgsql/lib \
  --without-mysql \
--with-sqlite \
  --with-tcltk-includes=/usr/include/tcl8.4 \
  --without-odbc \
  --with-nls \
  --with-motif \
  --with-motif-includes=/usr/include/Xm \
  --without-glw \
  --with-fftw \
--with-readline \
  --with-freetype --with-freetype-includes=/usr/include/freetype2 \
  --enable-largefile \

with config.log:

GRASS is now configured for: i686-pc-linux-gnu

Source directory: /home/sam/GRASS&QGIS/grass-6.2.0
Build directory: /home/sam/GRASS&QGIS/grass-6.2.0
Installation directory: /usr/local/grass-6.2.0
Startup script in directory: ${exec_prefix}/bin
C compiler: gcc -g -Wall
-Werror-implicit-function-declaration -fno-common
C++ compiler: c++ -g -Wall
FORTRAN compiler:
Building shared libraries: yes
64bit support: no
OpenGL platform: X11

  NVIZ: yes

  BLAS support: no
  C++ support: yes
  DWG support: no
  FFMPEG support: no
  FFTW support: yes
  FreeType support: yes
  GDAL support: yes
  GLw support: no
  JPEG support: yes
  LAPACK support: no
  Large File Support (LFS): yes
  Motif support: yes
  MySQL support: no
  NLS support: yes
  ODBC support: no
  OGR support: yes
  OpenGL support: yes
  PNG support: yes
  PostgreSQL support: yes
  Python support: no
  Readline support: yes
  SQLite support: yes
  Tcl/Tk support: yes
  TIFF support: yes
  X11 support: yes
$ make

I have this error:

sam@debian:~/GRASS&QGIS/grass-6.2.0$ make
mkdir -p /home/sam/GRASS&QGIS/grass-6.2.0/bin.i686-pc-linux-gnu
/bin/sh: QGIS/grass-6.2.0/bin.i686-pc-linux-gnu: No such file or directory
make: *** [/home/sam/GRASS&QGIS/grass-6.2.0/bin.i686-pc-linux-gnu] Error 127
sam@debian:~/GRASS&QGIS/grass-6.2.0$

Can someone explain me the motive?
I use Debian Etch!
--
View this message in context: http://www.nabble.com/Build-Grass62!-tf2660767.html#a7421558
Sent from the Grass - Users mailing list archive at Nabble.com.

I don't resolved it, still!
Can someone help me?

--
View this message in context: http://www.nabble.com/Build-Grass62!-tf2660767.html#a7434367
Sent from the Grass - Users mailing list archive at Nabble.com.

Salvator*eL*arosa wrote:

Hi to everbody, I have some problems while i am compiling grass-6.2.0
stable version.....

..

I have this error:

sam@debian:~/GRASS&QGIS/grass-6.2.0$ make
mkdir -p /home/sam/GRASS&QGIS/grass-6.2.0/bin.i686-pc-linux-gnu
/bin/sh: QGIS/grass-6.2.0/bin.i686-pc-linux-gnu: No such file or
directory make: ***
[/home/sam/GRASS&QGIS/grass-6.2.0/bin.i686-pc-linux-gnu] Error 127
sam@debian:~/GRASS&QGIS/grass-6.2.0$

remove the the "&" in the "GRASS&QGIS" path name.

"mkdir -p" isn't quoting the path so the & is getting parsed by the
shell. (it thinks everything after the & is a new command)

Hamish

Hamish wrote:

Salvator*eL*arosa wrote:

Hi to everbody, I have some problems while i am compiling grass-6.2.0
stable version.....

..

I have this error:

sam@debian:~/GRASS&QGIS/grass-6.2.0$ make
mkdir -p /home/sam/GRASS&QGIS/grass-6.2.0/bin.i686-pc-linux-gnu
/bin/sh: QGIS/grass-6.2.0/bin.i686-pc-linux-gnu: No such file or
directory make: ***
[/home/sam/GRASS&QGIS/grass-6.2.0/bin.i686-pc-linux-gnu] Error 127
sam@debian:~/GRASS&QGIS/grass-6.2.0$

remove the the "&" in the "GRASS&QGIS" path name.

"mkdir -p" isn't quoting the path so the & is getting parsed by the
shell. (it thinks everything after the & is a new command)

Hamish

_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser

Thanks for your reply.....
work fine, now
--
View this message in context: http://www.nabble.com/Build-Grass62!-tf2660767.html#a7438505
Sent from the Grass - Users mailing list archive at Nabble.com.

Hamish wrote:

"mkdir -p" isn't quoting the path

That looks like a bug in the Makefile(s); can you say which one(s)?

--
Glynn Clements <glynn@gclements.plus.com>