AWARE [SYSTEMS]
AWare Systems, , Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
June 2017

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



New Datamatrix section



Valid HTML 4.01!



Thread

2017.06.01 15:24 "TIFF printf warnings", by Aaron Boxer
2017.06.01 16:15 "Re: TIFF printf warnings", by Even Rouault
2017.06.01 17:03 "Re: TIFF printf warnings", by Bob Friesenhahn
2017.06.01 18:54 "Re: TIFF printf warnings", by Aaron Boxer
2017.06.02 20:05 "Re: TIFF printf warnings", by Roger Leigh
2017.06.03 00:19 "Re: TIFF printf warnings", by Aaron Boxer

2017.06.03 00:19 "Re: TIFF printf warnings", by Aaron Boxer

On Fri, Jun 2, 2017 at 4:05 PM, Roger Leigh <rleigh@codelibre.net> wrote:

> On 01/06/2017 18:54, Aaron Boxer wrote:
> >
> > On Thu, Jun 1, 2017 at 1:03 PM, Bob Friesenhahn
> > <bfriesen@simple.dallas.tx.us <mailto:bfriesen@simple.dallas.tx.us>>
> wrote:
> >
> >     On Thu, 1 Jun 2017, Aaron Boxer wrote:
> >
> >         Hi Folks,
> >
> >         I am getting the following warnings when building libtiff on 64
> >         bit Ubuntu
> >         with a C++ project with g++ warning level turned up:
> >
> >
> >     It seems like configure or cmake got the TIFF_UINT64_FORMAT
> >     definition incorrect.  Did you configure your build using
> >     'configure' or 'cmake'?
> >
> >
> >
> > Thanks! Yes, that was it. I am using cmake,
> > but my libtiff cmake file has diverged from standard file.
> > Just need to change %llu to %lu.
>
> Just to double check, there's nothing which we need to fix in the CVS
> copy of CMakeLists.txt?
>
> Are there any changes you have made which need integrating?  Or anything
> you've encountered which you would like improving?
>
>

Thanks for following up, Roger. No, you guys don't need to change anything.
It was my problem : the libtiff cmake file for my project is, I guess,
quite old, and I hadn't been
updating it with the latest changes from the project. It's all good now.

Cheers,
Aaron