On Wed, Nov 29, 2006 at 09:07:33PM +0100, Joachim Schipper wrote:
> On Mon, Nov 27, 2006 at 05:31:56PM +0100, Andreas Bihlmaier wrote:
> > Hello ports@,
> > 
> > since I want to do some mC development in my spare time on an Atmel
> > at89c51ed2 I was in need for a C compiler.
> > 
> > The port is based/improved on Alexandre Anriot's port:
> > http://marc.theaimsgroup.com/?l=openbsd-ports&m=111993817914959&w=2
> > 
> > All unnecessary bash crap was removed.
> > 
> > I hope it will be commited this time, _IF_ everything is fine :)
> > 
> > #pkg_info sdcc
> > Comment:
> > Small Device C Compiler
> > 
> > Description:
> > SDCC is an open source retargettable, optimizing ANSI - C compiler. The
> > current version targets the Intel 8051, Zilog Z80, Dallas 80C390,
> > Motorola HC08 and Microchip PIC MCUs.
> > 
> > Maintainer: Andreas Bihlmaier <[EMAIL PROTECTED]>

First of all,
thanks for the feedback :)

New port attached (see below).
 
> While building (on -current/i386), I noticed a couple of lines like
> 
> gputils not found -- PIC14 library not built!
> You might want to explicitly disable gputils, or depend on them.
Doh! Better to depend on it, somebody might use PIC

> make lib-depends-check is not entirely happy, either:
> 
> melpomene sdcc# make install
> ===>  Verifying specs:  c curses m panel stdc++ panel
> ===>  found c.40.2 curses.10.0 m.2.3 panel.3.0 stdc++.42.0
> ===>  Installing sdcc-2.6.0 from /usr/ports/packages/i386/all/
> sdcc-2.6.0: complete                                                          
>      
> melpomene sdcc# make lib-depends-check
> 
> /usr/ports/packages/i386/all/sdcc-2.6.0.tgz:
> Extra: curses.10
> Extra: panel.3

I know about this issue, BUT how to resolve this?
Never seen something like WANTLIB= curses.10
Not even sure if this _would_ be syntactially correct.

> Apparently, it should link against curses.10.0 and such. I don't know
> whether or not this is a problem.
Perhaps somebody could elaborate on this or point to relevant RTFM.

> It produces a text file with some digits when run on a trivial program,
> such as
> 
> int main (void) {
>       return 0;
> }
> 
> but I have no real clue about what it should do, or any devices to test
> it on.
> 
>               Joachim

I know that it (the compiled Intel HEX files) work, at least for my mC.
Tested on i386 and amd64 (both -current).

Regards,
ahb

Attachment: devel_sdcc.tgz
Description: application/tar-gz

Reply via email to