From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri, 13 Sep 2013 14:30:37 +0200
From: Jens Staal <staal1978@gmail.com>
To: 9fans@9fans.net
Message-ID: <20130913143037.5cefd0f1@Krypton>
In-Reply-To: <2f1c2a7896ed55e748a9537187c8e53b@brasstown.quanstro.net>
References: <56b14cb05fe9efa2d1c1ee474b6434c7@proxima.alt.za>
	<94594e360af74d88545fc8c2358c4c44@brasstown.quanstro.net>
	<6270901.iqtIslEohE@krypton>
	<2f1c2a7896ed55e748a9537187c8e53b@brasstown.quanstro.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] incompatible type signature
Topicbox-Message-UUID: 7f56b372-ead8-11e9-9d60-3106f5b1d025

On Thu, 12 Sep 2013 11:16:31 -0400
erik quanstrom <quanstro@quanstro.net> wrote:

> > On 9atom 1 out of two type signature conflicts got resolved when I
> > tried to build GNU nano (using FGB's PDcurses, rebuilt on 9atom to
> > avoid that character width or something might be an issue).
> >
> > The resolved issue was some sort of internal conflict in libbsd
> > bind. The remaining issue gives the following linking error (for
> > nano) and is a conflict between libbsd and libdraw:
> >
> > ??none??: incompatible type signatures 50220469
> > (/386/lib/ape/libdraw.a(screen)) and
> > 9bbe58(/386/lib/ape/libbsd.a(bind)) for bind
>
> when did you last sync your source?  i believe this has been fixed:
>
> minooka; nm (/386/lib/ape /n/atom/plan9`{pwd})^/libdraw.a | grep bind
>
> i just applied the patch "9diff" to 9atom which includes adiff (see
> 9diff(1)) which should make tracking differences easier.
>
> - erik
>

This was indeed the issue: I had done a recent pull but not rebuilt the
libraries.

Now nano builds on APE with PDCurses and sort of "works" : can open
text files and fast commands work.
what does not work:
- line change by enter
- saving a file (related to my mkstemp hack?)

... however it was just a test to see whether I could build stuff with
the pdcurses so not critical as such :) Now I can at least try to
figure out what goes wrong with the rest :)