From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] OpenAFS ebuild
Date: 16 Nov 2001 13:14:58 +0100 [thread overview]
Message-ID: <1005912898.10193.7.camel@zoidberg> (raw)
In-Reply-To: <3BF50DB7.80B500F4@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]
fre 2001-11-16 klockan 13.59 skrev Achim Gottinger:
> Mikael Hallendal wrote:
> >
> > fre 2001-11-16 klockan 13.45 skrev Achim Gottinger:
> > > Mikael Hallendal wrote:
> > > >
> > > > Hi!
> > > >
> > > > The OpenAFS ebuild seems pretty broken.
> > > >
> > > > 1) It fails for not finding a h-file LINUX/osi_vfs.h in src/afs
> > >
> > > do you see the following line in the configure output
> > >
> > > checking whether to build osi_vfs.h... wrote src/afs/LINUX/osi_vfs.h
> >
> > No.
>
> Hmm I do so we should check what configure does at this point.
Ok, I've located the problem. I found that /usr/include/linux is no
longer a symlink to /usr/src/linux/include/linux, so the stuff in
/usr/include/linux no longer reflects my current kernel.
Which package installs /usr/include/linux (linux-source)? If so I think
openafs should depend on that package since it doesn't compile
otherwise.
> > > > 2) it tries to link statically against a .so-file (libncurses.so)
> >
> > I'm adding a dosed to replace libncurses.so with libncurses.a if no one
> > objects.
>
> The latest ncurses package has a link for libncurses.so and here
> afsmonitor and compile_et are linked agains this shared lib. So the
> dosed is not required I think.
> I just retried the build here and it still works fine, my system build
> is from the last three days.
Does it use -lncurses in your case (to link dynamically?) Here it's
hardcoded to /usr/lib/libncurses.so (in the Makefile.in-file).
Where do /usr/lib/libncurses.so point?
Regards,
Mikael Hallendal
--
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-11-16 13:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 11:48 [gentoo-dev] OpenAFS ebuild Mikael Hallendal
2001-11-16 12:45 ` Achim Gottinger
2001-11-16 11:58 ` Mikael Hallendal
2001-11-16 12:59 ` Achim Gottinger
2001-11-16 12:14 ` Mikael Hallendal [this message]
2001-11-16 13:15 ` Achim Gottinger
2001-11-16 12:31 ` Mikael Hallendal
2001-11-16 13:35 ` Achim Gottinger
2001-11-16 12:52 ` Mikael Hallendal
2001-11-16 18:48 ` Daniel Robbins
2001-11-16 14:45 ` Juergen Ilse
2001-11-16 15:11 ` Mikael Hallendal
2001-11-16 18:15 ` Martin Schlemmer
2001-11-16 19:42 ` [gentoo-dev] How stable is RC-6? Nicholas Burlett
2001-11-16 20:17 ` Bart Verwilst
2001-11-17 3:52 ` Collins Richey
2001-11-16 20:16 ` [gentoo-dev] OpenAFS ebuild Mikael Hallendal
2001-11-17 12:35 ` Holger Brueckner
-- strict thread matches above, loose matches on Subject: below --
2003-08-04 15:16 [gentoo-dev] openafs ebuild Frederick Grim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1005912898.10193.7.camel@zoidberg \
--to=hallski@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox