Paul D. Smith wrote:
I'm still waiting for _ANY_ kind of response here.
Doesn't anyone know or care about config.guess or config.sub anymore?
From automake manual:
config.guess
config.sub
These programs compute the canonical triplets for the given build,
host, or target architecture. These progra
Joe Buehler writes:
> The IBM AIX compilers do the equivalent of +DAportable by default. For HP,
> you have to tell the compiler to produce a binary that will run on various
> kinds of processors.
Hey Joe,
put the following lines into your .profile file:
CCOPTS='+DAportable'
export C
Joe Buehler <[EMAIL PROTECTED]> writes:
> I have a mix of PA-RISC 1.1 and 2.0 processors and am continually having
> to manually add +DAportable to compile flags in order to get binaries to
> run on both kinds of machines (since I compile on a PA-RISC 2.0 machine).
>
> Is there some reason this i
Togethor with a collaborator, we are putting togethor
a gnu-like package for some scientific analysis. We
have it running on Linux, HP, SGI with both gcc and native
compilers but have run in to some problems on two Sun's;
maybe someone can make suggestions.
1) One of the systems has both X11R5 and
Paul Eggert wrote:
> Joe Buehler writes:
> > I have a mix of PA-RISC 1.1 and 2.0 processors and am continually having
> > to manually add +DAportable to compile flags in order to get binaries to
> > run on both kinds of machines (since I compile on a PA-RISC 2.0 machine).
> >
> > Is there some rea
Schleicher Ralph (LLI) wrote:
put the following lines into your .profile file:
CCOPTS='+DAportable'
export CCOPTS
LDOPTS='+vnocompatwarnings +s'
export LDOPTS
The last two lines make libtool happy.
Thank you, that is what I am going to do.
--
Joe Buehler
AC_INIT (PACKAGE, VERSION, [BUG-REPORT], [TARNAME])
is it possible to have something "more advanced" than just 2.31?
Suppose I want to use "2.31" in file names (e.g., tar name) and
"2.31 (2003-09-01)" for everything else.
Suggestions?
--
Sam Steingold (http://www.podval.org/~sds) running w2k
"L. D. Marks" <[EMAIL PROTECTED]> writes:
> 1) One of the systems has both X11R5 and X11R6 and it
> looks like AC_PATH_XTRA may be getting confused about
> which one to use. Does it seach by decreasing or increasing
> release?
I think it uses the first release it finds. The details are hairy tho
Hi all,
I have a package that produces a shared/static library via libtool.
However this package needs to make use of some external library for
data import/export. Since my library has both a shared and a static
version this external library also needs to have at least a shared
version availab
>>> "Dale" == Dale E Martin <[EMAIL PROTECTED]> writes:
[...]
Dale> AC_CONFIG_HEADERS([FooConfig.h:FooConfig.h.in])
Dale> AC_OUTPUT(Makefile)
AC_CONFIG_FILES([
FooConfig.h:FooConfig.h.in
Makefile
])
AC_OUTPUT
[...]
--
Alexandre Duret-Lutz
%% Paul Eggert <[EMAIL PROTECTED]> writes:
pe> Ben, would you like to have checkin privileges to gnulib?
pe> Then you can simply install the latest versions there.
In another message, John Eaton seems to imply that there's already a
"config" Savannah project that contains these files in CVS.
%% Russell Shaw <[EMAIL PROTECTED]> writes:
rs> Paul D. Smith wrote:
>> I'm still waiting for _ANY_ kind of response here.
>> Doesn't anyone know or care about config.guess or config.sub anymore?
rs> From automake manual:
rs> config.guess
rs> config.sub
rs> These programs compute
> In another message, John Eaton seems to imply that there's already a
> "config" Savannah project that contains these files in CVS. In
> fact, I can find it there now that I know about it :).
Yes, that's correct.
Ben
I've got the following configure.ac:
[configure.ac]
dnl Process this file with autoconf to produce a configure script.
AC_INIT( [foo.cpp] )
AM_INIT_AUTOMAKE( [foo], [v0] )
dnl Require GNU Autoconf version 2.57 or later
AC_PREREQ(2.57)
AC_PROG_CXX
AC_ARG_VAR([SSH],
[When spawning remote
14 matches
Mail list logo