Hello,
I've one doubt. Can I run 'autogen.sh' (which runs
aclocal, autoheader, autoconf and automake) on one
system to generate 'configure' script and use this
'configure' script on another system for installing
software?
Please give me a reply.
Thanks
shamju joseph
___
Hello,
* shamju joseph wrote on Tue, Nov 07, 2006 at 10:38:46AM CET:
> I've one doubt. Can I run 'autogen.sh' (which runs
> aclocal, autoheader, autoconf and automake) on one
> system to generate 'configure' script and use this
> 'configure' script on another system for installing
> software?
--- Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> Hello,
>
> * shamju joseph wrote on Tue, Nov 07, 2006 at
> 10:38:46AM CET:
> > I've one doubt. Can I run 'autogen.sh' (which
> runs
> > aclocal, autoheader, autoconf and automake) on one
> > system to generate 'configure' script and use
> th
Hello,
in
https://sourceforge.net/tracker/?func=detail&atid=103593&aid=1591697&group_id=3593
I was suggested to send an Email to bug-autoconf@gnu.org:
"
In other words, the last sed command is being skipped.
If you are running the full config.status script and you are
still
getting these funny
Hello Sergei,
Thanks for the report. I assume this is related to Bruce's recent
report on the autoconf@gnu.org list.
* Sergei Steshenko wrote on Tue, Nov 07, 2006 at 11:06:11AM CET:
>
> https://sourceforge.net/tracker/?func=detail&atid=103593&aid=1591697&group_id=3593
> Please let me know whet
Hi
I've some problem running autogen and is listed below.
Can someone tell the reason?
system : i686-pc-linux-gnu
aclocal : 1.9
automake : 1.9
autoheader : 2.59
autoconf : 2.59
libtoolize : 1.5
thanks
shamju joseph
[EMAIL PROTECTED] agg-2.4]$ ./autogen.sh
aclocal:configure.in:15: warning: macro
On 11/7/06, shamju joseph <[EMAIL PROTECTED]> wrote:
examples/Makefile.am:19: Libtool library used but
`LIBTOOL' is undefined
examples/Makefile.am:19:
examples/Makefile.am:19: The usual way to define
`LIBTOOL' is to add `AC_PROG_LIBTOOL'
examples/Makefile.am:19: to `configure.in' and run
`aclocal
--- Jian Wang <[EMAIL PROTECTED]> wrote:
> On 11/7/06, shamju joseph <[EMAIL PROTECTED]>
> wrote:
> > examples/Makefile.am:19: Libtool library used but
> > `LIBTOOL' is undefined
> > examples/Makefile.am:19:
> > examples/Makefile.am:19: The usual way to define
> > `LIBTOOL' is to add `AC_PROG_LI
Hello Ralf and Eric,
On Tue, Oct 31, 2006 at 03:22:48PM +0100, Ralf Wildenhues wrote:
> OTOH, I do think that an m4_for that has an empty 5th argument
> should not magically do the wrong thing, which really rules out
> that the comma following the optional STEP may be dropped.
> Let's remember th
Hi
We can specify cross-compiler by setting the variable CC. How can we specify
other cross tools like linker, assembler, ldd, strip etc to configure script?
Where should we specify CC, before configure or after configure?
(I mean CC=crosscompiler ./configure OR ./configure CC=crosscompile
Hello,
* shamju joseph wrote on Tue, Nov 07, 2006 at 03:14:07PM CET:
>We can specify cross-compiler by setting the variable CC. How can
>we specify other cross tools like linker, assembler, ldd, strip etc
>to configure script?
> Where should we specify CC, before configure or after con
shamju joseph wrote:
> We can specify cross-compiler by setting the variable CC.
That is *not* the way to specify a cross compiler; you *should*
use `--build=some-host --host=a-different-host' to specify cross
compiling mode.
> How can we specify other cross tools like linker, assembler, ldd,
>
* shamju joseph wrote on Tue, Nov 07, 2006 at 11:26:30AM CET:
> I've some problem running autogen and is listed below.
> Can someone tell the reason?
>
> system : i686-pc-linux-gnu
> aclocal : 1.9
> automake : 1.9
> autoheader : 2.59
> autoconf : 2.59
> libtoolize : 1.5
> [EMAIL PROTECTED] agg-2.
* Sergei Steshenko wrote on Tue, Nov 07, 2006 at 07:13:38PM CET:
> "
> build.pl :INFO: executing ==> \cd
> /maxtor5/sergei/AppsFromScratchWD/build/autogen-5.8.7; patch -p0
> < /maxtor5/sergei/AppsFromScratchWD/build/autogen-5.8.7/patch_file
> patching file autoopts/test/Makefile.am
> Hunk #1 FAILE
After release 2.59c `AC_PROG_CC' change <(autoconf) Guidelines>
changed its recommendation how to specify exit status for test
program from
> Test programs should `exit', not `return', from `main', because on
> some systems (old Suns, at least) the argument to `return' in `main'
> is ignored.
to
The issue in question:
https://sourceforge.net/tracker/?func=detail&atid=103593&aid=1591697&group_id=3593
should be fixed by the patch below. On the way I stumbled over more
possible issues (in autogen and its dependencies), none of which seem
Autoconf bugs either; with enough time, I'll try to wr
On 11/7/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
The issue in question:
https://sourceforge.net/tracker/?func=detail&atid=103593&aid=1591697&group_id=3593
should be fixed by the patch below. On the way I stumbled over more
possible issues (in autogen and its dependencies), none of which se
"Ilya N. Golubev" <[EMAIL PROTECTED]> writes:
> That systems ignoring `return' value are now rare is not a reason to
> do so.
It's only part of the reason. The other part is that supporting a
proper declaration for 'exit', that works on all modern systems in
widespread use (both C and C++), was
Paul Eggert wrote:
"Ilya N. Golubev" <[EMAIL PROTECTED]> writes:
Have no systems with broken `return' at hand,
That's the fundamental problem. These systems are _ancient_ -- they
all predate C89 -- and they are so old that nobody uses them any more.
As I recall when porting a numb
> > A reasonable solution would be standard tests as described above:
> > whether the argument to `return' in `main' is ignored, and, if yes,
> > how to call `exit' properly.
>
> Yes, something like that would be reasonable, if someone could take
> the time to write it, and (more important) test i
(Hopefully this is the right list... :-))
While trying to build gawk on Tandem NSK/OSS, I ran into dlopen, dlsys
and dlerror being unresolved. I finally determined that these are
present in the 'zrldsrl' library.
I have written to bug-gawk (AT gnu.org), but thought it would be nice if
autoco
Howard Chu wrote:
Paul Eggert wrote:
"Ilya N. Golubev" <[EMAIL PROTECTED]> writes:
Have no systems with broken `return' at hand,
That's the fundamental problem. These systems are _ancient_ -- they
all predate C89 -- and they are so old that nobody uses them any more.
As I recall when porti
Matthew Woehlke wrote:
Howard Chu wrote:
Paul Eggert wrote:
"Ilya N. Golubev" <[EMAIL PROTECTED]> writes:
Have no systems with broken `return' at hand,
That's the fundamental problem. These systems are _ancient_ -- they
all predate C89 -- and they are so old that nobody uses them any more.
> Matthew Woehlke wrote:
>> Hmm, mainframes? I want to say VMS also uses 'return 1' for success
>> (or maybe it even needs exit; I'm not the one that has to deal with
>> our VMS systems).
As I understand it, on VMS, exit(N) is equivalent to main returning N;
it's just that N==1 also means success.
Paul Eggert wrote:
Matthew Woehlke wrote:
Hmm, mainframes? I want to say VMS also uses 'return 1' for success
(or maybe it even needs exit; I'm not the one that has to deal with
our VMS systems).
As I understand it, on VMS, exit(N) is equivalent to main returning N;
it's just that N==1 also me
--- Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> The issue in question:
> https://sourceforge.net/tracker/?func=detail&atid=103593&aid=1591697&group_id=3593
> should be fixed by the patch below. On the way I stumbled over more
> possible issues (in autogen and its dependencies), none of which s
--- Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> * Sergei Steshenko wrote on Tue, Nov 07, 2006 at 07:13:38PM CET:
> > "
> > build.pl :INFO: executing ==> \cd
> > /maxtor5/sergei/AppsFromScratchWD/build/autogen-5.8.7; patch
> -p0
> > < /maxtor5/sergei/AppsFromScratchWD/build/autogen-5.8.7/patch_fi
Hello Matthew,
* Matthew Woehlke wrote on Tue, Nov 07, 2006 at 09:54:57PM CET:
> (Hopefully this is the right list... :-))
No, it's not, but it's good you mention it. Libtool would need a
similar change.
> While trying to build gawk on Tandem NSK/OSS, I ran into dlopen, dlsys
> and dlerror bei
The following is extracted from autoconf's info manual:
- Macro: AS_HELP_STRING (LEFT-HAND-SIDE, RIGHT-HAND-SIDE)
Expands into an help string that looks pretty when the user
executes `configure --help'. It is typically used in `AC_ARG_WITH'
(*note External Software::) or `AC_ARG
> > [AC_ARG_WITH([foo],
> >AS_HELP_STRING([--with-foo],
> > [use foo (default is NO)]),
> >[ac_cv_use_foo=$withval], [ac_cv_use_foo=no])
> > AC_CACHE_CHECK([whether to use foo],
> >
Thanks, Harlan.
I tried to use AS_HELP_STRING and found that we cannot double quote its
parameters. For example, I wrote a testing configure.ac like this:
AC_INIT([Foo], [1.0], [EMAIL PROTECTED], [foo])
AC_ARG_WITH(
bar,
AS_HELP_STRING([--with-bar=DIR], [[Where to find bar libs]])
)
Then
31 matches
Mail list logo