Re: scons 'v fails
Bill Deegan <[email protected]> Mon, 4 Mar 2024 10:10:13 -0800
| Newsgroups | gmane.comp.programming.tools.scons.user |
|---|---|
| Message-ID | <CAEyG4CF5vPwT5EqgZSTJL7kivQw+yoAax4msim+LfAC1AYi-9g@mail.gmail.com> |
How did they install SCons? (command line for install) Which version of python? On Mon, Mar 4, 2024 at 8:32 AM daggs via Scons-users <[email protected]> wrote: > > Sent: Monday, March 04, 2024 at 6:47 PM > > From: "Mats Wichmann" <[email protected]> > > To: [email protected] > > Subject: Re: [Scons-users] scons 'v fails > > > > On 3/4/24 08:25, daggs via Scons-users wrote: > > > Greetings, > > > > > > I've encountered a user on one of our systems where scons -v fails. > > > this is the output: > > > $ scons -v > > > Traceback (most recent call last): > > > File "/usr/bin/scons", line 33, in <module> > > > sys.exit(load_entry_point('SCons==4.5.2', 'console_scripts', > 'scons')()) > > > File "/usr/bin/scons", line 25, in importlib_load_entry_point > > > return next(matches).load() > > > StopIteration > > > > > > any ideas what can cause it? > > > > That's weird. I didn't think the entry_point magic even got invoked on > > Linux. Is there more information, like distro name/version? Have VMs > > here of various Fedora, Debian, Ubuntu, Mint and Centos-like here where > > could crosscheck. It *could* be a packaging problem, though I don't want > > to point fingers elsewhere without more info. > > > > rhel 9.3, kernel 5.14.0-362.18.1.el9_3.x86_64 > > any other info needed? > > _______________________________________________ > Scons-users mailing list > [email protected] > https://pairlist4.pair.net/mailman/listinfo/scons-users > _______________________________________________ Scons-users mailing list [email protected] https://pairlist4.pair.net/mailman/listinfo/scons-users