public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] OpenAFS ebuild
Date: 16 Nov 2001 13:52:29 +0100	[thread overview]
Message-ID: <1005915149.6483.13.camel@zoidberg> (raw)
In-Reply-To: <3BF51615.B0F2D040@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

fre 2001-11-16 klockan 14.35 skrev Achim Gottinger:
> Mikael Hallendal wrote:

> hmm here /usr/include/linux never occures in my build log-file but
> instead /usr/src/linux/include/linux

strange, here it looked in /usr/include/linux and said nothing useful or
something and then jumped over the part that made osi_vfs.h.

> > > > Does it use -lncurses in your case (to link dynamically?) Here it's
> > > > hardcoded to /usr/lib/libncurses.so (in the Makefile.in-file).
> > > Must build again
> > 
> > Yes, but the package when unpacked has hardcoded /usr/lib/libncurses.so
> > not -lncurses which it should have if linking dynamically.
> 
> Well it seems to work here unmodified but if you wanna do that fix
> please make sure it uses the lib in /lib and
> not the symlink in /usr/lib. I'll remove this link, cuz it was only
> needed to build openafs.

Hmm .. why is there a libncurses.a in /usr/lib and on in /lib? the one
in /usr/lib is _not_ a symlink to /lib/libncurses.a

> Sounds like your gcc build was not complete (that was my prob last time
> I had no dynamic ncurses libs).
> I have 5.2-r3 installed here -r4 is for gcc-3.0.x if I remember correct.
> Or you only looked into /usr/lib and not into /lib :)

Yes, I only looked in /usr/lib. Found the dynamic libs in /lib.
Anyway, should it build static or dynamic. Either way the Makefile.in is
wrong. Because it says /usr/lib/libncurses.so and should be saying
either:

For static:  /lib/libncurses.a
For dynamic: -lncurses

Is it possible for you to join irc for a while?

Regards,
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-11-16 13:51 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
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 [this message]
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=1005915149.6483.13.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