What you refer to as "uncommenting" is probably a mistake. A line
starting with a '#' is not a comment in C, but rather a pre-processor
directive. The HOSTNAME line should read like:
#define HOSTNAME "[my organisation]"
You can change the portion inside the quotes, but you shouldn't change
the rest of the line.
The analog.cfg file uses lines starting with a '#' as comments, but the
analhead.h file does not follow those conventions.
Good Luck
Jason
On 9/22/99 11:51 AM [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
>Thanks for such a quick reply...here are a few examples of the messages I
>get...
>
>Number 1 - This error set occured after I followed the instructions for
>editing the analhead.h file. THe only thing I changed was the "define
>HOSTNAME" I put a name in quotes on this line and un-commented it.
>
>
>gcc -O2 -DUNIX -c alias.c
>In file included from analhea2.h:227,
> from alias.c:9:
>analhead.h:19: parse error before `HOSTNAME'
>In file included from alias.c:9:
>analhea2.h:443: `INP_YEAR' undeclared here (not in a function)
>analhea2.h:597: `INP_CODE' undeclared here (not in a function)
>analhea2.h:603: `INP_CODE' undeclared here (not in a function)
>analhea2.h:605: `INP_CODE' undeclared here (not in a function)
>analhea2.h:606: `INP_CODE' undeclared here (not in a function)
>analhea2.h:1112: `INP_CODE' undeclared here (not in a function)
>analhea2.h:1112: warning: parameter has incomplete type
>alias.c: In function `do_alias':
>alias.c:22: `ITEM_FILE' undeclared (first use this function)
>alias.c:22: (Each undeclared identifier is reported only once
>alias.c:22: for each function it appears in.)
>alias.c:24: `ITEM_HOST' undeclared (first use this function)
>alias.c:26: `ITEM_REFERRER' undeclared (first use this function)
>alias.c:28: `ITEM_BROWSER' undeclared (first use this function)
>alias.c:30: `ITEM_VHOST' undeclared (first use this function)
>alias.c:32: `ITEM_USER' undeclared (first use this function)
>make: *** [alias.o] Error 1
>
>I have a feeling it has something to do with the analhead.h (or similar
>file) not being configured right.
>
>I have re-downloaded it twice...just to make sure my connection is not
>corrupting the file....just grasping at straws..
>
>Christopher
>
>On Tue, 21 Sep 1999, Jason Linhart wrote:
>
>> On 9/21/99 9:09 PM [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
>>
>> >I need help with compiling via gcc on a Solaris machine. Everytime i try
>> >to "make" analog, it fails. I have tried re-downloading 3 times, and
>> >re-taring 3-4 times of each. But everytime I get to the make stage I get
>> >a new error. Is there a known problem with the solaris (5.5.1) compiling
>> >of analog???
>>
>> We need to know what error messages you are getting. An error wouldn't
>> surprise me, but a different error each time means something is seriously
>> wrong.
-----------------
[EMAIL PROTECTED]
-----------------
Dr. Seuss books . . . can be read and enjoyed on several levels. For
example, 'One Fish Two Fish, Red Fish Blue Fish' can be deconstructed
as a searing indictment of the narrow-minded binary counting system.
-- Peter van der Linden, Expert C Programming, Deep C Secrets
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
