Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Apr 2003 18:17:03 -0400
From:      Michael Edenfield <kutulu@kutulu.org>
To:        Beech Rintoul <akbeech@northwindcom.net>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: Shared Source CLI
Message-ID:  <20030417221703.GA45948@basement.kutulu.org>
In-Reply-To: <IKEJIJGIHELBGLJDDPDEMELGCIAA.akbeech@northwindcom.net>
References:  <IKEJIJGIHELBGLJDDPDEMELGCIAA.akbeech@northwindcom.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--3MwIy2ne0vdjdPXF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Beech Rintoul <akbeech@northwindcom.net> [030417 16:52]:

> I got a request from one of our microsoft programmers to install sscli on
> one of our FreeBSD boxes. I had no luck compiling it. Has anyone gotten it
> to compile successfully on -CURRENT?

At one point, I did get the lang/cli port to build with no problem. =20
It's a bit outdated (2002-06-19 vs. 2002-11-02) but it worked. =20
Unfortunately, I'm now getting a syntax error in the configure:

=2E/configure: line 1041: syntax error near unexpected token `fi'
=2E/configure: line 1041: `fi'

that I think is unrelated to the sscli port and possibly related to a=20
broken shell.

As far as doing a build of the latest snapshot, it certainly doesn't=20
work out of the box.  The first problem I ran into was with their PAL=20
reimplementation of localtime, ctime, and mktime.  After going through=20
the macro-hackery in the headers that's used to redefine the C runtime=20
functions, you end up with conflicting definitions for these=20
functions, eg, you get:

struct * DUMMY_tm __attribute((cdecl)) PAL_localtime(const time_t *)
and
struct * PAL_tm __attribute((cdecl)) PAL_localtime(const time_t *)

in misc.c, and gcc stops there.  It looks like they're missing a macro=20
replacement of tm -> PAL_tm in a header, but I've not spent time=20
tracking it down.  My next goal, during my free time tommorrow, is to=20
check the patchs in the lang/cli port that I assume deal with similar=20
issues.

(FYI: I did try just dropping the new tarball overtop the one the port=20
expects but most of the patches didn't apply.)

--Mike

 =20

--3MwIy2ne0vdjdPXF
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+nyffCczNhKRsh48RAg+VAJ9QvyOnxdQ4/LY+sHASw8LvdF/6vACdH5G8
HDCKWtSWq99a/y8QeaRCjRY=
=hAlG
-----END PGP SIGNATURE-----

--3MwIy2ne0vdjdPXF--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030417221703.GA45948>