Hello,
* spam...@gmx.info wrote on Tue, Feb 16, 2010 at 06:27:46PM CET:
> I can't figure out where the pthread is come from.
[...]
> ==
> # Check for -lpthread
> #
> =
Sorry I forgot the error message:
bin/bash ../../../libtool --tag=CC --mode=link suncc -O3 -UPASSIVE -DFFTW -
mt-o cyto.run cyto_main.o cyto_allocation.o cyto_initialisation.o
cyto_boundary_conditions.o cyto_initial_condition.o cyto_output.o
cyto_equation.o cyto_laplace.o cyto_parallel_de
Hi,
With little more research, this is what I am able to figure out:
1. Enabling subdir-objects option creates .Po files in ".deps"
directories in each _SOURCE file's directories.
In a nested packages configuration, this can cause top-level packages'
_SOURCE and nested packages' _SOURCE to sha
On Tue, 16 Feb 2010, spam...@gmx.info wrote:
I wrote a configure.ac (below), use autoreconf --install
Everything runs fine if I use
CC=gcc CFLAGS="" LDFLAGS="" ./configure
But if I use
CC=suncc CFLAGS="" LDFLAGS="" ./configure
I get a linking problem.
/bin/bash ../../../libtool --tag=CC --
Hello!
I wrote a configure.ac (below), use autoreconf --install
Everything runs fine if I use
CC=gcc CFLAGS="" LDFLAGS="" ./configure
But if I use
CC=suncc CFLAGS="" LDFLAGS="" ./configure
I get a linking problem.
/bin/bash ../../../libtool --tag=CC --mode=link suncc -O3 -UPASSIVE -DFFTW
Hi,
We have been try to port GRUB2's build system to automake. GRUB2
build needs to make use of two different compilers (HOSTCC and
TARGETCC) for compiling grub-utilities and grub-binaries respectively.
So, we started using nested packages approach, where top-level
configure+Makefile.am builds