Re: [Cooker] /usr/lib/i686
Ouch. Okay, let me rephrase that... Has anyone here ever taken a regular application with one dynamic library, and built an RPM with both i586 and i686/mmx libraries? Austin -- Austin Acton Hon.B.Sc. Synthetic Organic Chemist, Teaching Assistant Department of Chemistry, York University, Toronto MandrakeClub Volunteer (www.mandrakeclub.com) homepage: www.groundstate.ca
Re: [Cooker] /usr/lib/i686
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 24 March 2003 07:16, Quel Qun wrote: > On Sun, 2003-03-23 at 21:49, Gwenole Beauchesne wrote: > > Hi, > > > > > 1. Does this happen automatically, or does the executable require code > > > to look there? > > > > Yes, based on what the kernel says to glibc. I explained that before. > > > > > 2. Can we actually compile two libraries (i586 and i686) and add them > > > both to the rpm packages, or does that have to be done explicitly by > > > the build process? > > > > We can add both in the package since i686 libraries go into another > > directory. I explained that before. > > > > > 3. Is there some tutorial for programmers on doing this type of thing? > > > > ? > > > > > It just seems like such an easy solution to our mmx problem, I wonder > > > why it's not more often employed. > > > > Please read Cooker archives. > > > > Bye, > > Gwenole. > > This is the worst answer I've ever seen in this list. I just can believe > we are spending so much time fighting with cooker and be answered with > such contempt. relax, people can't give good answers at all times, and also it's not always that easy to communicate > If you already answered these questions, then please repeat yourself if > cut and paste is not beyond your dignity, or at least give some > pointers. it's been described in other threads, and I don't think Gwenole gave such an answer in contempt, he probably thought that you could read it for yourself, and you must remember that while you don't think the explanation was good enough, he might've thought so, what might seem obvious for one, might not seem that obvious for everyone.. hopefully gwenole will take his time to document this, or maybe someone else will, also there's no stopping you from reading up on this yourself, after all, even gwenole probably did this once;) > I think I am done with mandrake and cooker for a while, and that's > wishing you'll survive. if that's some sort of a response to gwenole's answer, I don't think much of it.. - -- Regards, Per Øyvind Karlsen Sintrax Solutions http://www.sintrax.net - +47 41681061 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+fuu9v8F7V9JOSuURAiSeAKDZSaJcWlh84rxA9fAnH5tW9aKISgCgpbcx /m9quCvmCyLljMRHGmDOeJk= =JxKw -END PGP SIGNATURE-
Re: [Cooker] /usr/lib/i686
On Sun, 2003-03-23 at 21:49, Gwenole Beauchesne wrote: > Hi, > > > 1. Does this happen automatically, or does the executable require code > > to look there? > > Yes, based on what the kernel says to glibc. I explained that before. > > > 2. Can we actually compile two libraries (i586 and i686) and add them > > both to the rpm packages, or does that have to be done explicitly by > > the build process? > > We can add both in the package since i686 libraries go into another > directory. I explained that before. > > > 3. Is there some tutorial for programmers on doing this type of thing? > > ? > > > It just seems like such an easy solution to our mmx problem, I wonder > > why it's not more often employed. > > Please read Cooker archives. > > Bye, > Gwenole. This is the worst answer I've ever seen in this list. I just can believe we are spending so much time fighting with cooker and be answered with such contempt. If you already answered these questions, then please repeat yourself if cut and paste is not beyond your dignity, or at least give some pointers. I think I am done with mandrake and cooker for a while, and that's wishing you'll survive. -- _ _ _ _ | |_| | |_/ | | / / -_) | / / | |_\_\___|_|_\_\_| @ sbcglobal.net signature.asc Description: This is a digitally signed message part
Re: [Cooker] /usr/lib/i686
Hi, 1. Does this happen automatically, or does the executable require code to look there? Yes, based on what the kernel says to glibc. I explained that before. 2. Can we actually compile two libraries (i586 and i686) and add them both to the rpm packages, or does that have to be done explicitly by the build process? We can add both in the package since i686 libraries go into another directory. I explained that before. 3. Is there some tutorial for programmers on doing this type of thing? ? It just seems like such an easy solution to our mmx problem, I wonder why it's not more often employed. Please read Cooker archives. Bye, Gwenole.
