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.
On Wed, 28 Oct 2026 13:21:02 +0800, 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.
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.
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.
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.
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.
"should't go?" "should go?"
On GNU/Linux one can put anything anywhere one damn well pleases.
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.
"should't go?" "should go?"
On GNU/Linux one can put anything anywhere one damn well pleases.
On my own systems, I don't mess around with anything installed
via the OS package management system.
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.
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.
If you think Ubuntu, Canonical, or any other entity has authority over
what I do on hardware that I personally own, I'd love to hear your
reasoning. I'm curious where you got this odd idea.
On Wed, 28 Oct 2026 16:28:41 -0700, Keith Thompson wrote:
If you think Ubuntu, Canonical, or any other entity has authority over
what I do on hardware that I personally own, I'd love to hear your
reasoning. I'm curious where you got this odd idea.
They have chosen for you both systemd and wayland
and you are essentially powerless to refuse.
But I will not venture into a protracted, and fruitless, battle about the
de facto control of GNU/Linux other than to state that the mainstream
distros have far too much power and that this power is a serious threat
to the long-term freedom.
The original point of this thread was where executables and libraries
should be located. I merely indicated, correctly, that there is no "should be" and that the user is free to choose any locations at will.
The user creates the distro and not vice versa.
On Thu, 29 Oct 2026 00:05:20 +0000, Leroy H wrote:
On Wed, 28 Oct 2026 16:28:41 -0700, Keith Thompson wrote:
If you think Ubuntu, Canonical, or any other entity has authority overThey have chosen for you both systemd and wayland and you are
what I do on hardware that I personally own, I'd love to hear your
reasoning. I'm curious where you got this odd idea.
essentially powerless to refuse.
MX Linux allows me to select either Wayland or X11 at login and to set the boot options to either systemd or sysVinit.
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.
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.
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.
If you think
If you thinkNo. He doesn't think. He claims, he pretends, but he doesn't know and he doesn't think.
On Wed, 28 Oct 2026 16:28:41 -0700, Keith Thompson wrote:
If you think Ubuntu, Canonical, or any other entity has authority over
what I do on hardware that I personally own, I'd love to hear your
reasoning. I'm curious where you got this odd idea.
They have chosen for you both systemd
and wayland
and you are essentially powerless to refuse.
But I will not venture into a protracted, and fruitless, battle about the
de facto control of GNU/Linux other than to state that the mainstream
distros have far too much power and that this power is a serious threat
to the long-term freedom.
The original point of this thread was where executables and libraries
should be located.
I merely indicated, correctly, that there is no "should
be" and that the user is free to choose any locations at will.
The user creates the distro and not vice versa.
Leroy H <lh@somewhere.net> writes:
[...]
That's so self-evidently wrong that
I don't know how to respond to it.
Maybe there's some truth buried under the nonsense,
but I'm not going to expend the effort to find it.
(There are Linux distros that use neither systemd nor wayland.)
That might be a sensible argument. It's certainly something that can be discussed. But probably not with you.
"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.
They have chosen for you both systemd
Yes, but as one can chose a distro based on its init system, it's not a
one way choice. You would need a brain to understand that.
On 31 Oct 2026 11:02:34 GMT, St‚phane CARPENTIER wrote:
They have chosen for you both systemd
Yes, but as one can chose a distro based on its init system, it's not a
one way choice. You would need a brain to understand that.
That's not the point, but then your pitiful failure with
simple logic has caused you to completely misunderstand.
You pretend to fight for long time freedom but the freedom you are
fighting for is for you to have the freedom to remove the freedom to
everyone else.
[snip bloated nonsense]
You pretend to fight for long time freedom but the freedom you are
fighting for is for you to have the freedom to remove the freedom to
everyone else.
Go back to your lovely Windows which has neither systemd nor
wayland.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498677:21:19 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 910 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,826 |