I ran 'svn up' on the grass-6.5 directory on my laptop running
Slackware-13.37/x64, then configured and tried building. The make fails
because the main.o is 32-bit not 64-bit.
Is there another configuration option I need for this? Or, is the issue
something else?
Rich
On Fri, 20 Jan 2012, Rich Shepard wrote:
Is there another configuration option I need for this? Or, is the issue
something else?
I added '--enable-64bit' to the configuration but that made no difference.
Rich
Rich Shepard wrote:
I ran 'svn up' on the grass-6.5 directory on my laptop running
Slackware-13.37/x64, then configured and tried building. The make fails
because the main.o is 32-bit not 64-bit.Is there another configuration option I need for this? Or, is the issue
something else?
It's impossible to say without more information (e.g. exact errors
messages).
The main issue is that everything has to use the same architecture:
you can't link a 32-bit executable against 64-bit libraries or vice
versa.
I added '--enable-64bit' to the configuration but that made no difference.
That option only affects certain platforms, specifically AIX, HP-UX,
IRIX and Solaris.
On Linux, unless there's something wrong with your build environment,
you shouldn't need any additional options. The compiler should
automatically generate 64-bit object files and the default library
search paths used by the linker should only contain 64-bit libraries.
If you need to use any libraries which you compiled yourself, ensure
that they were built as 64-bit. Don't point any --with-*-includes=
options to directories containing 32-bit libraries.
--
Glynn Clements <glynn@gclements.plus.com>
On Sat, 21 Jan 2012, Glynn Clements wrote:
It's impossible to say without more information (e.g. exact errors
messages).
I'll do a screenshot tomorrow and send that.
The main issue is that everything has to use the same architecture:
you can't link a 32-bit executable against 64-bit libraries or vice
versa.
Of course! I should mention that GRASS 6.5svn successfully built on this
laptop before. I ran 'svn up', configured, and tried to make it.
If you need to use any libraries which you compiled yourself, ensure that
they were built as 64-bit. Don't point any --with-*-includes= options to
directories containing 32-bit libraries.
Not applicable. Everything on that box was built on that box; most with
SlackBuild scripts.
Here're the configuration options:
--with-postgres --with-sqlite --with-cairo --with-freetype --with-cxx \
--with-geos=usr/bin/geos-config --with-gdal=/usr/bin/gdal-config \
--with-python=/usr/bin/python-config --with-wxwidgets=/usr/bin/wx-config \
--enable-largefile --with-postgres-includes=/usr/local/pgsql/include/ \
--with-postgres-libs=/usr/local/pgsql/lib/ --with-openmp\
--with-sqlite-includes=/usr/include/ --with-sqlite-libs=/usr/lib/
Thanks,
Rich
On Sat, 21 Jan 2012, Glynn Clements wrote:
It's impossible to say without more information (e.g. exact errors
messages).
Hi, Glynn!
A screenshot is attached. Please let me know if I can provide more
information.
Thanks,
Rich
On Fri, 20 Jan 2012, Rich Shepard wrote:
I ran 'svn up' on the grass-6.5 directory on my laptop running
Slackware-13.37/x64, then configured and tried building. The make fails
because the main.o is 32-bit not 64-bit.
FIXED: deleted all files in the grass-6.5svn/ directory then checked 'em
all out again instead of updating. Built with no errors.
Rich
Rich Shepard wrote:
Of course! I should mention that GRASS 6.5svn successfully built on this
laptop before. I ran 'svn up', configured, and tried to make it.
There should have been a "make clean" step in there somewhere.
Whenever you update the source code or re-run cnofigure, you should
always run "make clean".
--
Glynn Clements <glynn@gclements.plus.com>
On Sun, 22 Jan 2012, Glynn Clements wrote:
There should have been a "make clean" step in there somewhere. Whenever
you update the source code or re-run cnofigure, you should always run
"make clean".
Yep. And that's what I forgot to do just after the previous build. Sigh.
I'll try to not make the same error again.
Rich