On Tuesday, 28 December 2004, at 19:43:36 (-0500),
Mike Frysinger wrote:
> so i just upgraded to eterm-0.9.3 / libast-0.6.1 and i noticed that
> sometimes i get these overlines when using some apps ... these lines
> didnt exist before ...
>
> i happened to have some eterm-0.9.2 / libast-0.5 still
On Tuesday, 28 December 2004, at 19:40:34 (-0500),
Peter Hyman wrote:
> > configure creates the Makefiles
>
> That's my point. It doesn't! There is no Makefile.in.
Peter,
This is why these tools are less-than-affectionately known around here
as autoFUCK. There's very little consistency between
On Tuesday, 28 December 2004, at 19:07:20 (-0500),
Mike Frysinger wrote:
> lemme redefine 'bombs' ... it doesnt install the file into
> $(DESTDIR)/usr/share/terminfo/
Ah, okay. Yes, that can happen. :)
The reason is this: The contents of /usr/share/terminfo are owned by
ncurses, and newer ver
You need to get the ecco theme eet from my website. www.atmos.org/edje/
mkdir $prefix/share/entrance/ecco/
copy the ecco.eet to that directory
run entrance_edit as root, i'm adding a printf to cvs to tell you where it
is. there's a long story behind why there's no theme eet in cvs, etc etc.
I d
On Tuesday 28 December 2004 05:59 pm, Peter Hyman wrote:
> Well, this was not easy for me, esp., since I am not the config guru.
take a step back
why are you running these autotools yourself ? why arent you running
`./autogen.sh` ?
as you showed somewhere in a previous e-mail, you're attemptin
On Tue, 2004-12-28 at 20:07 -0500, Mike Frysinger wrote:
> On Tuesday 28 December 2004 07:40 pm, Peter Hyman wrote:
> > That's my point. It doesn't! There is no Makefile.in.
>
> Makefile.in is generated by automake from Makefile.am and other magical
> files,
> configure generates Makefile from M
On Tuesday 28 December 2004 07:40 pm, Peter Hyman wrote:
> That's my point. It doesn't! There is no Makefile.in.
Makefile.in is generated by automake from Makefile.am and other magical files,
configure generates Makefile from Makefile.in
-mike
---
so i just upgraded to eterm-0.9.3 / libast-0.6.1 and i noticed that sometimes
i get these overlines when using some apps ... these lines didnt exist
before ...
i happened to have some eterm-0.9.2 / libast-0.5 still running, so i compared
them and took a screenshot:
http://dev.gentoo.org/~vapier
On Tue, 2004-12-28 at 18:28 -0500, Michael Jennings wrote:
> On Tuesday, 28 December 2004, at 17:59:11 (-0500),
> Peter Hyman wrote:
>
> > Well, this was not easy for me, esp., since I am not the config guru.
> >
> > HOWEVER, I found the problem that allowed me to complete configure,
> > althoug
On Tuesday, 28 December 2004, at 17:59:11 (-0500),
Peter Hyman wrote:
> Well, this was not easy for me, esp., since I am not the config guru.
>
> HOWEVER, I found the problem that allowed me to complete configure,
> although it still does not create a Makefile.
>
> First, configure.in has an er
Well, this was not easy for me, esp., since I am not the config guru.
HOWEVER, I found the problem that allowed me to complete configure,
although it still does not create a Makefile.
First, configure.in has an error
[EMAIL PROTECTED]:/mnt/src/libast$ automake -a -c
configure.in:91: required fi
On Tuesday 28 December 2004 06:21 pm, Michael Jennings wrote:
> On Tuesday, 28 December 2004, at 18:06:06 (-0500),
> Mike Frysinger wrote:
> > when utilizing DESTDIR with the install target, doc/Makefile bombs
> > ...
>
> Doesn't happen here.
lemme redefine 'bombs' ... it doesnt install the file i
when utilizing DESTDIR with the install target, doc/Makefile bombs ... it's
because doc/Makefile.am's install-data-hook doesnt respect DESTDIR ...
-mike
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundred
On Tuesday, 28 December 2004, at 18:06:06 (-0500),
Mike Frysinger wrote:
> when utilizing DESTDIR with the install target, doc/Makefile bombs
> ...
Doesn't happen here.
> it's because doc/Makefile.am's install-data-hook doesnt respect
> DESTDIR ...
Nor should it. But in any event, all the inst
On Tuesday 28 December 2004 10:55 am, Michael Jennings wrote:
> Given that 0.6.1 was released on the 14th, I'd say yes, it is. :)
side note, front page of http://www.eterm.org/ is outdated:
# Latest Release:0.9.2
# CVS Version:0.9.3
shouldnt release now say 0.9.3 ?
-mike
---
On Tue, 2004-12-28 at 15:56 -0600, Nathan Ingersoll wrote:
> Try setting one of your language variables to en_US.UTF-8
>
> That shushed the error message for me. Regardless, that is a non-fatal
> warning and should have nothing to do with your problem afaik.
Yes, it IS non-fatal. entrance_edit en
No matter what I type, entrance_edit does nothing.
At first I thought ecore_init was killing it, but it returns TRUE which
is good. entrance_edit is aborting sometime after without a message.
[EMAIL PROTECTED]:~$ entrance_edit
ISO-8859-1
WARNING: not a utf8 locale!
1
I added some output to ecore
On Tuesday, 28 December 2004, at 09:53:09 (-0500),
Peter Hyman wrote:
> But perhaps my libast v 0.5 is out of date.
Given that 0.6.1 was released on the 14th, I'd say yes, it is. :)
Michael
--
Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]>
n + 1, Inc., http://www.n
Peter Hyman <[EMAIL PROTECTED]> [2004-12-28 16:32]:
> On Tue, 2004-12-28 at 16:19 +0100, Tilman Sauerbeck wrote:
> > Peter Hyman <[EMAIL PROTECTED]> [2004-12-28 16:14]:
> > > > > Am I missing something?
> > > >
> > > > Yes. libast.m4
> > > >
> > > [EMAIL PROTECTED]:~$ locate libast.m4
> > > /usr
On Tue, 2004-12-28 at 16:19 +0100, Tilman Sauerbeck wrote:
> Peter Hyman <[EMAIL PROTECTED]> [2004-12-28 16:14]:
> > > > Am I missing something?
> > >
> > > Yes. libast.m4
> > >
> > [EMAIL PROTECTED]:~$ locate libast.m4
> > /usr/share/aclocal/libast.m4
>
> Try
> export ACLOCAL_FLAGS="-I /usr/lo
Peter Hyman <[EMAIL PROTECTED]> [2004-12-28 16:14]:
> > > Am I missing something?
> >
> > Yes. libast.m4
> >
> [EMAIL PROTECTED]:~$ locate libast.m4
> /usr/share/aclocal/libast.m4
Try
export ACLOCAL_FLAGS="-I /usr/local/share/aclocal"
--
Regards,
Tilman
-
Same error happens when compiling libast from cvs.
Cannot find Makefile.in.
Are there particular versions of autoconf, automake, etc. that I need?
--
Peter
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on h
On Tue, 2004-12-28 at 09:41 -0500, Michael Jennings wrote:
snip...
> >
> > Am I missing something?
>
> Yes. libast.m4
>
[EMAIL PROTECTED]:~$ locate libast.m4
/usr/share/aclocal/libast.m4
I seem to have it. But perhaps my libast v 0.5 is out of date. I will
update that and see if that helps.
--
On Tuesday, 28 December 2004, at 09:37:41 (-0500),
Peter Hyman wrote:
> autogen.sh returns errors and I don't know why!
>
> automake --version 1.9.3
> aclocal --version 1.9.3
> autoconf --version 2.59
> autoheader --version 2.59
> libtool --version 1.5.6
>
> After running autogen, the following
autogen.sh returns errors and I don't know why!
automake --version 1.9.3
aclocal --version 1.9.3
autoconf --version 2.59
autoheader --version 2.59
libtool --version 1.5.6
After running autogen, the following file is created in the top source
dir. .in, no filename, just .in. I think it is config.h
25 matches
Mail list logo
