To: gopher@complete.org, rhahn@golden.net
Subject: [gopher] Re: Can't build Gopher on Mac OS X
References: <430FB234-0ED8-11D6-9A05-003065663F8C@golden.net>
From: John Goerzen <jgoerzen@complete.org>
Date: 22 Jan 2002 08:39:04 -0500
In-Reply-To: <430FB234-0ED8-11D6-9A05-003065663F8C@golden.net>
Message-ID: <87u1teec93.fsf@complete.org>
Lines: 60
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp)
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


Robert,

Thanks for the information.  What we'll need to track this down is:

 * A build log
 * Copies of config.cache, config.h, and config.status from the build
   directory

You may mail these to me directly.

You can create a build log by running:

script ~/logfile
./configure
make
exit

and then send me ~/logfile.

-- John

Robert Hahn <rhahn@golden.net> writes:

> Hi, guys
> 
> I saw a mention of Gopher's 10th birthday on Slashdot, and wanted to 
> download it and try it for myself.  Thus far, it doesn't work, but I'm 
> not willing to give up just yet.
> 
> However, I'm just learning how to program in C, and I have about 'zip' 
> experience with modifying configure scripts and makefiles to get it to 
> compile successfully.  I hope there will be someone here to help me.
> 
> Basically, when I type make, a whole whack (yes that's a technical term) 
> of "warning: implicit declaration of function"'s come up for function 
> calls like malloc() and free().  And, when I check the output of 
> ./configure, indeed it can't find a couple of .h files that are 
> definitely present (like malloc.h)
> 
> So, anyway, the make process dies trying to compile GSgopherobj.c during 
> the preprocessing stage.  Which obviously is a different problem, but 
> even if it didn't die there, I'm sure my program would have been 
> non-functional due to the problems described in the earlier paragraph.
> 
> So:  I've looked through the archives, and it looks to me that you're 
> generally helpful, provided that the newbies give you enough 
> information.  What do you need from me to help you figure out what's 
> going on?  This is the first unixy package I've tried to compile that 
> Didn't Work (out of about I think 3 in total, personal projects 
> notwithstanding), and I'm willing to roll up my sleeves to see what's 
> involved in getting it to work.  Odds are, these kinds of issues will 
> crop up in other software packages too.
> 
> Thanks in advance!
> -rh
> 
> 

-- 
John Goerzen <jgoerzen@complete.org>    GPG: 0x8A1D9A1F    www.complete.org