Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #94729 > unrolled thread
| Started by | Woozy Song <suzyw0ng@outlook.com> |
|---|---|
| First post | 2026-10-28 13:21 +0800 |
| Last post | 2026-10-28 05:35 -0400 |
| Articles | 6 on this page of 26 — 9 participants |
Back to article view | Back to comp.os.linux.misc
weird issue lib/lib64 with Suse Woozy Song <suzyw0ng@outlook.com> - 2026-10-28 13:21 +0800
Re: weird issue lib/lib64 with Suse Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-28 05:43 +0000
Re: weird issue lib/lib64 with Suse Woozy Song <suzyw0ng@outlook.com> - 2026-10-28 15:38 +0800
Re: weird issue lib/lib64 with Suse Leroy H <lh@somewhere.net> - 2026-10-28 15:38 +0000
Re: weird issue lib/lib64 with Suse Leroy H <lh@somewhere.net> - 2026-10-28 15:51 +0000
Re: weird issue lib/lib64 with Suse Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-10-28 13:55 -0700
Re: weird issue lib/lib64 with Suse Leroy H <lh@somewhere.net> - 2026-10-28 22:02 +0000
Re: weird issue lib/lib64 with Suse Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-10-28 16:28 -0700
Re: weird issue lib/lib64 with Suse Leroy H <lh@somewhere.net> - 2026-10-29 00:05 +0000
Re: weird issue lib/lib64 with Suse Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-10-28 17:40 -0700
Re: weird issue lib/lib64 with Suse Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-10-31 11:15 +0000
Re: weird issue lib/lib64 with Suse rbowman <bowman@montana.com> - 2026-10-29 03:32 +0000
Re: weird issue lib/lib64 with Suse Robert Riches <spamtrap42@jacob21819.net> - 2026-10-29 16:48 +0000
Re: weird issue lib/lib64 with Suse rbowman <bowman@montana.com> - 2026-10-29 19:32 +0000
Re: weird issue lib/lib64 with Suse Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-10-31 11:02 +0000
Re: weird issue lib/lib64 with Suse Leroy H <lh@somewhere.net> - 2026-10-31 14:05 +0000
Re: weird issue lib/lib64 with Suse Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-10-31 17:12 +0000
Re: weird issue lib/lib64 with Suse The Natural Philosopher <tnp@invalid.invalid> - 2026-10-31 17:39 +0000
Re: weird issue lib/lib64 with Suse Leroy H <lh@somewhere.net> - 2026-10-31 18:18 +0000
Re: weird issue lib/lib64 with Suse Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-31 21:22 +0000
Re: weird issue lib/lib64 with Suse Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-10-31 10:36 +0000
Re: weird issue lib/lib64 with Suse The Natural Philosopher <tnp@invalid.invalid> - 2026-10-31 10:47 +0000
Re: weird issue lib/lib64 with Suse Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-10-31 10:33 +0000
Re: weird issue lib/lib64 with Suse Leroy H <lh@somewhere.net> - 2026-10-31 13:46 +0000
Re: weird issue lib/lib64 with Suse Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-28 22:05 +0000
Re: weird issue lib/lib64 with Suse c186282 <c186282@nnada.net> - 2026-10-28 05:35 -0400
Page 2 of 2 — ← Prev page 1 [2]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2026-10-31 10:36 +0000 |
| Message-ID | <6ae5c4a1$0$2497$426a74cc@news.free.fr> |
| In reply to | #94758 |
Le 28-10-2026, Keith Thompson <Keith.S.Thompson+u@gmail.com> a écrit : > Leroy H <lh@somewhere.net> writes: >> On Wed, 28 Oct 2026 13:55:46 -0700, Keith Thompson wrote: >>> On my own systems, I don't mess around with anything installed >>> via the OS package management system. >> >> Then they are not your "own systems." They belong to the distro >> and you have no control whatsoever. >> >> I am so sorry to have to disturb your dreams. > > No need to apologize, other than for being completely wrong. It's an habit with him. > If you think No. He doesn't think. He claims, he pretends, but he doesn't know and he doesn't think. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2026-10-31 10:47 +0000 |
| Message-ID | <11c4h0o$10k2m$3@dont-email.me> |
| In reply to | #94831 |
On 31/10/2026 10:36, Stéphane CARPENTIER wrote: >> If you think > No. He doesn't think. He claims, he pretends, but he doesn't know and he > doesn't think. Sadly, that describes around 90% of the population, especially those who *think* only that they are intelligent... -- Those who want slavery should have the grace to name it by its proper name. They must face the full meaning of that which they are advocating or condoning; the full, exact, specific meaning of collectivism, of its logical implications, of the principles upon which it is based, and of the ultimate consequences to which these principles will lead. They must face it, then decide whether this is what they want or not. Ayn Rand.
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2026-10-31 10:33 +0000 |
| Message-ID | <6ae5c3f1$0$2497$426a74cc@news.free.fr> |
| In reply to | #94742 |
Le 28-10-2026, Leroy H <lh@somewhere.net> a écrit : >>> >>> Stuff you’re building from source, without going through the distr >>> package management, shouldn’t go in /lib or /bin or /usr/lib or >>> /usr/bin etc: they should go in /usr/local/lib or /usr/local/bin e >>> > > "should't go?" "should go?" > > On GNU/Linux one can put anything anywhere one damn well pleases. Because one can doesn't mean it's a smart thing to do. I remember a time, not so long ago, where you were unable to buy your own food. The only reason involved was your messing up the default without understanding them. And the way you found for fixing Firefox, was to remove the improvements you brought to Firefox. Blaming Firefox and th food sellers for your own incompetence. > For the system to automatically locate programs and libraries just > modify the PATH variable and the /etc/ld.so.conf file appropriately. > > Of course, one can also invoke a program and libraries directly: > > LD_LIBRARY_PATH=/some/place /some/other/place/program > > One can also statically link all library routines. First you learn, then you'll be able to give advices. Right now, the best advice that can be given to anyone is to avoid following your advices. It can't even be harmful to do the opposite of what you say. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | Leroy H <lh@somewhere.net> |
|---|---|
| Date | 2026-10-31 13:46 +0000 |
| Message-ID | <18e3a148860e82a8$1681$3261087$802601b3@news.usenetexpress.com> |
| In reply to | #94830 |
On 31 Oct 2026 10:33:21 GMT, Stéphane CARPENTIER wrote: >> >> "should't go?" "should go?" >> >> On GNU/Linux one can put anything anywhere one damn well pleases. > > Because one can doesn't mean it's a smart thing to do. > GNU/Linux is completely configurable from the ground up and this is the sole, simple point that I am making. I could create a viable GNU/Linux installation that placed all executables in "/myexecs" and all libraries in "/mylibs" and nothing would be amiss. It would involve a lot of detailed configuration but it could be done. (Note: _I_ could do it but _you_ could never do it because you lack understanding and are forever dependent on the mainstream distros.) > > I remember a > time, not so long ago, where you were unable to buy your own food. The > only reason involved was your messing up the default without > understanding them. > Your memory is distorted. This is totally false. In fact, this constitutes malicious slander and I could easily sue your ass for defamation in a court of law. > > And the way you found for fixing Firefox, was to > remove the improvements you brought to Firefox. Blaming Firefox and th > food sellers for your own incompetence. > I had challenged you at the time to actually visit the same web site with your immaculate, untouched version of Firefox. You would have experienced the same problem, but you refused to do so. You refused because you were afraid that I would be, as usual, shown to be absolutely correct. The web site was junk. They must have consulted with your company during the design.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-10-28 22:05 +0000 |
| Message-ID | <11btrih$2qolc$3@dont-email.me> |
| In reply to | #94731 |
On Wed, 28 Oct 2026 15:38:50 +0800, Woozy Song wrote: > Lawrence D’Oliveiro wrote: >> >> Stuff you’re building from source, without going through the distro >> package management, shouldn’t go in /lib or /bin or /usr/lib or >> /usr/bin etc: they should go in /usr/local/lib or /usr/local/bin >> etc. > > Yes you define a build directory like /usr/local or /opt > that is what I meant by 'target' in the original post. My /usr/local has no lib64 etc architecture-dependent directories in it. Actually on Debian multiarch the directory name would be “x86-64-linux-gnu”.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-10-28 05:35 -0400 |
| Message-ID | <h6idnY7XvMhKXHz3nZ2dnZfqn_udnZ2d@giganews.com> |
| In reply to | #94729 |
On 10/28/26 01:21, Woozy Song wrote: > I have a package that was written about 25 years ago. It uses fftw and > mpich3, which are built with autotools (configure/make/install). They > would end up in directory target/lib in Centos/Debian/Arch and the > oddball independent distros, but with Suse to target/lib64. This > happened with enterprise/Leap/Tumbleweed. So the build scripts had to be > kludged for Suse. > I hadn't used Tumblweed for a while, but did a fresh install yesterday. > And the problem has apparently been quietly fixed, stuff went to lib. Yikes ! 25 YEARS ??? Almost EVERYTHING has changed considerably since then ! I quit (o)SUSE a while back. DID love it - but then it got *weird* and also dropped a bunch of standard utils I often used within other apps. Used to use it for all my servers and my personal desktop ... now ........ The degradation of YAST and the smart/sane installer were the final straws. No more. They "improved" it - to DEATH. Went vanilla Deb for the servers, MX for any desktops.
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | comp.os.linux.misc
csiph-web