Date: Tue, 14 Oct 1997 10:42:06 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Johan Romin - SP3B <sp95joro AT Katedral DOT SE>
cc: djgpp AT delorie DOT com
Subject: Re: HELP WITH MIKMOD NEEDED
In-Reply-To: <Pine.GSO.3.96.971013182842.16063A-300000@Calcitratus.Katedral.SE>
Message-ID: <Pine.SUN.3.91.971014104147.14214B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 13 Oct 1997, Johan Romin - SP3B wrote:

> MikMod is driving me nuts. It won't link. I've attached both the output of
> the make session and the makefile. My test program is almost a copy of the
> mikmod example program. My BIG problem is that I get a error message about
> undefined references to the mikmod functions.
> If someone can help me I would be very greatful
> By the way I use mikmod 2.09b
> 
> 	/Johan
> 
> ---559023410-851401618-876760298=:16063
> Content-Type: TEXT/PLAIN; charset=US-ASCII; name="GCC.LOG"
> Content-Transfer-Encoding: BASE64
> Content-ID: <Pine DOT GSO DOT 3 DOT 96 DOT 971013183138 DOT 16063B AT Calcitratus DOT Katedral DOT SE>
> Content-Description: 
> 
> Z2NjIC1zIC1PMyAtbTQ4NiBtaWsuY2Mgc3RhcnMuY2MgZ2Z4Y21kLmNjIG1h
> aW4uY2MgaHBsYXMuY2MgYnJhaW4uY2MgLW8gZGVtIGxvYWRfeG0ubyBkcnZf

Please be advised that when posting requests to help you overcome such
problems, it is MUCH better to include error messages and short
programs as plain ASCI text, not as MIME-encoded attachments.  Many
people read the messages with mailers that don't automatically decode
the attachments and cannot be bothered to go to great lengths just to
see what is it that you are complaining about.  So you lose their
potential help.

I know that many mailers will automatically MIME-encode any
attachment.  Please find a way to convince your mailer not to encode,
if you want more efficient help.  (Usually, there should be some
command for including an external text file in your message.)