Date: Wed, 17 Nov 2010 18:12:51 -0800 From: Rob Farmer <rfarmer@predatorlabs.net> To: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de> Cc: "O. Hartmann" <ohartman@zedat.fu-berlin.de>, freebsd-questions@freebsd.org Subject: Re: porting software to FreeBSD, what to do if Makefile lacks? Message-ID: <AANLkTinzs2KAb_gUu3dJ3K-cVfp6V9pc22Pe-EDBB5oU@mail.gmail.com> In-Reply-To: <4CE47A1F.804@mail.zedat.fu-berlin.de> References: <4CE416D0.2020105@zedat.fu-berlin.de> <AANLkTik-TZNc7ZkwKxH%2BrE2Dmd17vgAsmmnNwtRBwwH0@mail.gmail.com> <4CE47A1F.804@mail.zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 17, 2010 at 16:58, O. Hartmann
<ohartman@mail.zedat.fu-berlin.de> wrote:
> Thanks.
> I got it. But it seems that my first porting task run into some difficulties
> for the advanced porters, since there is no autotool environment.
>
> By the way, the global environment variable ${CSH} seems to be noneexistent,
> instead ${SH} exists.
Interesting - I assumed it would be listed in bsd.commands.mk, but it
seems to not be. Most of the base system tools are. In any case, glad
to hear you got it working.
--
Rob Farmer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinzs2KAb_gUu3dJ3K-cVfp6V9pc22Pe-EDBB5oU>