Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 3132 - le-1.9.0.ebuild (new package)
Summary: le-1.9.0.ebuild (new package)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High enhancement (vote)
Assignee: Michael M Nazaroff (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-28 19:25 UTC by Matt Keadle
Modified: 2003-02-04 19:42 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
le-1.9.0.ebuild (le-1.9.0.ebuild,761 bytes, text/plain)
2002-05-28 19:26 UTC, Matt Keadle
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Keadle 2002-05-28 19:25:34 UTC
LE is a small, lightweight, hex capable console editor. It uses the ncurses
library for rendering.
Comment 1 Matt Keadle 2002-05-28 19:26:01 UTC
Created attachment 1201 [details]
le-1.9.0.ebuild
Comment 2 Matt Keadle 2002-06-03 22:31:29 UTC
Sorry. I just noticed I left out the DEPEND for ncurses. DOH.
Comment 3 Michael M Nazaroff (RETIRED) gentoo-dev 2002-06-17 12:55:07 UTC
implement-inlines -Winline -Wall -c highli.cc
highli.cc: In static member function `static void syntax_hl::attrib_line(const
char*, int, const char*, int, unsigned char*)':
highli.cc:466: `CLK_TCK' undeclared (first use this function)
highli.cc:466: (Each undeclared identifier is reported only once for each
function it appears in.)
make[2]: *** [highli.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/var/tmp/portage/le-1.9.0/work/le-1.9.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/le-1.9.0/work/le-1.9.0'
make: *** [all-recursiv


Ok this isn't my day for ebuilds compiling on my machine .. ergh..
Matt ... I will look into this one as well but just thought I would let you know :o)

Naz
Comment 4 Matt Keadle 2002-06-17 13:55:25 UTC
gcc 2.95 here. never considered it may have issues with 3.x.

i don't have a gcc 3.x machine handy, but i'll see what i can dig up.