Dear all,
I hope all is well with you. I managed to resolve the issue by calling rbenv
with the following Ruby configuration options:
RUBY_CONFIGURE_OPTS="--with-openssl-dir=/opt/local/libexec/openssl3
--with-libyaml-dir=/opt/local" rbenv install 3.4.1
This way it worked. Additionally I had to
No Ryan, I didn't switch from zsh to bash as any user - after migration
of users and apps, and my moving from a temporary user to my usual one,
Terminal came up in bash with the usual zsh entreaty, and I left things
that way. This was all a few hours before starting a "clean" install of
MacPort
On Oct 20, 2023, at 19:44, Chris F wrote:
>
> I have created an appropriate .bash_profile (as described in the Guide) and
> everything appears normal now.
You are using bash on Sonoma? The default shell is zsh. The MacPorts installer
is supposed to detect which shell you use and configure the a
Thanks Bill, Chris - I have created an appropriate .bash_profile (as
described in the Guide) and everything appears normal now.
I've searched back to the time when Migration Assistant restored my user
directory. That .bash_profile had several comments made at the time(s)
that MacPorts install
> On 20 Oct 2023, at 6:13 pm, Bill Cole
> wrote:
>
> On 2023-10-19 at 18:47:01 UTC-0400 (Fri, 20 Oct 2023 11:47:01 +1300)
> Chris F
> is rumored to have said:
>
>>> On 20/10/23 11:17 am, Chris Jones wrote:
>>>
>>>
On 19 Oct 2023, at 10:58 pm, Chris F wrote:
On 2023-10-19 at 18:47:01 UTC-0400 (Fri, 20 Oct 2023 11:47:01 +1300)
Chris F
is rumored to have said:
On 20/10/23 11:17 am, Chris Jones wrote:
On 19 Oct 2023, at 10:58 pm, Chris F wrote:
I've just migrated to Sonoma 14.0 via a clean OS install plus
Migration Assistant and I'm now rein
On 20/10/23 11:17 am, Chris Jones wrote:
On 19 Oct 2023, at 10:58 pm, Chris F wrote:
I've just migrated to Sonoma 14.0 via a clean OS install plus
Migration Assistant and I'm now reinstalling my ports one at a time.
Port ruby31 installed without problems but ruby-select doesn't seem
t
> On 19 Oct 2023, at 10:58 pm, Chris F wrote:
>
>
> I've just migrated to Sonoma 14.0 via a clean OS install plus Migration
> Assistant and I'm now reinstalling my ports one at a time.
>
> Port ruby31 installed without problems but ruby-select doesn't seem to
> work/be effective - after r
I think that there’s something more going on, because most of this shouldn’t
be necessary, and some of it shouldn’t be in $PATH at all (like
/opt/local/share/man; that belongs in $MANPATH). In `~/.bashrc`, you should
be specifying something like:
```bash
export PATH=$HOME/bin:/opt/local/bin:/opt/l
Ah. Freaky. Whatever works :).
On 3/20/23 12:13 PM, chilli.names...@gmail.com wrote:
Also, for whatever reason, Mountain Lion does not source .bash_profile
on login. So on that box, I have to source it after I login and
whenever I sudo. I guess I could add a script to source it at login,
but i
Also, for whatever reason, Mountain Lion does not source .bash_profile on
login. So on that box, I have to source it after I login and whenever I sudo. I
guess I could add a script to source it at login, but it's not a big deal.
> On Mar 20, 2023, at 13:10, chilli.names...@gmail.com wrote:
>
>
Really? Do you never edit your .bash_profile to add functions?
> On Mar 20, 2023, at 13:01, Will Senn wrote:
>
> bash_profile is executed for login shells, so it shouldn't be sourced more
> than once per login.
>
> On 3/20/23 11:49 AM, chilli.names...@gmail.com wrote:
>> I was checking. ech
fixed duplicates when sourcing .bash_profile by clearing PATH before the export
command with
PATH=
LOL
ugly, but it works
> On Mar 20, 2023, at 12:49, chilli.names...@gmail.com wrote:
>
>
> I was checking. echo $PATH reports correctly. If I source the .bash_profile
> more than once, howeve
bash_profile is executed for login shells, so it shouldn't be sourced
more than once per login.
On 3/20/23 11:49 AM, chilli.names...@gmail.com wrote:
I was checking. echo $PATH reports correctly. If I source the
.bash_profile more than once, however, I get duplicates.
On Mar 20, 2023, at 12:
I was checking. echo $PATH reports correctly. If I source the .bash_profile
more than once, however, I get duplicates.
> On Mar 20, 2023, at 12:44, Will Senn wrote:
>
>
> Sounds like you should check $PATH before and after the change to see what
> it's actually doing. Whatever you want to ru
Sounds like you should check $PATH before and after the change to see
what it's actually doing. Whatever you want to run, say your version of
ruby in /some/dir/ruby, needs to appear earlier in the path than the
system version, say /usr/bin/ruby... period. It's not rocket science.
However, it's
This is the only way I can get it to work right without error
> export
> PATH="$PATH:$HOME/bin:/opt/local/bin:/opt/local/sbin:/opt/local/share/man:/usr/X11/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
It doesn't like :$PATH at the end
> On Mar 20, 2023, at 09:27, chilli.names...@gmail.co
Dear all,
How are you? I hope all is well with you. Sometime ago I was recommended to use
rbenv script (https://github.com/rbenv/rbenv) to manage multiple installations
and versions of Ruby. I followed that advice and have no problems since then.
You just need to set it up properly. Read the in
I am closer, but my $PATH is still messed up.
This in .bash_profile
> export
> PATH=$HOME/bin:/opt/local/bin:/opt/local/sbin:/opt/local/share/man:/usr/X11/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:$PATH
gets me this when I source it
> env: bash: No such file or directory
> dude@mac:~/E
Yeah, this is the answer. You always want `/opt/local/bin/` to be near the
start of your path. Only stuff that you specifically want to override
MacPorts should be before it. (Examples of things you may want before: RVM
or NVM or any of the version managers that put things in your home)
—Mark
Change that toexport PATH=$HOME/bin:/opt/local/bin:/opt/local/sbin:/opt/local/share/man:/usr/X11/bin:$PATH-aOn Mar 11, 2023, at 14:03, chilli.names...@gmail.com wrote:Thank you, I will check thatI haveexport PATH=$PATH:$HOME/bin:/opt/local/bin:/opt/local/sbin:/opt/local/share/man:/usr/X11/binin my
They all point to the old system versions
My $PATH is pretty screwed up.
Thanks.
> On Mar 11, 2023, at 13:50, Bill Cole
> wrote:
>
> On 2023-03-11 at 13:05:54 UTC-0500 (Sat, 11 Mar 2023 13:05:54 -0500)
>
> is rumored to have said:
>
>> Hi,
>> I need a quick ruby primer, please.
>>
>> I'd
Thank you, I will check that
I have
> export
> PATH=$PATH:$HOME/bin:/opt/local/bin:/opt/local/sbin:/opt/local/share/man:/usr/X11/bin
in my .bash_profile, but echo $PATH shows what you expected:
> dude@mac:~$ echo $PATH
> /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/dude/bin:/opt/local/
On 2023-03-11 at 13:05:54 UTC-0500 (Sat, 11 Mar 2023 13:05:54 -0500)
is rumored to have said:
Hi,
I need a quick ruby primer, please.
I'd like to install this,
https://github.com/pedrozath/coltrane
sudo gem install coltrane
won't work because I'm on Mojave with an an ancient ruby and thi
No problem. The system ruby showing up instead of MacPorts-installed Ruby
would be *probably* because your $PATH has `/opt/local/bin` *after*
`/usr/bin`. Typically, one wants to have Macports (or other third-party
package systems) *before* /usr/local/bin and /usr/bin.
-a
On Sat, Mar 11, 2023 at 1
> root@mac:~$ ruby -S gem install coltrane
> ERROR: Error installing coltrane:
> activesupport requires Ruby version >= 2.7.0.
Unfortunately, Mojave:
ruby 2.3.7p456 (2018-03-28 revision 63024) [universal.x86_64-darwin18]
So I install ruby 2.7.7
> root@mac:~$ port -vsN install ruby27
26 matches
Mail list logo
