Re: [Xpert] stripping X server modules on Alpha makes them unusable
On Fri, 8 Dec 2000, Christopher C. Chimelis wrote: While I've got you here, I've run into a problem with X -configure segfaulting in the s3virge driver. I haven't checked it lately (meaning in the past three weeks), so it might be fixed already (I'll check again tomorrow), but I wanted to see if you had heard of anything like this... Sorry, I don't keep up wth what happens with that driver. Stuart Stuart R. Anderson [EMAIL PROTECTED] Metro Link Incorporated South Carolina Office 5807 North Andrews Way 129 Secret Cove Drive Fort Lauderdale, Florida 33309 Lexington, SC 29072 voice: 954.660.2500 voice: 803.951.3630 fax: 954.938.1982 SkyTel: 800.405.3401 http://www.metrolink.com/
Re: [Xpert] stripping X server modules on Alpha makes them unusable
On Thu, 7 Dec 2000, Branden Robinson wrote: On Thu, Dec 07, 2000 at 02:27:22AM -0500, Christopher C. Chimelis wrote: Oh, while I'm on the subject, I really need that patch to the rules script incorporated for now. For some reason, whenever the modules in xserver-xfree86 are stripped on Alpha, it renders them unusable. The patch should allow strip to do it's job for all packages on every arch but Alpha, so it's safe (this has been tested with every revision thusfar, so it's still needed). Sorry, I didn't know that. I was just trying to protect myself from the Policy Nazis. I think the authors of the ELF loader for XFree86 would be very interested to know about this bug. I seemed to miss the patch mentioned, but my guess would be that it involves wether or not to pass -s to install? The modules that get loaded can't get completely stripped, or they loose the symbol relocation information which is required for loading. It is probably OK to strip out some other stuff like debugging info. I just peeked at the config file, and I don't see where -s is getting set. Is this a patch to another patch? Has the default behavior of install changed? Should I just wait for the coffee to kick in and then all this will make sense? Stuart Stuart R. Anderson [EMAIL PROTECTED] Metro Link Incorporated South Carolina Office 5807 North Andrews Way 129 Secret Cove Drive Fort Lauderdale, Florida 33309 Lexington, SC 29072 voice: 954.660.2500 voice: 803.951.3630 fax: 954.938.1982 SkyTel: 800.405.3401 http://www.metrolink.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Xpert] stripping X server modules on Alpha makes them unusable
On Thu, Dec 07, 2000 at 11:12:48AM -0500, Christopher C. Chimelis wrote: On Thu, 7 Dec 2000, Stuart Anderson wrote: I seemed to miss the patch mentioned, but my guess would be that it involves wether or not to pass -s to install? The modules that get loaded can't get completely stripped, or they loose the symbol relocation information which is required for loading. It is probably OK to strip out some other stuff like debugging info. I just peeked at the config file, and I don't see where -s is getting set. Is this a patch to another patch? Has the default behavior of install changed? Should I just wait for the coffee to kick in and then all this will make sense? Not really...it's not -s that's the problem, it's dh_strip. In the patch, I placed an ifeq in the rules file that made it so that, on Alpha, dh_strip is called with '-Nxserver-xfree86', but on other archs, it isn't. Stuart may not be familiar with the vagaries of Debian packaging. I build with debugging symbols enabled, but Debian Policy insists that they be stripped out when the package is generated. My completely uneducated guess is that something in module loader "knows" that debugging symbols are enabled and depends on this, so that when later this same code is run stripped, it becomes confused? -- G. Branden Robinson| We either learn from history or, Debian GNU/Linux | uh, well, something bad will happen. [EMAIL PROTECTED] | -- Bob Church http://deadbeast.net/~branden/ | PGP signature
Re: [Xpert] stripping X server modules on Alpha makes them unusable
On Thu, 7 Dec 2000, Branden Robinson wrote:
Stuart may not be familiar with the vagaries of Debian packaging.
I build with debugging symbols enabled, but Debian Policy insists that they
be stripped out when the package is generated.
My completely uneducated guess is that something in module loader "knows"
that debugging symbols are enabled and depends on this, so that when later
this same code is run stripped, it becomes confused?
Just as a note...
I don't know how other rpm based distributions did it, but in the rpms
I built, what I did was this:
%define __os_install_post %{___build_post}
in the top of the spec file, so that rpm post scripts will not insist in
strip everything.
and added this to the bottom of the %install
(set +x; strip %{buildroot}%{prefix}/bin/* || :)
(set +x; strip %{buildroot}%{prefix}/lib/lib*.so* || :)
--
G. Branden Robinson| We either learn from history or,
Debian GNU/Linux | uh, well, something bad will happen.
[EMAIL PROTECTED] | -- Bob Church
http://deadbeast.net/~branden/ |
Paulo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Xpert] stripping X server modules on Alpha makes them unusable
On Thu, Dec 07, 2000 at 01:25:40PM -0500, Stuart Anderson wrote: Where is dh_strip invoked? I don't see it in the XFree86 config files, so I'll assume it is run as part of te packagin process. Yes. It is run as part of the debian/rules makefile, which wraps the XFree86 make World and make install rules. Can it be told to removing debugging section, but leave the regular symbols alone, or does the policy require that all symbols be removed? Here's the relevant quote. Note that by default all installed binaries should be stripped, either by using the -s flag to install, or by calling strip on the binaries after they have been copied into debian/tmp but before the tree is made into a package. We know how to turn off stripping for Alpha, that's not the problem. The problem is why the loader is choking on stripped modules. We don't know. -- G. Branden Robinson|The errors of great men are venerable Debian GNU/Linux |because they are more fruitful than the [EMAIL PROTECTED] |truths of little men. http://deadbeast.net/~branden/ |-- Friedrich Nietzsche PGP signature
Re: [Xpert] stripping X server modules on Alpha makes them unusable
On Thu, 7 Dec 2000, Branden Robinson wrote: We know how to turn off stripping for Alpha, that's not the problem. The problem is why the loader is choking on stripped modules. We don't know. This loader is different from the libc loader in that it operates on the symbols that are used when linking an object (and are the ones that get stripped). This differ from the .so libraries that the libc loader uses. They have a .dynsym section which is still there even if the object gets stripped. What is the error message when it chokes? It is still puzzleing why it does something different on Alpha vs others. Maybe someone could run objdump --headers on Alpha x86 versions of the same modules so we can see if there are any interesting differences. Stuart Stuart R. Anderson [EMAIL PROTECTED] Metro Link Incorporated South Carolina Office 5807 North Andrews Way 129 Secret Cove Drive Fort Lauderdale, Florida 33309 Lexington, SC 29072 voice: 954.660.2500 voice: 803.951.3630 fax: 954.938.1982 SkyTel: 800.405.3401 http://www.metrolink.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Xpert] stripping X server modules on Alpha makes them unusable
On Thu, 7 Dec 2000, Stuart Anderson wrote: It is still puzzleing why it does something different on Alpha vs others. Maybe someone could run objdump --headers on Alpha x86 versions of the same modules so we can see if there are any interesting differences. While I've got you here, I've run into a problem with X -configure segfaulting in the s3virge driver. I haven't checked it lately (meaning in the past three weeks), so it might be fixed already (I'll check again tomorrow), but I wanted to see if you had heard of anything like this... C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Xpert] stripping X server modules on Alpha makes them unusable
On Thu, 7 Dec 2000, Branden Robinson wrote: On Thu, Dec 07, 2000 at 02:27:22AM -0500, Christopher C. Chimelis wrote: Oh, while I'm on the subject, I really need that patch to the rules script incorporated for now. For some reason, whenever the modules in xserver-xfree86 are stripped on Alpha, it renders them unusable. The patch should allow strip to do it's job for all packages on every arch but Alpha, so it's safe (this has been tested with every revision thusfar, so it's still needed). Sorry, I didn't know that. I was just trying to protect myself from the Policy Nazis. I think the authors of the ELF loader for XFree86 would be very interested to know about this bug. I seemed to miss the patch mentioned, but my guess would be that it involves wether or not to pass -s to install? The modules that get loaded can't get completely stripped, or they loose the symbol relocation information which is required for loading. It is probably OK to strip out some other stuff like debugging info. I just peeked at the config file, and I don't see where -s is getting set. Is this a patch to another patch? Has the default behavior of install changed? Should I just wait for the coffee to kick in and then all this will make sense? Stuart Stuart R. Anderson [EMAIL PROTECTED] Metro Link Incorporated South Carolina Office 5807 North Andrews Way 129 Secret Cove Drive Fort Lauderdale, Florida 33309 Lexington, SC 29072 voice: 954.660.2500 voice: 803.951.3630 fax: 954.938.1982 SkyTel: 800.405.3401 http://www.metrolink.com/
Re: [Xpert] stripping X server modules on Alpha makes them unusable
On Thu, Dec 07, 2000 at 01:25:40PM -0500, Stuart Anderson wrote: Where is dh_strip invoked? I don't see it in the XFree86 config files, so I'll assume it is run as part of te packagin process. Yes. It is run as part of the debian/rules makefile, which wraps the XFree86 make World and make install rules. Can it be told to removing debugging section, but leave the regular symbols alone, or does the policy require that all symbols be removed? Here's the relevant quote. Note that by default all installed binaries should be stripped, either by using the -s flag to install, or by calling strip on the binaries after they have been copied into debian/tmp but before the tree is made into a package. We know how to turn off stripping for Alpha, that's not the problem. The problem is why the loader is choking on stripped modules. We don't know. -- G. Branden Robinson|The errors of great men are venerable Debian GNU/Linux |because they are more fruitful than the [EMAIL PROTECTED] |truths of little men. http://deadbeast.net/~branden/ |-- Friedrich Nietzsche pgpy4KScmValB.pgp Description: PGP signature
Re: [Xpert] stripping X server modules on Alpha makes them unusable
On Thu, 7 Dec 2000, Stuart Anderson wrote: This loader is different from the libc loader in that it operates on the symbols that are used when linking an object (and are the ones that get stripped). This differ from the .so libraries that the libc loader uses. They have a .dynsym section which is still there even if the object gets stripped. Ok, that'll help me track it down. There is a problem with objcopy/strip that I'm trying to track down (I'm the binutils maintainer for Debian, incidentally), so that may be involved as well. What is the error message when it chokes? I'll dig out an old log and forward it to the list. I don't have the message handy right now and am running too many package builds to start X right now. It is still puzzleing why it does something different on Alpha vs others. Maybe someone could run objdump --headers on Alpha x86 versions of the same modules so we can see if there are any interesting differences. Will do...now that I have an x86 around here, it'll be easy to compare... C
Re: [Xpert] stripping X server modules on Alpha makes them unusable
On Thu, 7 Dec 2000, Stuart Anderson wrote: It is still puzzleing why it does something different on Alpha vs others. Maybe someone could run objdump --headers on Alpha x86 versions of the same modules so we can see if there are any interesting differences. While I've got you here, I've run into a problem with X -configure segfaulting in the s3virge driver. I haven't checked it lately (meaning in the past three weeks), so it might be fixed already (I'll check again tomorrow), but I wanted to see if you had heard of anything like this... C
