Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Oct 2010 12:16:46 +0200
From:      Roland Smith <rsmith@xs4all.nl>
To:        Gary Kline <kline@thought.org>
Cc:        FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject:   Re: mkmf on Linux??
Message-ID:  <20101015101646.GA47849@slackbox.erewhon.net>
In-Reply-To: <20101015012031.GA28439@thought.org>
References:  <20101014233028.GA26845@thought.org> <20101015010017.GA36117@slackbox.erewhon.net> <20101015012031.GA28439@thought.org>

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

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

On Thu, Oct 14, 2010 at 06:20:32PM -0700, Gary Kline wrote:
> On Fri, Oct 15, 2010 at 03:00:17AM +0200, Roland Smith wrote:
> > On Thu, Oct 14, 2010 at 04:30:32PM -0700, Gary Kline wrote:
> > > 	I tried my first minor build of an unusual program [that only a
> > > 	CLI geek like me would use].  But can't find the mkmf that I've
> > > 	used for years.  I haven't found anything comparable in the
> > > 	Linux world.  Has anybody else out there gotten our old '93 src
> > > 	mkmf installed on Linux?
> >=20
> > Even on FreeBSD mkmf 4.11 needs some patching to compile (as evidenced =
by the
> > devel/mkmf port), so I expect same goes for Linux. Maybe the FreeBSD pa=
tches
> > work?
> >=20
> > Roland
>=20
> 	We'll see.  I have entirely forgotten howto use
> 	uuencode/uudecode [!!] -- well, it's been at least 13 years--so=20
> 	carefully transferring things by hand.

Why not use netcat or rsync? Or copy the files to a USB stick to transfer i=
t?
Haven't had use for uuencode for at least a decade.

> 	Anyway, there is the 32 and 64 bit issues... .

Compiles and runs fine here on FreeBSD 8.1-RELEASE amd64, except for a warn=
ing
about mktemp.

> 	gary
>=20
> 	PS: be nice to see [*esp'ly* ubuntu] get with it; maintain the
> 	older stuff.  Even if it was back in the Eozoic:)

A lot of people use the blighted evil twins autoconf and automake. Writing
plain makefiles seems to be relegated to us greybeards these days. :-) and
while a tool like mkmf is fine, I stick to my own makefile templates that I=
've
developed over the years.

Roland
--=20
R.F.Smith                                   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)

--tKW2IUtsqtDRztdT
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)

iEYEARECAAYFAky4Kg4ACgkQEnfvsMMhpyXnZACeKSS6ti/zudGScPUIsWzYguef
vT0An20hO0Kgbjuu7LzU3MrOc/idm8Hz
=idp3
-----END PGP SIGNATURE-----

--tKW2IUtsqtDRztdT--



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