From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 17 15:17:00 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3475F37B401 for ; Thu, 17 Apr 2003 15:17:00 -0700 (PDT) Received: from basement.kutulu.org (pcp03610121pcs.longhl01.md.comcast.net [68.49.239.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8061E43FD7 for ; Thu, 17 Apr 2003 15:16:56 -0700 (PDT) (envelope-from kutulu@kutulu.org) Received: by basement.kutulu.org (Postfix, from userid 1001) id EC1D6A933; Thu, 17 Apr 2003 18:17:03 -0400 (EDT) Date: Thu, 17 Apr 2003 18:17:03 -0400 From: Michael Edenfield To: Beech Rintoul Message-ID: <20030417221703.GA45948@basement.kutulu.org> Mail-Followup-To: Beech Rintoul , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Mailer: Mutt http://www.mutt.org/ X-Accept-Language: en X-PGP-Key: http://www.kutulu.org/pgp/kutulu.asc X-PGP-Fingerprint: 1CE0 3C31 7013 D529 406D 37DC 09CC CD84 A46C 878F cc: freebsd-hackers@freebsd.org Subject: Re: Shared Source CLI X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2003 22:17:00 -0000 --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Beech Rintoul [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--