bind mount (and anything invoking mount) requires root privilege, except for
fusemount and some removable medium use cases - even that is often disabled
based on site policy.
Using proot-me seems to be no better than the original poster's - depending on
a peculiar way of doing things
Greetings,
I hope this is relevant and not besides the point, but I was thinking
that you may be able to use proot to bind mount your shell to /bin/sh
without root privileges:
https://proot-me.github.io/
Hopefully this would also be useful in other situations where the SHELL
environment
>> But you still doesn't show us an *exact* recipe or log files that
>> demonstrates the problem you encounter.
>
> Below you can see the error: (the Readline library that '/bin/sh'
> needed was more recent than our custom Readline installation; so
> '/bin/sh' could not find the function it
But you still doesn't show us an *exact* recipe or log files that
demonstrates the problem you encounter.
Below you can see the error: (the Readline library that '/bin/sh' needed
was more recent than our custom Readline installation; so '/bin/sh'
could not find the function it needed
>> Please describe your setup carefully before jumping to quick
>> solutions.
>
> The problem occurred on an Arch GNU/Linux, and the '/bin/sh
> --version' is GNU Bash 5.2.26 and I installed FreeType 2.11.0. After
> checking the Git repository and noticing that my particular problem
> occurred
I dare say your problem does not happen to thousands of Arch Linux users who
try to compile freetype.
One thing on the security aspect of sh and GNU Bash - you are aware that GNU
Bash itself behaves differently, depending on what you call the binary, right?
If you build GNU Bash yourself, then
>
> The main purpose of going through all this trouble is long-term
> reproducibility of our scientific publications/results.
Reproducibility is not equal to determinism.
Thanks Hin-Tak,
I will be updating the version of FreeType shortly, this was for an
older project.
The main purpose of going through all this trouble is long-term
reproducibility of our scientific publications/results. Unfortunately
that is something most operating system package managers
Hmm, why are you trying to compile an older version of freetype (2.11.x), when
arch linux ships 2.13.x ?
Anyway, here is how the Arch Linux people build freetype - they use meson
instead of autoconf (PKGBUILD itself is largely a shell script with, divided
into shell script routines):
Dear Alexei, Werner and Hin-Tak,
Thank you for the comments; I appreciate the prompt replies :-).
There is this peculiar autogen.sh to be run initially... Still fails? How?
I had indeed read the README, but it had only instructed using
'autogen.sh' when "... building a git snapshot or
Besides what Werner said - name your system. Most of the world has converged
on GNU bash, but Ubuntu/Debian uses dash, some older Solaris used ksh. Some
really old unix system (tru64 came to mind) has genuine BSD sh. You wrote about
lacking the privilege to be root, so I guess you are not
>>
>> Do you mean here?
>>
>> https://gitlab.freedesktop.org/freetype/freetype/-/tree/master/builds/unix
>> ...
>
> Please start at README and README.git or here:
> https://gitlab.freedesktop.org/freetype/freetype/-/blob/master/docs/INSTALL.UNIX
>
> There is this peculiar autogen.sh to be run
On Wed, May 1, 2024 at 7:11 PM Mohammad Akhlaghi wrote:
>
> Do you mean here?
>
> https://gitlab.freedesktop.org/freetype/freetype/-/tree/master/builds/unix
> ...
Please start at README and README.git or here:
https://gitlab.freedesktop.org/freetype/freetype/-/blob/master/docs/INSTALL.UNIX
Do you mean here?
https://gitlab.freedesktop.org/freetype/freetype/-/tree/master/builds/unix
There is only 'configure.raw' there; its contents are indeed Autoconf,
but its name is non-standard, that is probably why I missed it ;-).
The main point is that the 'configure' script at the top
I know all that. :) Check out builds/unix/configure.ac
behdad
http://behdad.org/
On Wed, May 1, 2024 at 4:40 PM Mohammad Akhlaghi
wrote:
> I had set the 'SHELL' environment variable but still '/bin/sh' was used.
> The only way I could pass my SHELL to the Make command within the
> configure
I had set the 'SHELL' environment variable but still '/bin/sh' was used.
The only way I could pass my SHELL to the Make command within the
configure script was through the non-standard hack I mentioned before:
GNUMAKE="make SHELL=$SHELL"
Autoconf generates the './configure' script
Scratch that.
Where is it exactly failing? On Unix, the build system is essentially
autoconf, so it should respect SHELL as you suggest.
behdad
http://behdad.org/
On Wed, May 1, 2024 at 3:15 PM Behdad Esfahbod wrote:
> Can you check if also setting CONFIG_SHELL helps?
>
> behdad
>
Can you check if also setting CONFIG_SHELL helps?
behdad
http://behdad.org/
On Wed, May 1, 2024 at 3:06 PM Mohammad Akhlaghi
wrote:
> The Autoconf-generated configure script, or even CMake, respect SHELL, so
> if a user gives it a problematic shell, they won't be able to build
> anything abd
The Autoconf-generated configure script, or even CMake, respect SHELL, so if a
user gives it a problematic shell, they won't be able to build anything abd
many programs will crash.
But please consider the scenario mentioned before: when a user doesn't have
root permissions to change
I'm not talking about the user overriding the shell specifically. I'm
talking about users who genuinely use a non-POSIX shell as their terminal
shell. Then just running ./configure would fail if configure was to respect
$SHELL.
Or rather you're saying that only POSIX-compatible shells should set
Thanks Behdad,
The problem is that I do not have root permissions on the system with the
faulty '/bin/sh': I cannot change '/bin/sh' and need to build my programs with
a custom shell.
If the user specifies a wrong shell (not the default '/bin/sh'), it is their
own responsibility that it is
There's no guarantee that the user's shell is sh-compatible. autoconf
really means sh here, because that's the shell the script is written for.
Just symlink your favorite shell to sh then, if it's compatible.
behdad
http://behdad.org/
On Wed, May 1, 2024 at 2:13 PM Mohammad Akhlaghi
wrote:
>
Hi again,
I was able to find a cleaner hack by running this command before the
'./configure' script:
export GNUMAKE="make SHELL=$SHELL"
Afterwards, FreeType successfully ran with my desired shell.
But generally, it would greatly help those building FreeType from source
if the configure
23 matches
Mail list logo
