From mint-bounce@lists.fishpool.fi Tue Jun 15 08:21:09 2010 To: Subject: Re: [MiNT] libjpeg MIME-Version: 1.0 Date: Tue, 15 Jun 2010 14:18:23 +0200 From: m0n0 Reply-To: ole@monochrom.net In-Reply-To: <000d6add.01b8d262a74d@smtp.freeola.net> References: <000d6add.01b8d262a74d@smtp.freeola.net> Message-ID: <00128fa5201e068cbd7e9bc14fd918c4-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUBFBDBTXF5bVkYBWUF3BFY6XF1YR0MCW1lZQw==-webmailer2@server04.webmailer.hosteurope.de> X-Sender: ole@monochrom.net User-Agent: Host Europe Webmailer/2.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 X-HE-Access: Yes X-bounce-key: webpack.hosteurope.de;ole@monochrom.net;1276604310;4a122430; X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: ole@monochrom.net Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Am Dienstag, den 15.06.2010, 11:53 +0200 schrieb Peter Slegg : > On Tue, 15 Jun 2010 12:43:35 , Miro Kropacek > wrote: >> > In file included from /usr/include/jpeglib.h:27, >> > á á á á á á á á from p_about.c:31: >> > /usr/include/jmorecfg.h:156: warning: empty declaration >> > make: *** [obj.040/p_about.o] Error 1 >> It this is only error message, I suspect -Werror is used (i.e. >> interpret warning as errors). >> >> > The offending line is the typedef: >> > >> > /* INT16 must hold at least the values -32768..32767. */ >> > >> > #ifndef XMD_H á á á á á á/* X11/xmd.h correctly defines INT16 >> */ >> > typedef short INT16; >> > #endif >> > >> > >> > I suspect this might not be needed but suggestions welcomed. >> Well, you shouldn't change official headers (in /usr/include). So >> either inspect why you get this warning in source code (gcc4, i.e. >> strict compiler for example) or remove -Werror flag from Highwire as >> temporary solution. >> > > As a temporary solution I added -DXMD_H to the gcc def options > in the HW makefile. So this "fix" would just leave the INT16 undefined. I don't know the libjpeg - but does it really depend on X11 code? If so, there is probably an way to disable these parts of libjpeg. Did you executed "./configure --help" or something like that to see witch options are available? Maybe there is something like, for example: --disable-x11-stuff )