AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
October 1994

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



Valid HTML 4.01!



Thread

1994.10.21 11:05 "strtoul", by Harry Schreurs
1994.10.21 19:03 "Re: strtoul", by Sam Leffler
1994.10.21 21:38 "Re: strtoul", by Niles Ritter

1994.10.21 11:05 "strtoul", by Harry Schreurs

Starting with 3.3beta21 the `strtoul' library call is being used.
My host however doesn't have support for this call.

    Host:       Sun 3/50; SUNOS 4.1.1_U1
    Compiler:   gcc 2.6.0
    
Is my host becoming obsolete?


Starting with version 3.3beta15 `tiffcp' behaves differently from
previous versions!

I used to use `tiffcp' to convert multiple strip TIFF files into single 
strip TIFF files. For this to work I used:

        tiffcp src1 .. srcN dst

This worked like a charm. But this doesn't work anymore. :-(

I now have to use:

        tiffcp -rowsperstrip <large number> src1 .. srcN dst

where <large number> is equal to the Image Length.
 
In the source code I couldn't detect any significant change.
What's going on?

Harry Schreurs

------------------------------------------------------------------------------
H.L Schreurs                                            Email: hls@oce.nl
Business Unit Printing Systems                          Phone: +31 77 593775
Oce Nederland B.V.                                      Fax:   +31 77 595434
The Netherlands
   
            `Copying an printing with the simple touch of genius' 
------------------------------------------------------------------------------



      ###########################################################
      #  This note does not necessarily represent the position  #
      #     of Oce-Nederland B.V. Therefore no liability or     #
      #      responsibility for whatever will be accepted.      #
      ###########################################################