|
From: SourceForge.net <no...@so...> - 2003-01-31 00:14:28
|
Bugs item #677866, was opened at 2003-01-30 19:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=677866&group_id=34096 Category: Package Group: v0.6 Status: Open Resolution: None Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: oidentd and new lfs system Initial Comment: oidentd can't be compile within the new lfs system, contacted author. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=677866&group_id=34096 |
|
From: SourceForge.net <no...@so...> - 2003-03-11 01:47:48
|
Bugs item #677866, was opened at 2003-01-30 19:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=677866&group_id=34096 Category: Package Group: v0.6 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) Summary: oidentd and new lfs system Initial Comment: oidentd can't be compile within the new lfs system, contacted author. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=677866&group_id=34096 |
|
From: Diego T. <dt...@co...> - 2003-01-31 14:19:58
|
On Thu, Jan 30, 2003 at 04:19:23PM -0800, SourceForge.net wrote: > Bugs item #677866, was opened at 2003-01-30 19:19 > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=410643&aid=677866&group_id=34096 > Initial Comment: > oidentd can't be compile within the new lfs system, > contacted author. what is the exact problem with oidentd? -- -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-01-31 15:06:28
|
On Fri, 31 Jan 2003 15:19:10 +0100 Diego Torres <dt...@co...> wrote: > On Thu, Jan 30, 2003 at 04:19:23PM -0800, SourceForge.net wrote: > > Bugs item #677866, was opened at 2003-01-30 19:19 > > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=410643&aid=677866&group_id=34096 > > > Initial Comment: > > oidentd can't be compile within the new lfs system, > > contacted author. > > > what is the exact problem with oidentd? I'm not a programer, so it's a little bit hard for me to analyze that problem. Here is the output: gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -funsigned-char -c `test -f oidentd.c || echo './'`oidentd.c source='oidentd_util.c' object='oidentd_util.o' libtool=no \ depfile='.deps/oidentd_util.Po' tmpdepfile='.deps/oidentd_util.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -funsigned-char -c `test -f oidentd_util.c || echo './'`oidentd_util.c source='oidentd_inet_util.c' object='oidentd_inet_util.o' libtool=no \ depfile='.deps/oidentd_inet_util.Po' tmpdepfile='.deps/oidentd_inet_util.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -funsigned-char -c `test -f oidentd_inet_util.c || echo './'`oidentd_inet_util.c source='oidentd_user_db.c' object='oidentd_user_db.o' libtool=no \ depfile='.deps/oidentd_user_db.Po' tmpdepfile='.deps/oidentd_user_db.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -funsigned-char -c `test -f oidentd_user_db.c || echo './'`oidentd_user_db.c source='oidentd_options.c' object='oidentd_options.o' libtool=no \ depfile='.deps/oidentd_options.Po' tmpdepfile='.deps/oidentd_options.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -funsigned-char -c `test -f oidentd_options.c || echo './'`oidentd_options.c source='oidentd_masq.c' object='oidentd_masq.o' libtool=no \ depfile='.deps/oidentd_masq.Po' tmpdepfile='.deps/oidentd_masq.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -funsigned-char -c `test -f oidentd_masq.c || echo './'`oidentd_masq.c bison -y -d ./oidentd_cfg_parse.y ./oidentd_cfg_parse.y:300.1: syntax error, unexpected "|" ./oidentd_cfg_parse.y:302.21-22: $1 of `cap_statement' has no declared type ./oidentd_cfg_parse.y:303.42-43: invalid $ value ./oidentd_cfg_parse.y:303.42-43: $2 of `cap_statement' has no declared type ./oidentd_cfg_parse.y:305.43-44: invalid $ value ./oidentd_cfg_parse.y:305.43-44: $2 of `cap_statement' has no declared type ./oidentd_cfg_parse.y:307.35-36: $1 of `cap_statement' has no declared type make[4]: *** [stamp_parse] Error 1 make[4]: Leaving directory `/data/build/tmp/oidentd-2.0.4/src' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/data/build/tmp/oidentd-2.0.4/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/data/build/tmp/oidentd-2.0.4' make[1]: *** [all] Error 2 make[1]: Leaving directory `/data/build/tmp/oidentd-2.0.4' make: *** [build] Error 1 |
|
From: Diego T. <dt...@co...> - 2003-01-31 15:33:46
|
On Fri, Jan 31, 2003 at 10:00:45AM -0500, Heiko Zuerker wrote: > > what is the exact problem with oidentd? > > I'm not a programer, so it's a little bit hard for me to analyze that problem. > Here is the output: > bison -y -d ./oidentd_cfg_parse.y > ./oidentd_cfg_parse.y:300.1: syntax error, unexpected "|" pretty strange. I've used bison 1.35 (the same that comes with lfs 4.0) to compile oidentd without problems. is the current devil-linux cvs usable to build a working system, so i can try it? (i've read a post from you which says that cvs was not stable right now). i don't think that we'll get much support from the author of oidentd... looks like a configure setting on bison. -- -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-01-31 17:36:28
|
Diego Torres wrote: > On Fri, Jan 31, 2003 at 10:00:45AM -0500, Heiko Zuerker wrote: > pretty strange. I've used bison 1.35 (the same that comes with lfs 4.0) to compile oidentd without problems. It's the current CVS version of LFS, with glibc 2.3.1 . > is the current devil-linux cvs usable to build a working system, so i can try it? > (i've read a post from you which says that cvs was not stable right now). Yes you can use it. It's things like the probs with oidentd, why I said it's unstable. > i don't think that we'll get much support from the author of oidentd... looks like a configure setting on bison. I hope you can figure it out. It could also be something within the new LFS system, but everything else compiled fine. -- Regards Heiko We are Penguin, resistance is futile! http://www.devil-linux.org |