rsb problem with python

Wed May 30 21:32:09 UTC 2018

Hi Pete,

That's something I would like to know as well. When something fails after
building GCC, it would be nice to not have to rebuild GCC the next time. I
don't know enough about the RTEMS build process at this point to be able to
help you on that part.

Regards,

Alex

On Wed, May 30, 2018 at 2:19 PM D Peter Siddons <siddons at bnl.gov> wrote:

> Hi Alex,
>
>  OK, thanks. I'll try that tonight. Maybe it will work as-is from my home
> network.
>
> Is there a way to skip parts of the build? The first part is very slow.
>
> Pete.
>
>
>
> On 05/30/2018 04:59 PM, Slide wrote:
>
> Hi Pete,
>
> I also ran into a similar failure :-) I had to use:
>
> git config url https://git.rtems.org/.insteadOf
> <https://git.rtems.org/rtems.insteadOf> git://git.rtems.org
>
> My IT blocks the git protocol port on our company firewall. You can make
> this global by adding --global after config in the command above
>
> Alex
>
> On Wed, May 30, 2018 at 12:58 PM D Peter Siddons <siddons at bnl.gov> wrote:
>
>> Hi Gedare,
>>     That worked, i.e. commenting out the miniconda path and installing
>> python3.6-dev. So on to the next stop :)
>>
>> Processing stopped when building the kernel. At the end of the log file I
>> see:
>>
>> script: 72: export PATH
>> script: 73: # Default environment set up.
>> script: 74: LANG=C
>> script: 75: export LANG
>> script: 76: unset DISPLAY || :
>> script: 77: umask 022
>> script: 78: cd "/home/peter/development/rtems/src/rtems-source-builder/rtems/build/arm-rtems5-kernel-5-1"
>> script: 79: echo "=> arm-rtems5-kernel-5-1:"
>> script: 80: echo "==> %prep:"
>> script: 81: source_dir_rtems="rtems-5"
>> source setup: arm-rtems5-kernel-5-1: source rtems -q -c -n arm-rtems5-kernel-5-1-5
>> making dir: /home/peter/development/rtems/src/rtems-source-builder/rtems/sources/git
>> git: reset: git://git.rtems.org/rtems.git
>> git: checkout: git://git.rtems.org/rtems.git => 5
>> error: git command failed (/usr/bin/git): 1
>>
>> I have attached the entire report, FYI. Does this mean that git could not
>> supply the source?
>>
>> Pete.
>>
>>
>> On 05/30/2018 01:01 PM, Gedare Bloom wrote:
>>
>> Pete,
>>
>> On Wed, May 30, 2018 at 12:19 PM, D Peter Siddons <siddons at bnl.gov> <siddons at bnl.gov> wrote:
>>
>> Hi Gedare,
>>
>>    I didn't get your earlier email (?), but the answer is:
>>
>> /home/peter/miniconda3/bin/python3.6
>>
>> so the only way I have 3.6 is through miniconda. Maybe it expects
>> /usr/bin/python3.6?
>>
>>
>> Odd that my email didn't come through to you. Anyway, since 'which'
>> finds it, the paths seem correct. Alex' suggestion to install the
>> development library is a good one however. I have had problems in the
>> past with mixed Anaconda python installations and Ubuntu distro ones.
>> I (like you) had the conda in a subdir of my home directory though, so
>> I found it was easiest for me to just disable the conda paths e.g. by
>> commenting out
>> #export PATH="/home/gedare/anaconda3/bin:$PATH"
>> in my .bashrc was sufficient for me
>>
>> Then, I could install/use the Ubuntu distributions Python2/3 packages
>> without conflicts.
>>
>> Gedare
>>
>>
>> Pete.
>>
>>
>>
>> On 05/30/2018 12:12 PM, Gedare Bloom wrote:
>>
>> Alex,
>>
>> Yes that also makes sense, thank you. Usually, I've seen that problem
>> manifest as missing Python.h, but error messages can be vague and
>> inconsistent. :)
>>
>> On Wed, May 30, 2018 at 11:49 AM, Slide <slide.o.mix at gmail.com> <slide.o.mix at gmail.com> wrote:
>>
>> I ran into a similar issue and the way I solved it was by installing the
>> -dev package for Python. For me this was libpython3-dev on Ubuntu. I'm not
>> sure how to do that with the Anaconda installation, but this may help point
>> you in the right direction.
>>
>> Regards,
>>
>> Alex
>>
>> On Wed, May 30, 2018 at 6:57 AM Gedare Bloom <gedare at rtems.org> <gedare at rtems.org> wrote:
>>
>> Pete,
>>
>> Do you get anything with:
>> $ which python3.6
>>
>> Probably, it is looking for that invocation command. I ought to try
>> this, because my Ubuntu does not ship with python3.6 I know, so maybe
>> it breaks too... hm
>>
>> On Mon, May 28, 2018 at 6:23 PM, Siddons, David <siddons at bnl.gov> <siddons at bnl.gov> wrote:
>>
>> Hi Amaan,
>>    Actually,  /home/peter/miniconda3/bin/python is a soft link to
>> /home/peter/miniconda3/bin/python3.6 already! Does rsb not follow links?
>> Pete.
>>
>> ________________________________
>> From: Amaan Cheval [amaan.cheval at gmail.com]
>> Sent: Monday, May 28, 2018 6:05 PM
>> To: Siddons, David
>> Cc: users at rtems.org
>> Subject: Re: rsb problem with python
>>
>> Hey David!
>>
>> It looks to me like Anaconda doesn't install the "alias" binaries
>> specifying
>> the version (for eg. both "python" and "python3.6"). I believe the fix
>> in
>> your case should be as simple as copying your existing binary with the
>> following command:
>>
>> cp /home/peter/miniconda3/bin/python
>> /home/peter/miniconda3/bin/python3.6
>>
>>
>> On Tue, May 29, 2018, 3:28 AM Siddons, David <siddons at bnl.gov> <siddons at bnl.gov> wrote:
>>
>> While building rsb for arm-rtems I got this problem:
>>
>> checking for python... /home/peter/miniconda3/bin/python
>> checking for python3.6... no
>> configure: error: python is missing or unusable
>> Makefile:9095: recipe for target 'configure-gdb' failed
>> make[1]: *** [configure-gdb] Error 1
>> make[1]: Leaving directory
>>
>> '/home/peter/development/rtems/src/rtems-source-builder/rtems/build/arm-rtems5-gdb-8.0.1-x86_64-linux-gnu-1/build'
>> Makefile:848: recipe for target 'all' failed
>> make: *** [all] Error 2
>> shell cmd failed: /bin/sh -ex
>>
>> /home/peter/development/rtems/src/rtems-source-builder/rtems/build/arm-rtems5-gdb-8.0.1-x86_64-linux-gnu-1/doit
>> error: building
>>
>> arm-rtems5-gdb-8.0.1-x86_64-linux-gnu-1peter at peter-Latitude-E7240:~/development/rtems/src/rtems-source-builder/rtems$
>>
>> I am running Ubuntu:
>>
>> peter at peter-Latitude-E7240:/etc$ lsb_release -a
>> LSB Version:
>>
>> core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
>> Distributor ID: Ubuntu
>> Description:    Ubuntu 16.04.4 LTS
>> Release:        16.04
>> Codename:       xenial
>>
>> then:
>>
>> python -V
>> Python 3.6.1 :: Continuum Analytics, Inc.
>>
>> This comes from an Anaconda installation. If I remove the path entry
>> which
>> causes that I get python 2.7, which is the default Ubuntu 16.04
>> version. Do
>> I need to install Python 3.6?
>>
>> Pete.
>>
>>
>> _______________________________________________
>> users mailing listusers at rtems.orghttp://lists.rtems.org/mailman/listinfo/users
>>
>> _______________________________________________
>> users mailing listusers at rtems.orghttp://lists.rtems.org/mailman/listinfo/users
>>
>> _______________________________________________
>> users mailing listusers at rtems.orghttp://lists.rtems.org/mailman/listinfo/users
>>
>> .
>>
>>
>> --
>> D. Peter Siddons
>> Detector Development Group Leader
>> Photon Science Division, NSLS-II,
>> Bldg. 535B
>> Brookhaven National Laboratory
>> Upton, NY 11973
>>
>> email: siddons at bnl.gov
>> Phone: (631) 344-2738
>>
>> .
>>
>>
>>
>> --
>> D. Peter Siddons
>> Detector Development Group Leader
>> Photon Science Division, NSLS-II,
>> Bldg. 535B
>> Brookhaven National Laboratory
>> Upton, NY 11973
>>
>> email: siddons at bnl.gov
>> Phone: (631) 344-2738
>>
>>
> --
> D. Peter Siddons
> Detector Development Group Leader
> Photon Science Division, NSLS-II,
> Bldg. 535B
> Brookhaven National Laboratory
> Upton, NY 11973
>
> email: siddons at bnl.gov
> Phone: (631) 344-2738
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20180530/e3fcbc24/attachment-0002.html>