| > From: Akim Demaille <[EMAIL PROTECTED]>
| > Date: 11 Sep 2002 17:23:02 +0200
| >
| > I think the doc should be fixed: I see no reason to prevent someone
| > from just defining to nothing :(
|
| I too have been confused by this in the past, so I installed the
| following doc patch.
|
| 2002
| I'm not able to get autoreconf to work at all, it just hangs:
|
| bash-2.03$ autoreconf --install --verbose --debug
| autoreconf: running: autoconf --version | sed 1q >&2
| autoconf (GNU Autoconf) 2.53
|
| autoreconf: running: autoheader --version | sed 1q >&2
| autoheader (GNU Autoconf) 2.53
| | I'm not able to get autoreconf to work at all, it just hangs:
| |
| | bash-2.03$ autoreconf --install --verbose --debug
| | [...]
| | It hangs forever(?) here.
|
| What does autoreconf -v say?
Sorry, I guess my brains were off :(
Well, honestly, I'd prefer that you check what happens with
On Thu, Sep 12, 2002 at 03:35:19PM +0200, Akim Demaille wrote:
>
> What does autoreconf -v say?
bash-2.03$ autoreconf -v
autoreconf: working in `.'
Akim,
I should have mentioned that I am running the sunfreeware package.
I have not had any problems with their packages in the past but
who knows? I will try to build the autoconf-2.53c.tar.gz version.
-Vance
On Thu, Sep 12, 2002 at 03:41:54PM +0200, Akim Demaille wrote:
>
> Well, ho
| On Thu, Sep 12, 2002 at 03:35:19PM +0200, Akim Demaille wrote:
| >
| > What does autoreconf -v say?
|
| bash-2.03$ autoreconf -v
| autoreconf: working in `.'
Ahem... Well, give a try to the following:
PERLDB_OPTS="NonStop frame=5 AutoTrace" perl -d \
`which autoreconf`
Interrupt it (C-c
Akim,
Yes, that certainly did something! Here's the end of the trace:
396: if ( $debug ) {
406: my $goon = 1;
407: while ( $goon && @ARGV > 0 ) {
589: if ( @ret && $order == $PERMUTE ) {
596: return ($error == 0);
291:foreach (grep { /^-./ } @ARGV)
292
It looks like chdir ('.') never ends?
Give a try to:
perl -e 'chdir(".")'
it should exit (with success).
Akim,
That test seems to pass:
bash-2.03$ perl -e 'chdir(".")'
bash-2.03$
-Vance
On Thu, Sep 12, 2002 at 06:12:28PM +0200, Akim Demaille wrote:
> It looks like chdir ('.') never ends?
>
> Give a try to:
>
> perl -e 'chdir(".")'
>
> it should exit (with success).
| Akim,
| That test seems to pass:
|
| bash-2.03$ perl -e 'chdir(".")'
| bash-2.03$
So what about this one?
perl -e "use Cwd 'chdir'; chdir('.')"
Akim,
Ok, that hangs it:
bash-2.03$ perl -e "use Cwd 'chdir'; chdir('.')"
Nothing after that.
-Vance
On Thu, Sep 12, 2002 at 06:45:15PM +0200, Akim Demaille wrote:
>
> | Akim,
> | That test seems to pass:
> |
> | bash-2.03$ perl -e 'chdir(".")'
> | bash-2.03$
>
> So what about th
> "Vance" == Vance Shipley <[EMAIL PROTECTED]> writes:
Vance> Akim, Ok, that hangs it:
Vance> bash-2.03$ perl -e "use Cwd 'chdir'; chdir('.')"
Vance> Nothing after that.
Good!
Now, what about this:
perl -e 'print ($ENV{"PWD"} =~ m|(/[^/]+(/[^/]+/[^/]+))(.*)|s);'\
-e 'print ", ", $E
Akim,
bash-2.03$ perl -e 'print ($ENV{"PWD"} =~ m|(/[^/]+(/[^/]+/[^/]+))(.*)|s);'\
> -e 'print ", ", $ENV{"PWD"}, ", $1, $2\n"'
/export/home/vances/home/vances/netaccess, /export/home/vances/netaccess,
/export/home/vances, /home/vances
bash-2.03$
On Thu, Sep 12, 2002 at 07:04:35PM +0200,
| Akim,
| bash-2.03$ perl -e 'print ($ENV{"PWD"} =~ m|(/[^/]+(/[^/]+/[^/]+))(.*)|s);'\
| > -e 'print ", ", $ENV{"PWD"}, ", $1, $2\n"'
| /export/home/vances/home/vances/netaccess, /export/home/vances/netaccess,
|/export/home/vances, /home/vances
| bash-2.03$
|
|
| On Thu, Sep 12, 2002 at
Hi all,
I am trying to compile all packages for a Linux from Scratch installation
but I encounter problem with the compilation.
I am using Mandrake 8.2 on a AMD Athlon Xp1600+ and I got following
messages.
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux
bash-2.03$ perl -e 'print join (", ", stat ("/export/home/vances")), "\n"'
35651591, 7808, 16877, 6, 101, 101, 0, 512, 1031850371, 1031836178, 1031836178, 8192, 2
bash-2.03$ perl -e 'print join (", ", stat ("/home/vances")), "\n"'
... and here it hangs
On Thu, Sep 12, 2002 at 07:25:34PM +0200, A
Es schrieb vincent blondel:
>
> Hi all,
>
> I am trying to compile all packages for a Linux from Scratch installation
> but I encounter problem with the compilation.
> I am using Mandrake 8.2 on a AMD Athlon Xp1600+ and I got following
> messages.
>
> checking build system type... i686-pc-linux
vincent blondel writes:
> Hi all,
>
> I am trying to compile all packages for a Linux from Scratch installation
> but I encounter problem with the compilation.
> I am using Mandrake 8.2 on a AMD Athlon Xp1600+ and I got following
> messages.
>
> checking build system type... i686-pc-linux-gnu
>
I give you here the content of my config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.52. Invocation command line was
$ ./configure
##
Es schrieb vincent blondel:
>
> I give you here the content of my config.log
why don't you read it?
[guidod@pc3 pfe]$ gcc -v
Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/2.96/specs
gcc version 2.96 2731 (Mandrake Linux 8.2 2.96-0.76mdk)
[guidod@pc3 pfe]$ gcc -print-prog-name=
Guido Draheim writes:
> tail config.log
Which reminds me, it would be nice if this actually worked.
Currently, tail config.log gives you confdefs.h, before that are the cache
variables. Would it be reasonable to put the tests at the very end?
--
Peter Eisentraut [EMAIL PROTECTED]
Es schrieb Peter Eisentraut:
>
> Guido Draheim writes:
>
> > tail config.log
>
> Which reminds me, it would be nice if this actually worked.
>
> Currently, tail config.log gives you confdefs.h, before that are the cache
> variables. Would it be reasonable to put the tests at the very end?
>
Am I missing something here?
I can't get AC_PROG_PATH to work the way it is documented.
I am using the example from the documentation:
AC_PATH_PROG(INETD, inetd, /usr/libexec/inetd,
$PATH:/usr/libexec:/usr/sbin:/usr/etc:etc)
The path to search for the program should be my P
| bash-2.03$ perl -e 'print join (", ", stat ("/export/home/vances")), "\n"'
| 35651591, 7808, 16877, 6, 101, 101, 0, 512, 1031850371, 1031836178, 1031836178,
|8192, 2
| bash-2.03$ perl -e 'print join (", ", stat ("/home/vances")), "\n"'
|
| ... and here it hangs
Thanks for the report! I have
| Am I missing something here?
|
| I can't get AC_PROG_PATH to work the way it is documented.
| I am using the example from the documentation:
|
| AC_PATH_PROG(INETD, inetd, /usr/libexec/inetd,
|$PATH:/usr/libexec:/usr/sbin:/usr/etc:etc)
|
| [Maybe this is related to my pr
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for gcc... gcc
checking for C compiler default output... configure: error: C compiler cannot create
executables
check config.log for details
T
26 matches
Mail list logo
