From owner-freebsd-questions@FreeBSD.ORG Mon May 26 18:42:22 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DCD8AA43 for ; Mon, 26 May 2014 18:42:21 +0000 (UTC) Received: from rc3.surewest.net (rc3.surewest.net [66.60.130.52]) by mx1.freebsd.org (Postfix) with ESMTP id BAEA42FF2 for ; Mon, 26 May 2014 18:42:21 +0000 (UTC) Received: from smtp3.surewest.net ([66.60.130.145]) by rc3.surewest.net ({89e988b2-2a53-469e-91f0-3e9924092bec}) via TCP (outbound) with ESMTP id 20140526184205515; Mon, 26 May 2014 18:42:05 +0000 X-RC-FROM: Received: from smtpauth.surewest.net (smtpauth.surewest.net [66.60.130.153]) by smtp3.surewest.net (Postfix) with ESMTP id 6B5C689729; Mon, 26 May 2014 11:42:05 -0700 (PDT) Received: from blacklamb.mykitchentable.net (mykitchentable.net [69.62.167.70]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtpauth.surewest.net (Postfix) with ESMTPSA id 4ADCD9C215; Mon, 26 May 2014 11:42:05 -0700 (PDT) Received: from [127.0.0.1] (unknown [198.69.254.143]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drew) by blacklamb.mykitchentable.net (Postfix) with ESMTPSA id 869C4D790F; Mon, 26 May 2014 11:42:01 -0700 (PDT) Message-ID: <53838AF9.8030708@mykitchentable.net> Date: Mon, 26 May 2014 11:42:01 -0700 From: Drew Tomlinson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: nightrecon@hotmail.com, freebsd-questions@freebsd.org Subject: Re: Help Compiling apligen References: <538360F7.3090707@mykitchentable.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 140526-2, 05/26/2014), Outbound message X-Antivirus-Status: Clean X-MAG-OUTBOUND: surewest.redcondor.net@66.60.130.145/32 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2014 18:42:22 -0000 On 5/26/2014 10:10 AM, Michael Powell wrote: > Drew Tomlinson wrote: > >> I am not a programmer and I don't understand compiling. If it's not in >> the ports, I don't know how to use it. However I really want to try >> this utility: >> >> http://apligen.sourceforge.net/ >> >> I've downloaded the source and attempted to run 'make'. First error was >> that it couldn't find g++. I figured that out and installed gcc 4.7 >> from the ports tree. Ran 'make' again. Now I get these errors: >> > [snip] > > I'm not a coder either so please take that into account lest I get > something wrong. :-) > > Most of the tarballs have a README and/or an INSTALL file with > instructions. I suspect the step you're missing (and a quick perusal of > these should confirm) that you're skipping the autotools stuff. > > Secondly, the gcc 4.2.1 may, or may not, be useable. Should you rather > utilize a newer gcc installed from ports there are some lines you probably > need to place into /etc/make.conf. Should be easy enough to Google out > these, they essentially point make to the ports-installed compiler instead > of the one in base. > > But back to the autotools step first. Mostly you'll need autoconf, > automake, m4, maybe libtools (not sure anything uses this though), and > possibly gmake. > > The step you may be missing is to run ./configure in wherever you > decompressed the tarball. This cranks through the autoconf/automake process > to attempt to 'adjust' code which has been written with portability in > mind. The adjustment is to prepare for building on a particular platform, > if possible. > > I have seen somewhere in the past occasionally when I've pulled source > straight out of a CVS or Git repository there was another script that needs > to be executed prior to the ./configure step to "pre configure" the > configure. This will show in the README or INSTALL notes if required. > > While I have ommitted a couple of small detail(s) or two, this autotools > portability thing is still not a guarantee that something is buildable on > FreeBSD. This is where the a port maintainer comes in and creates/provides > patches to fix this situation. These are what are in the 'files' directory > under a port in the ports tree where the Makefile is found. > > There are some other small tidbits probably missing, but maybe this is > enough to get you going. Hope it helps. More smarter coder types can > probably chime in with better details along the way. > Thank you for your reply. However there is no 'configure' script included. And the instructions from the readme are: Install: use: make or: g++ main.cpp -o apligen Cheers, Drew