Sorry Mike for the miscommunication. I attached the complete log. :)
--
With kind regards,
Didier.
Yum/apt repository for DR17/EFL: http://sps.nus.edu.sg/~didierbe
Didier F.B Casse
PhD candidate, Singapore Synchrotron Light Source (SSLS)
National University of Singapore.
On 7/18/0
On Monday 18 July 2005 04:25 am, Didier Casse wrote:
> On 7/18/05, Mike Frysinger <[EMAIL PROTECTED]> wrote:
> > On Sunday 17 July 2005 10:32 pm, Didier Casse wrote:
> > > config.status: error: cannot find input file: Makefile.in
> >
> > Makefile.in doesnt exist because the autotools failed
> >
> >
On 7/18/05, Mike Frysinger <[EMAIL PROTECTED]> wrote:
> On Sunday 17 July 2005 10:32 pm, Didier Casse wrote:
> > config.status: error: cannot find input file: Makefile.in
>
> Makefile.in doesnt exist because the autotools failed
>
> no idea why exactly they failed, you cut the log after that poin
On Sunday 17 July 2005 10:32 pm, Didier Casse wrote:
> config.status: error: cannot find input file: Makefile.in
Makefile.in doesnt exist because the autotools failed
no idea why exactly they failed, you cut the log after that point ...
-mike
I checked out libast from CVS but the latter is looking for
makefile.in which doesn't seem to be around. Any clues anybody? :( Am
I missing out something?
[SNIP]
checking for snprintf... yes
checking for vsnprintf... yes
checking for strcasestr... yes
checking for strcasechr... no
checking for str
On Sunday, 17 July 2005, at 11:51:51 (-0500),
laurence vanek wrote:
> I just did a fresh CVS co and rebuilt libast (no issues now). For the
> Eterm build I did this:
>
> export ACLOCAL_FLAGS="-I /usr/local/share/aclocal"
>
>
> as Nathan & you suggested prior to "./autogen.sh".
>
> It works on
laurence vanek wrote:
>
> I just did a fresh CVS co and rebuilt libast (no issues now). For the
> Eterm build I did this:
>
> export ACLOCAL_FLAGS="-I /usr/local/share/aclocal"
>
>
> as Nathan & you suggested prior to "./autogen.sh".
>
> It works on my updated FC4 sytem. "make" & "make install" ok
Michael Jennings wrote:
Have you tried setting ACLOCAL_FLAGS="-I /usr/local/share/aclocal"
when calling autogen.sh?
Michael
Michael -
I just did a fresh CVS co and rebuilt libast (no issues now). For the
Eterm build I did this:
export ACLOCAL_FLAGS="-I /usr/local/share/aclocal"
as Nath
On Saturday, 16 July 2005, at 13:32:10 (-0500),
laurence vanek wrote:
> libast.m4 resides at "/usr/local/share/aclocal/libast.m4". since I
> didnt put it there I presume the "make install" did during my build
> of libast.
Yes, that's correct. But that doesn't mean aclocal will automatically
look
Michael Jennings wrote:
On Sunday, 17 July 2005, at 01:58:46 (+0200),
dienekes wrote:
Eterm builds and works fine with the commented out line.
Did you actually read the comment? If you have to comment out that
line, the problem is on YOUR END.
As you are so skilled I wonder tha
On Sunday, 17 July 2005, at 01:58:46 (+0200),
dienekes wrote:
> Eterm builds and works fine with the commented out line.
Did you actually read the comment? If you have to comment out that
line, the problem is on YOUR END.
> As you are so skilled I wonder that there is a "eterm & FC4" thread.
>
Michael Jennings wrote:
>Those who cannot read have no business using Eterm.
>
>
Eterm builds and works fine with the commented out line.
>No, there is something wrong with Eterm's user.
>
>
>
As you are so skilled I wonder that there is a "eterm & FC4" thread.
With a working configure there
Nathan Ingersoll wrote:
>The problem with the configure is that it wasn't able to substitute a
>libast.m4 macro when aclocal ran from autogen.sh. Where do you have
>libast installed?
>
>
>
>
>
/usr/local/enlightenment/
I modified the value of the ACLOCAL environment variable to
/usr/local/enl
On Sunday, 17 July 2005, at 00:07:34 (+0200),
dienekes wrote:
> # NOTE: The following line is NOT NOT NOT NOT NOT a typo!
> # If you are having problems with it, libast.m4 is not installed
> # or aclocal couldn't find it. Hence the problem is on YOUR end.
> dps_snprintf_oflow()
Those who cannot
The problem with the configure is that it wasn't able to substitute a
libast.m4 macro when aclocal ran from autogen.sh. Where do you have
libast installed?
On 7/16/05, dienekes <[EMAIL PROTECTED]> wrote:
> Nathan Ingersoll wrote:
>
> >This is not a correct solution, it's working around a problem
Nathan Ingersoll wrote:
>This is not a correct solution, it's working around a problem with aclocal.
>Try:
>export ACLOCAL_FLAGS="-I /usr/local/share/aclocal"
>./autogen.sh
>
>
unfortunately this also doesn't help. I also linked libast.m4 to
/usr/share/aclocal and /usr/local/share/ac
This is not a correct solution, it's working around a problem with aclocal. Try:
export ACLOCAL_FLAGS="-I /usr/local/share/aclocal"
./autogen.sh
Libast installs libast.m4 which is required by aclocal to substitute
dps_snprintf_oflow. The default install path is in
/usr/local/share/aclocal,
Thererafter I changed
# NOTE: The following line is NOT NOT NOT NOT NOT a typo!
# If you are having problems with it, libast.m4 is not installed
# or aclocal couldn't find it. Hence the problem is on YOUR end.
dps_snprintf_oflow()
of ./configure to
# NOTE: The following line is NOT NOT NOT N
laurence vanek wrote:
> Im running FC4, any suggestions as to where the "proper location"
> might be? Perhaps its
> a path issue.
I installed libast before I run configure for Eterm in
/usr/local/enlightenment where all my E stuff resides. Result:
checking for nl_langinfo... yes
./configure: lin
Michael Jennings wrote:
On Friday, 15 July 2005, at 22:18:32 (-0500),
laurence vanek wrote:
./configure: line 23460: syntax error near unexpected token `echo'
./configure: line 23460: `echo "$as_me:$LINENO: checking for pow in -lm" >&5'
Install libast.m4 into the proper location.
Mi
On Friday, 15 July 2005, at 22:18:32 (-0500),
laurence vanek wrote:
> ./configure: line 23460: syntax error near unexpected token `echo'
> ./configure: line 23460: `echo "$as_me:$LINENO: checking for pow in -lm" >&5'
Install libast.m4 into the proper location.
Michael
--
Michael Jennings (a.k.
Mike Frysinger wrote:
On Friday 15 July 2005 09:33 pm, laurence vanek wrote:
yes, that worked. thank you.
added to cvs then
As a side note, ./autogen for Eterm generates complaint for configure file.
The file lines involved are line number 23460, 23461. Complaining about
syntax
On Friday 15 July 2005 09:33 pm, laurence vanek wrote:
> yes, that worked. thank you.
added to cvs then
> As a side note, ./autogen for Eterm generates complaint for configure file.
> The file lines involved are line number 23460, 23461. Complaining about
> syntax error in the following 2 lines
Mike Frysinger wrote:
On Friday 15 July 2005 12:02 am, laurence vanek wrote:
This patch allow me to build libast.but during Eterm make I got:
=
In file included from feature.h:99,
from actions.c:27:
/usr/local/include/libast.h:289:19: error: #if with no expressio
On Friday 15 July 2005 12:02 am, laurence vanek wrote:
> This patch allow me to build libast.but during Eterm make I got:
>
> =
> In file included from feature.h:99,
> from actions.c:27:
> /usr/local/include/libast.h:289:19: error: #if with no expression
does this work
Mike Frysinger wrote:
On Thursday 14 July 2005 12:19 am, laurence vanek wrote:
Of course eterm needs libast to build. I would imagine its gcc4 in FC4.
failed same way for me with gcc-4.0.1 on Gentoo ... checked in this patch
which seemed to fix the issue for me:
Index: libast.h
==
On Thursday 14 July 2005 12:19 am, laurence vanek wrote:
> Of course eterm needs libast to build. I would imagine its gcc4 in FC4.
failed same way for me with gcc-4.0.1 on Gentoo ... checked in this patch
which seemed to fix the issue for me:
Index: libast.h
27 matches
Mail list logo
