Re: Problems with libtiff!

Re: Problems with libtiff!

[Earnie Boyd]

--- "Suhaib M. Siddiqi" <ssiddiqi@ipass.net> wrote:
> 
> 
> > "Suhaib M. Siddiqi" wrote:
> >
> > > that is where the problem is, at least i noticed.
> >
> > glad to see that I'm not alone...
> >
> > > if you unmount the disk then binary mount it
> > >
> > > umount /
> > > mount -b c: /
> > >
> >
> > For now, I do not know what this command sequence does
> > but I will try to verify this and examine if the created
> > headers are ok.
> >
> 
> This command sequence will unmount your C:\ drive, which is text! mounted by
> default
> and then binary mount it.
> 
> 
> >
> > > That's what I meant that someone needs to port Tiff properly the
> precompiled
> > > binaries available
> > > from Cygwin users have the above mentioned problems.  I have tried
> almost
> > > all the precompiled
> > > Tiff binaries available on net from different porters and all of them
> have
> > > this problem.
> >
> > I wonder now why this is not mentioned in the mailing list archives?
> > Maybe libtiff does work on their computers?
> 
> I do not know about thier *computers*.  Maybe they are using the binary
> mounted disks.
> The prefered way of having a text! mounted disk.
> 
> I know a few other users who have complain about the similar problems to me
> via
> personal comunications.  So, it is not you or me only, i guess a lot of
> other Cygwin users.

This is caused by lazy porting.  Lazy porting is relying in the default
processing mode for a file.  CAUTION: If you change to binary mounts you will
need to remove all \r characters from the line endings of all scripts.
===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't include me)
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[Suhaib M. Siddiqi, Ph.D.]

> 
> This is caused by lazy porting.  Lazy porting is relying in the default
> processing mode for a file.  CAUTION: If you change to binary mounts you will
> need to remove all \r characters from the line endings of all scripts.

That is why I do not like binary mounts.  Well, I decided to avoid
using tiff libs available for Cygwin from different users. Not going
to say by name, but all the 3 ports I know of available from UK and US
sites have this problem. 

Suhaib


> ===
> Earnie Boyd < mailto:earnie_boyd@yahoo.com >
> 
> Newbies, please visit
> < http://www.freeyellow.com/members5/gw32/index.html >
> 
> (If you respond to the list, then please don't include me)
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[itz]

   Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
   Precedence: bulk
   Sender: cygwin-owner@sourceware.cygnus.com
   Delivered-To: mailing list cygwin@sourceware.cygnus.com
   Date: Fri, 18 Jun 1999 11:14:08 -0400
   From: "Suhaib M. Siddiqi, Ph.D." <ssiddiqi@inspirepharm.com>
   Reply-To: ssiddiqi@inspirepharm.com
   Organization: Inspire Pharmaceuticals, Inc.
   X-Mailer: Mozilla 4.07C-SGI [en] (X11; I; IRIX64 6.5 IP28)
   MIME-Version: 1.0
   CC: cygwin@sourceware.cygnus.com
   References: < 19990618145838.11856.rocketmail@send205.yahoomail.com >
   Content-Type: text/plain; charset=us-ascii
   Content-Transfer-Encoding: 7bit

   >  This is caused by lazy porting.  Lazy porting is relying in the
   > default processing mode for a file.  CAUTION: If you change to
   > binary mounts you will need to remove all \r characters from the
   > line endings of all scripts.

   That is why I do not like binary mounts.  

But this is a development problem, not a usage one.  Yes, developers
and porters should be much more careful about their f?open() calls.
But where users are concerned, I find it hard to use text mounts (and
recommend them to other users) when even the most important program of
them all (bash) is not yet binary/text clean.

-- 
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324
San Francisco, California 94107
U.S.A.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[Earnie Boyd]

--- "Suhaib M. Siddiqi" <ssiddiqi@ipass.net> wrote:
> 
> 
> > "Suhaib M. Siddiqi" wrote:
> >
> > > that is where the problem is, at least i noticed.
> >
> > glad to see that I'm not alone...
> >
> > > if you unmount the disk then binary mount it
> > >
> > > umount /
> > > mount -b c: /
> > >
> >
> > For now, I do not know what this command sequence does
> > but I will try to verify this and examine if the created
> > headers are ok.
> >
> 
> This command sequence will unmount your C:\ drive, which is text! mounted by
> default
> and then binary mount it.
> 
> 
> >
> > > That's what I meant that someone needs to port Tiff properly the
> precompiled
> > > binaries available
> > > from Cygwin users have the above mentioned problems.  I have tried
> almost
> > > all the precompiled
> > > Tiff binaries available on net from different porters and all of them
> have
> > > this problem.
> >
> > I wonder now why this is not mentioned in the mailing list archives?
> > Maybe libtiff does work on their computers?
> 
> I do not know about thier *computers*.  Maybe they are using the binary
> mounted disks.
> The prefered way of having a text! mounted disk.
> 
> I know a few other users who have complain about the similar problems to me
> via
> personal comunications.  So, it is not you or me only, i guess a lot of
> other Cygwin users.

This is caused by lazy porting.  Lazy porting is relying in the default
processing mode for a file.  CAUTION: If you change to binary mounts you will
need to remove all \r characters from the line endings of all scripts.
===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't include me)
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[Suhaib M. Siddiqi, Ph.D.]

> 
> This is caused by lazy porting.  Lazy porting is relying in the default
> processing mode for a file.  CAUTION: If you change to binary mounts you will
> need to remove all \r characters from the line endings of all scripts.

That is why I do not like binary mounts.  Well, I decided to avoid
using tiff libs available for Cygwin from different users. Not going
to say by name, but all the 3 ports I know of available from UK and US
sites have this problem. 

Suhaib


> ===
> Earnie Boyd < mailto:earnie_boyd@yahoo.com >
> 
> Newbies, please visit
> < http://www.freeyellow.com/members5/gw32/index.html >
> 
> (If you respond to the list, then please don't include me)
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[itz]

   Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
   Precedence: bulk
   Sender: cygwin-owner@sourceware.cygnus.com
   Delivered-To: mailing list cygwin@sourceware.cygnus.com
   Date: Fri, 18 Jun 1999 11:14:08 -0400
   From: "Suhaib M. Siddiqi, Ph.D." <ssiddiqi@inspirepharm.com>
   Reply-To: ssiddiqi@inspirepharm.com
   Organization: Inspire Pharmaceuticals, Inc.
   X-Mailer: Mozilla 4.07C-SGI [en] (X11; I; IRIX64 6.5 IP28)
   MIME-Version: 1.0
   CC: cygwin@sourceware.cygnus.com
   References: < 19990618145838.11856.rocketmail@send205.yahoomail.com >
   Content-Type: text/plain; charset=us-ascii
   Content-Transfer-Encoding: 7bit

   >  This is caused by lazy porting.  Lazy porting is relying in the
   > default processing mode for a file.  CAUTION: If you change to
   > binary mounts you will need to remove all \r characters from the
   > line endings of all scripts.

   That is why I do not like binary mounts.  

But this is a development problem, not a usage one.  Yes, developers
and porters should be much more careful about their f?open() calls.
But where users are concerned, I find it hard to use text mounts (and
recommend them to other users) when even the most important program of
them all (bash) is not yet binary/text clean.

-- 
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324
San Francisco, California 94107
U.S.A.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[Ulrich Koehler]

"Suhaib M. Siddiqi" wrote:

> that is where the problem is, at least i noticed.

glad to see that I'm not alone...

> if you unmount the disk then binary mount it
> 
> umount /
> mount -b c: /
> 

For now, I do not know what this command sequence does
but I will try to verify this and examine if the created
headers are ok.


> That's what I meant that someone needs to port Tiff properly the precompiled
> binaries available
> from Cygwin users have the above mentioned problems.  I have tried almost
> all the precompiled
> Tiff binaries available on net from different porters and all of them have
> this problem.

I wonder now why this is not mentioned in the mailing list archives?
Maybe libtiff does work on their computers?

Ulrich
Koehler

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Problems with libtiff!

[Ulrich Koehler]

Hello,

I browsed through the archives and there should be
no problems at all, but...

libtiff v3.4beta037 + cygwin B20.1

% sh configure --target=i586
% make

compiles without any errors on Win95b, AMD-K6-2.

execution problems:

tools/tiffdump.exe - works ok
tools/tiff2ps.exe  - does not work, probs with strip-size
tools/thumbnail.exe - does not work,
  the thumbnail image is 8 byte in size (just the header)
  I guess libtiff is unable to read my greyscale image
  which I created with libtiff on a UNIX-system.
  (the images is ok, a hex-dump shows this)
and so on...

If I save images with my own program via libtiff
(on UNIX everything works well) the TIFF-images
are corrupt. The hex dump of the image shows:
- byte ordering and the first 4 bytes (0..3) of the header
  seem to be ok.
- the pointer to the first IFD (Byte 4..7) misses the real IFD
  by one byte. If I fix this manually the image is recognized
  by other programs (type, size etc. are correct) but the data
  is still corrupt.
???

Does anybody got a _working_ libtiff on Win95?

Bye
Ulrich Koehler

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[Suhaib M. Siddiqi]

> "Suhaib M. Siddiqi" wrote:
>
> > that is where the problem is, at least i noticed.
>
> glad to see that I'm not alone...
>
> > if you unmount the disk then binary mount it
> >
> > umount /
> > mount -b c: /
> >
>
> For now, I do not know what this command sequence does
> but I will try to verify this and examine if the created
> headers are ok.
>

This command sequence will unmount your C:\ drive, which is text! mounted by
default
and then binary mount it.


>
> > That's what I meant that someone needs to port Tiff properly the
precompiled
> > binaries available
> > from Cygwin users have the above mentioned problems.  I have tried
almost
> > all the precompiled
> > Tiff binaries available on net from different porters and all of them
have
> > this problem.
>
> I wonder now why this is not mentioned in the mailing list archives?
> Maybe libtiff does work on their computers?

I do not know about thier *computers*.  Maybe they are using the binary
mounted disks.
The prefered way of having a text! mounted disk.

I know a few other users who have complain about the similar problems to me
via
personal comunications.  So, it is not you or me only, i guess a lot of
other Cygwin users.

Suhaib

>
> Ulrich
> Koehler
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[Earnie Boyd]

--- itz@lbin.com wrote:
-8<-
> But this is a development problem, not a usage one.  Yes, developers
> and porters should be much more careful about their f?open() calls.
> But where users are concerned, I find it hard to use text mounts (and
> recommend them to other users) when even the most important program of
> them all (bash) is not yet binary/text clean.

If you believe that bash has problems with binary/text then the best solution
would be to find the problems and submit a patch.  BTW, IMO it is readline that
has the problem and not bash.  I've been using cygwin for a couple of years now
processing with text default mounts and the only problem I've seen with bash is
the initialization of the history buffer from the history file.

Changing from a default of text mode processing to a default of binary mode
processing only changes the cause of the headaches.  You still must properly
port the code.  For truly portable code you must specify how the file is to be
processed before it's processed.  DON'T DEPEND ON DEFAULTS.

===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't include me)
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[Suhaib M. Siddiqi]

> Hello,
>
> I browsed through the archives and there should be
> no problems at all, but...
>
> libtiff v3.4beta037 + cygwin B20.1
>
> % sh configure --target=i586
> % make
>
> compiles without any errors on Win95b, AMD-K6-2.

Yes, it compiles without errors.

>
> execution problems:
>
> tools/tiffdump.exe - works ok
> tools/tiff2ps.exe  - does not work, probs with strip-size
> tools/thumbnail.exe - does not work,
>   the thumbnail image is 8 byte in size (just the header)
>   I guess libtiff is unable to read my greyscale image
>   which I created with libtiff on a UNIX-system.
>   (the images is ok, a hex-dump shows this)
> and so on...

that is where the problem is, at least i noticed.
if you unmount the disk then binary mount it

umount /
mount -b c: /

Now your tiff images created on UNIX can be read, also tiff images created
under Cygwin
will not have header problems and can be opened with Photoshop and/or MS
Wang Image Editor.

That's what I meant that someone needs to port Tiff properly the precompiled
binaries available
from Cygwin users have the above mentioned problems.  I have tried almost
all the precompiled
Tiff binaries available on net from different porters and all of them have
this problem.

--Suhaib

>
> If I save images with my own program via libtiff
> (on UNIX everything works well) the TIFF-images
> are corrupt. The hex dump of the image shows:
> - byte ordering and the first 4 bytes (0..3) of the header
>   seem to be ok.
> - the pointer to the first IFD (Byte 4..7) misses the real IFD
>   by one byte. If I fix this manually the image is recognized
>   by other programs (type, size etc. are correct) but the data
>   is still corrupt.
> ???
>
> Does anybody got a _working_ libtiff on Win95?
>
> Bye
> Ulrich Koehler
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[Earnie Boyd]

--- itz@lbin.com wrote:
-8<-
> But this is a development problem, not a usage one.  Yes, developers
> and porters should be much more careful about their f?open() calls.
> But where users are concerned, I find it hard to use text mounts (and
> recommend them to other users) when even the most important program of
> them all (bash) is not yet binary/text clean.

If you believe that bash has problems with binary/text then the best solution
would be to find the problems and submit a patch.  BTW, IMO it is readline that
has the problem and not bash.  I've been using cygwin for a couple of years now
processing with text default mounts and the only problem I've seen with bash is
the initialization of the history buffer from the history file.

Changing from a default of text mode processing to a default of binary mode
processing only changes the cause of the headaches.  You still must properly
port the code.  For truly portable code you must specify how the file is to be
processed before it's processed.  DON'T DEPEND ON DEFAULTS.

===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't include me)
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[Suhaib M. Siddiqi]

> "Suhaib M. Siddiqi" wrote:
>
> > that is where the problem is, at least i noticed.
>
> glad to see that I'm not alone...
>
> > if you unmount the disk then binary mount it
> >
> > umount /
> > mount -b c: /
> >
>
> For now, I do not know what this command sequence does
> but I will try to verify this and examine if the created
> headers are ok.
>

This command sequence will unmount your C:\ drive, which is text! mounted by
default
and then binary mount it.


>
> > That's what I meant that someone needs to port Tiff properly the
precompiled
> > binaries available
> > from Cygwin users have the above mentioned problems.  I have tried
almost
> > all the precompiled
> > Tiff binaries available on net from different porters and all of them
have
> > this problem.
>
> I wonder now why this is not mentioned in the mailing list archives?
> Maybe libtiff does work on their computers?

I do not know about thier *computers*.  Maybe they are using the binary
mounted disks.
The prefered way of having a text! mounted disk.

I know a few other users who have complain about the similar problems to me
via
personal comunications.  So, it is not you or me only, i guess a lot of
other Cygwin users.

Suhaib

>
> Ulrich
> Koehler
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[Ulrich Koehler]

"Suhaib M. Siddiqi" wrote:

> that is where the problem is, at least i noticed.

glad to see that I'm not alone...

> if you unmount the disk then binary mount it
> 
> umount /
> mount -b c: /
> 

For now, I do not know what this command sequence does
but I will try to verify this and examine if the created
headers are ok.


> That's what I meant that someone needs to port Tiff properly the precompiled
> binaries available
> from Cygwin users have the above mentioned problems.  I have tried almost
> all the precompiled
> Tiff binaries available on net from different porters and all of them have
> this problem.

I wonder now why this is not mentioned in the mailing list archives?
Maybe libtiff does work on their computers?

Ulrich
Koehler

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problems with libtiff!

[Suhaib M. Siddiqi]

> Hello,
>
> I browsed through the archives and there should be
> no problems at all, but...
>
> libtiff v3.4beta037 + cygwin B20.1
>
> % sh configure --target=i586
> % make
>
> compiles without any errors on Win95b, AMD-K6-2.

Yes, it compiles without errors.

>
> execution problems:
>
> tools/tiffdump.exe - works ok
> tools/tiff2ps.exe  - does not work, probs with strip-size
> tools/thumbnail.exe - does not work,
>   the thumbnail image is 8 byte in size (just the header)
>   I guess libtiff is unable to read my greyscale image
>   which I created with libtiff on a UNIX-system.
>   (the images is ok, a hex-dump shows this)
> and so on...

that is where the problem is, at least i noticed.
if you unmount the disk then binary mount it

umount /
mount -b c: /

Now your tiff images created on UNIX can be read, also tiff images created
under Cygwin
will not have header problems and can be opened with Photoshop and/or MS
Wang Image Editor.

That's what I meant that someone needs to port Tiff properly the precompiled
binaries available
from Cygwin users have the above mentioned problems.  I have tried almost
all the precompiled
Tiff binaries available on net from different porters and all of them have
this problem.

--Suhaib

>
> If I save images with my own program via libtiff
> (on UNIX everything works well) the TIFF-images
> are corrupt. The hex dump of the image shows:
> - byte ordering and the first 4 bytes (0..3) of the header
>   seem to be ok.
> - the pointer to the first IFD (Byte 4..7) misses the real IFD
>   by one byte. If I fix this manually the image is recognized
>   by other programs (type, size etc. are correct) but the data
>   is still corrupt.
> ???
>
> Does anybody got a _working_ libtiff on Win95?
>
> Bye
> Ulrich Koehler
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Problems with libtiff!

[Ulrich Koehler]

Hello,

I browsed through the archives and there should be
no problems at all, but...

libtiff v3.4beta037 + cygwin B20.1

% sh configure --target=i586
% make

compiles without any errors on Win95b, AMD-K6-2.

execution problems:

tools/tiffdump.exe - works ok
tools/tiff2ps.exe  - does not work, probs with strip-size
tools/thumbnail.exe - does not work,
  the thumbnail image is 8 byte in size (just the header)
  I guess libtiff is unable to read my greyscale image
  which I created with libtiff on a UNIX-system.
  (the images is ok, a hex-dump shows this)
and so on...

If I save images with my own program via libtiff
(on UNIX everything works well) the TIFF-images
are corrupt. The hex dump of the image shows:
- byte ordering and the first 4 bytes (0..3) of the header
  seem to be ok.
- the pointer to the first IFD (Byte 4..7) misses the real IFD
  by one byte. If I fix this manually the image is recognized
  by other programs (type, size etc. are correct) but the data
  is still corrupt.
???

Does anybody got a _working_ libtiff on Win95?

Bye
Ulrich Koehler

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com