Received: with LISTAR (v1.0.0; list gopher); Mon, 21 Jan 2002 20:38:26 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from sodium.golden.net (sodium.golden.net [199.166.210.252]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id B6ECC3B80B for ; Mon, 21 Jan 2002 20:38:25 -0500 (EST) Received: from localhost (AS53-05-165.cas-kit.golden.net [209.226.188.165]) by sodium.golden.net (8.10.1/8.10.1) with ESMTP id g0M1cNe18539 for ; Mon, 21 Jan 2002 20:38:24 -0500 (EST) Date: Mon, 21 Jan 2002 20:35:05 -0500 Subject: [gopher] Can't build Gopher on Mac OS X Content-type: text/plain; charset=US-ASCII Mime-Version: 1.0 (Apple Message framework v480) From: Robert Hahn To: gopher@complete.org Content-Transfer-Encoding: 8bit In-Reply-To: <87pu43g046.fsf@complete.org> Message-Id: <430FB234-0ED8-11D6-9A05-003065663F8C@golden.net> X-Mailer: Apple Mail (2.480) X-archive-position: 373 X-listar-version: Listar v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: rhahn@golden.net Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Listar version 1.0.0 X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher 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