Re: [MiNT] libjpeg

[Peter Slegg <p.slegg@scubadivers.co.uk>]

On Tue, 15 Jun 2010 16:26:27 , Miro Kropacek <miro.kropacek@gmail.com> wrote:
> > http://bugs.php.net/bug.php?id=18617
> >
> > Thisexplains the same sort of problem. Maybe the config log
> > would explain why it happens in libjpeg.
> Peter, you can't google for errors/warnings like that :) You can look
> for meaning but actual cause depends from situation to situation.

Yes I know but you usually learn something or gain an insight into
were the error might lie. I have tracked down thousands of issues
this way and usually a lot faster than struggling along on my own.

> As others already mentioned, it could be either INT16 is equal to
> nothing, i.e. your expression becomes "typedef short;" or it's already
> defined as short, i.e. your expression becomes "typedef short short;".
> And maybe there's even 3rd option, who knows. In all cases, you must
> take a look if some other part of your source base didn't define it
> already -- it can be HW, other header which HW includes before your
> libjpeg header (very possible) or maybe even badly configured libjpeg
> (marked as "don't have INT16" but it does in fact).

Without an IDE it is like looking for the proverbial needle in
a haystack ;-)  I have been resorting to Suji to search folders
for the offending items.

> You can easily
> start with line "INT16 xxx = 1000" before the line where your warning
> occurs -- this will tell you if INT16 is already defined. If so, just
> search where it is.

Vincent wrote:
>When there is an unexplainable compilation problem,
>look at the preprocessor output:
>
>look at the gcc command in the makefile output,
>replace -c by -E and change the name of the output file.

I did find this in my searching which was helpful:

http://tigcc.ticalc.org/doc/comopts.html

I would like to see a Mint wiki with some hint and tips for
porting stuff.

The makefiles can be huge and not easy if you aren't familiar
with them.

Peter