ports/52130: New Port: sysutils/klineakconfig configure lineakd via kde-interface
kay_lehmann at web.de
Thu Jun 5 09:27:46 UTC 2003
Am Di, 2003-06-03 um 06.50 schrieb Will Andrews:
> Synopsis: New Port: sysutils/klineakconfig configure lineakd via kde-interface
> State-Changed-From-To: open->feedback
> State-Changed-By: will
> State-Changed-When: Mon Jun 2 21:49:26 PDT 2003
> This fails to configure/build for me.
> checking for kde-config... /usr/local/bin/kde-config
> checking for meinproc... /usr/local/bin/meinproc
> checking for keyboard definitions file... no
> The lineakd keyboard definition file lineakkb.def could not be found.
> ===> Building for klineakconfig-0.5.1
> cd . && /bin/sh /home/sheldonl/development/klineakconfig-3/admin/missing --run autoheader
> /home/sheldonl/development/klineakconfig-3/admin/missing: Can't open /home/sheldonl/development/klineakconfig-3/admin/missing: No such file or directory
> gmake: *** [stamp-h.in] Error 2
> *** Error code 2
> Stop in /net/fremont/will/ports/sysutils/klineakconfig.
> Seeing as how there's no PR for lineakd or an existing port (that I
> can find), I'll need that first...
sorry for taking so long to answer but I just went away a few days. I
think you noticed, that the pr's I sent had some problems with cut and
paste, so I had to sent another pr for the ports I wish to include into
portstree. So more actual are pr=52159 (for klineakconfig) and pr=52158
for lineakd. Tilman Linneweh has closed pr=52129, which had some
problems with the patches, which don't apply cleanly. I think the best
would be if you load shar-output for lineakd and klineakconfig from my
homepage to prevent problems with tabs and spaces because of my copy and
paste. The addresses are:
Hope these work. But I have to mention that I noticed a problem with
lineakd (I told Tilman, because he wanted to commit the port, but he
didn't answer till now) with version 5.1-beta. One header which is
needed has been moved to another subdirectory and I don't know how this
should be handled.
Thanks for your answer.
Kay Lehmann <kay_lehmann at web.de>
More information about the freebsd-ports-bugs