Re: Bug#23618: debmake: debstd corrupts .a files!

1998-06-19 Thread John Goerzen
repoen 23618
stop

I'm sorry, but saying that I should not use debmake because it is
buggy does not fix the bug and the bug should not be closed!

Corrupting files in packages that I am building is very serious
indeed, and if I didn't set the severity to important or greater, I
probably should have.  debstd issues no warnings about it, and it took 
me several hours to figure out the problem, since this is a package
with a source tree of over 100 megs and each rebuild takes in excess
of 30 minutes.  (Not only that, but the install method is complex and
I looked everywhere else first, assuming that it could not possibly
be debstd)

Santiago Vila [EMAIL PROTECTED] writes:

 debstd is not supposed to guess that. stripping a library using
 just strip --strip-debug is ok for 95% of cases, if your case is in the
 remaining 5%, then the debstd provided by debmake is not suitable for your
 package. I would suggest either:
 
 a) debstd-ize your debian/rules

Eh?  debian/rules already uses debstd.

 b) copy debstd to your debian directory and change the debstd invocation
 by debian/debstd (probably adding a chmod +x debian/debstd in the build
 target). Then you can fine-tune your own debstd according to the special
 requirements of your package.

OK, this could be a possibility then -- comment out that part.  But
still, I don't think it's a good solution to require me to hack the
source.  Further, there is no documentation anywhere that indicates
that debstd may corrupt files.

 I do not consider this to be a bug in debstd.

You are welcome to reassign it to the appropriate package (binutils?)
then, but it is not fixed and should not be closed.


-- 
John Goerzen   Linux, Unix consulting  programming   [EMAIL PROTECTED] |
Developer, Debian GNU/Linux (Free powerful OS upgrade)   www.debian.org |
+
Visit the Air Capitol Linux Users Group on the web at http://www.aclug.org


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#23618: debmake: debstd corrupts .a files!

1998-06-19 Thread Santiago Vila
-BEGIN PGP SIGNED MESSAGE-

I will repeat what I said:

debstd is not supposed to guess that your static library is in coff
format, because normal libraries in Linux are ELF. stripping a library
using just strip --strip-debug is ok for 95% of cases, if your case is in the
remaining 5%, then the debstd provided by debmake, as is, is not suitable
for your package.

I would like to add that there are two different issues here:

1. You didn't know that debstd does strip --strip-debug on static
libraries. By reading debstd(1), I realize that this may be a
documentation bug in debmake, if you like. In such case I can retitle
this bug to something like debstd behaviour is not fully documented and
add a phrase saying debstd strips static libraries in the man page. Ok?

2. Normal strip seems to mess up a coff library. This is a completely
different issue. If you think this is a bug in binutils, submit a bug
against binutils.

-BEGIN PGP SIGNATURE-
Version: 2.6.3ia
Charset: latin1

iQCVAgUBNYq2XCqK7IlOjMLFAQEyPQP/W5ydMmQqHu52kWqt4hAH3zp2V7vqzpEx
GoNuUK9/N2pjwGjoYAalgIUeNXZ6o7H9F+85gfK0p/Ra07CUgxpDg4k0qG+ZwLDI
pL1oRyiFpP9iJRtVto1iLJbsbuAzzoQj7C1r4lOKlWpMPbDa1rMl7goNoFXcXaxL
FJyPqs2YSvM=
=4p2t
-END PGP SIGNATURE-


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#23618: debmake: debstd corrupts .a files!

1998-06-19 Thread John Goerzen
reopen 23618
reassign 23618 binutils
quit

Santiago Vila [EMAIL PROTECTED] writes:

 debstd is not supposed to guess that your static library is in coff
 format, because normal libraries in Linux are ELF. stripping a library
 using just strip --strip-debug is ok for 95% of cases, if your case is in the
 remaining 5%, then the debstd provided by debmake, as is, is not suitable
 for your package.

I would say that debstd should not touch that which it does not
understand.  This is perfectly reasonable.  It does not understand
coff, which is fine.  It should not touch it, though.  It so happens
that touching it reduces a package with 100 megs of source to less
usefulness than cat.

 2. Normal strip seems to mess up a coff library. This is a completely
 different issue. If you think this is a bug in binutils, submit a bug
 against binutils.

I have reassigned this one to binutils then.  Closing it is not
appropriate since the problem has not been dealt with.  Also, file
corruption is not a documentation issue only.

-- 
John Goerzen   Linux, Unix consulting  programming   [EMAIL PROTECTED] |
Developer, Debian GNU/Linux (Free powerful OS upgrade)   www.debian.org |
+
Visit the Air Capitol Linux Users Group on the web at http://www.aclug.org


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]