Eduard Bloch [EMAIL PROTECTED] wrote:
This is not related to my text above and mkisofs _does_ give an error
message.
The problem I was referring to above will cause that string options will
silently get wrong parameters. And BTW: getargs allows you to contol the
behavior - GNU
Eduard Bloch [EMAIL PROTECTED] wrote:
This is not related to my text above and mkisofs _does_ give an error
message.
The problem I was referring to above will cause that string options
will
silently get wrong parameters. And BTW: getargs allows you to contol
the
behavior - GNU
Package: mkisofs
Version: 4:2.01+01a03-5
Severity: normal
There is bug in options handling. It should not matter in which order
the options are given. See below for demonstation.
-rJf ERROR
-frJ ok
Hi Jari,
your problem is caused by a bug in the option parser (GNU
#include hallo.h
* Joerg Schilling [Tue, Dec 12 2006, 08:14:35PM]:
Package: mkisofs
Version: 4:2.01+01a03-5
Severity: normal
There is bug in options handling. It should not matter in which order
the options are given. See below for demonstation.
-rJf ERROR
-frJ ok
Eduard Bloch [EMAIL PROTECTED] wrote:
your problem is caused by a bug in the option parser (GNU getopt_long).
The mkisofs version you are using is very old ( 1.5 years). Three months
ago, mkisofs has been converted to use the more mature and older (starting
1982)
getargs(). This
#include hallo.h
* Joerg Schilling [Tue, Dec 12 2006, 10:48:59PM]:
Eduard Bloch [EMAIL PROTECTED] wrote:
your problem is caused by a bug in the option parser (GNU getopt_long).
The mkisofs version you are using is very old ( 1.5 years). Three months
ago, mkisofs has been converted
Package: mkisofs
Version: 4:2.01+01a03-5
Severity: normal
There is bug in options handling. It should not matter in which order
the options are given. See below for demonstation.
-rJf ERROR
-frJ ok
---
7 matches
Mail list logo
