Date: 23-10-20  Time: 06:17 AM

Recent Posts

Pages: 1 ... 3 4 [5] 6 7 ... 10
41
I had guessed as much...
I have a clean system (well almost - experimenting with jenkins), but no compiler, so it has errors of course.
First thing I do is create a "clean" virtualenv that I switch to - to not disturb anything at a system level.

But my first phase is always to just 'download' the target and see where issues come up.
So, since I do not have a compiler - I run into cffi as an issue - no C compiler to build it:
Code: [Select]
root@x072:[/home/root]py38
(py38) root@x072:[/home/root]mkdir py38
(py38) root@x072:[/home/root]pip download pynacl
Collecting pynacl
  Downloading PyNaCl-1.4.0.tar.gz (3.4 MB)
     |################################| 3.4 MB 3.1 MB/s
  Installing build dependencies ... error
  ERROR: Command errored out with exit status 1:
   command: /opt/python/py38/bin/python /opt/python/py38/lib/python3.8/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-_57fryna/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- 'setuptools>=40.8.0' wheel 'cffi>=1.4.1; python_implementation != '"'"'PyPy'"'"''
42
Thanks Michael,

# lslpp -l aixtools.python.py38.*
  Fileset                      Level  State      Description
  ----------------------------------------------------------------------------
Path: /usr/lib/objrepos
  aixtools.python.py38.adt   3.8.2.0  COMMITTED  python py38 ADT files
  aixtools.python.py38.man.en_US
                             3.8.2.0  COMMITTED  python py38 man pages
  aixtools.python.py38.rte   3.8.2.0  COMMITTED  python py38 31-Mar-2020
43
Years ago - I had no issues with sodium - that I can recall - but I'll give it a shot.
Which Python3 version are you using?
Michael
44
Hi Michael,

Have you had any joy compiling this yourself?  Ultimately I'm trying to install module pysftp.  I've found a few hits online but no joy so far so any advice appreciated.

For me it hangs as below -
 # pip3 install  pynacl
Collecting pynacl
  Downloading PyNaCl-1.4.0.tar.gz (3.4 MB)
     |################################| 3.4 MB 3.2 MB/s
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
    Preparing wheel metadata ... done
Requirement already satisfied: cffi>=1.4.1 in /opt/lib/python3.8/site-packages (from pynacl) (1.14.0)
Requirement already satisfied: six in /opt/lib/python3.8/site-packages (from pynacl) (1.14.0)
Requirement already satisfied: pycparser in /opt/lib/python3.8/site-packages (from cffi>=1.4.1->pynacl) (2.20)
Building wheels for collected packages: pynacl
  Building wheel for pynacl (PEP 517) ... -


 ps shows -
    root  8323076  8716394 120 00:39:28  pts/1  0:00 /bin/sh ../../libtool --silent --tag=CC --mode=compile xlc_r -DPACKAGE_NAME="libsodium" -DPACKAGE_TARNAME="libsodium" -DPACKAGE_VERSION="1.0.18" -DPACKAGE_STRING="libsodium 1.0.18" -DPACKAGE_BUGREPORT="https://github.com/jedisct1/libsodium/issues" -DPACKAGE_URL="https://github.com/jedisct1/libsodium" -DPACKAGE="libsodium" -DVERSION="1.0.18" -DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -DHAVE_C_VARARRAYS=1 -DHAVE_CATCHABLE_SEGV=1 -DHAVE_CATCHABLE_ABRT=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=".libs/" -DHAVE_SYS_MMAN_H=1 -DNATIVE_BIG_ENDIAN=1 -DHAVE_INLINE_ASM=1 -DCPU_UNALIGNED_ACCESS=1 -DHAVE_ATOMIC_OPS=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_MMAP=1 -DHAVE_MLOCK=1 -DHAVE_MADVISE=1 -DHAVE_MPROTECT=1 -DHAVE_POSIX_MEMALIGN=1 -DHAVE_GETPID=1 -DHAVE_NANOSLEEP=1 -DHAVE_MEMSET_S=1 -DCONFIGURED=1 -I. -I/tmp/pip-install-ub689zph/pynacl/src/libsodium/src/libsodium -I/tmp/pip-install-ub689zph/pynacl/src/libsodium/src/libsodium/include/sodium -I./include/sodium -D_FORTIFY_SOURCE=2 -DNDEBUG -O -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 -q64 -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 -q64 -c -o crypto_stream/chacha20/ref/libsodium_la-chacha20_ref.lo /tmp/pip-install-ub689zph/pynacl/src/libsodium/src/libsodium/crypto_stream/chacha20/ref/chacha20_ref.c

45
Virtualization / Re: number of VIOS for large virtualized server
« Last post by orian on June 21, 2020, 03:04:09 PM »
Hi Michael
I was wondering : if I have two lpars communicating on one same vlan through vnics defined with the main backing device on the same sr-iov physical port, the packets won't get out of the adapter and it is fine for me, but does it make a difference if I choose the same VIOS for the main backing device on both LPARs or if I choose two different VIOS ?
My concern is to have the shortest communication path between both lpars over this vlan, because one lpar is for an application environment and the other lpar will host some oracle databases, and the application is badly written with small SQL queries executed in loops so it is highly impacted by any change of latency and I want the smallest possible network latency for the communication between these two lpars.

if you just want to communicate between lpar on same box, and no partial takeover happen, I mean app may running on different box than DB, nothing needed, no physical card, no vios. just create vlan and assign vnic on each partitions onto the vlan, that is.

don't forget enable firmware memory mirroring of p980 to have the redundant, there is only ONE vlan.
46
Virtualization / Re: number of VIOS for large virtualized server
« Last post by orian on June 21, 2020, 02:56:40 PM »
VIOC                                                    VIOS
aix tcp/ip stack                            SEA bridge(data moving)
vNIC driver                       vNIC driver              enet adapter driver
             physical memory DMA                                    outside/network switch

vs.

VIOC
aix tcp/ip stack
enet adapter driver
physical memory DMA/sriov sharing


the delay could be up to hundred milliseconds or more, the throughput shouldn't be impacted for lightweight networking traffic, but if there is less of physical CPU (entilment PU) on vios and huge network delay already, for example, long distance (more than hundred KMs) between production and dr site, the delay appended may be not acceptable.

to use CPU more effectiveness, use VIOS/SEA and balance CPU allocation by real test
to get good performance, especially for response sensitive application, SRIOV would be the best choice.
outside/network switch
47
AIXTOOLS / Re: What your goals are
« Last post by Michael on June 10, 2020, 07:14:29 PM »
Maybe I wrote it wrong. I'll check.
Quote
AIXTOOLS began simply - porting Apache/ASF httpd and PHP tools needed to host the ROOTVG.net portal. Now I am trying to provide an alternate repository for packages not in the original AIX ToolBox and/or from other sources such as Perzl's RPM repository.
Note: My goal is not to completely replace the [IBM AIX Toolbox -- RPM Repository].
My goal is to provide what people actually use - and is doable with the IBM xlc compiler I have.
The "not" in that sentence may have been true 6 or 7 years ago - as I packaged some things I could not find anywhere - however, as it stands - that word, by itself - is misleading.
The later issue is that I ran into problems - where the RPM .spec file would overwrite files also managed by an installp package. Updating the installp package broke the RPM; the RPM could not be removed; or an update of an RPM broke other things. This is why I put my libraries in /opt/lib rather than /usr/lib. There are exceptions - due to dlopen() issues - but then I save the original file so that if/when you remove the AIXTOOLS package - the original IBM AIX file is restored. (Lessons learned!)
I use IBM XLC, not GCC. This means there are packages I "cannot" package. GCC has a few special features that make packaging some things impossible. Likely, xlc is behind (years behind). Not because I do not like GCC, but if I use GCC then I feel I must also maintain the GNU rte (run-time-environment) - in particular the GNU libc that GCC depends on.
So, to close - I am not trying to be a copy of Perzl, BULL, or AIX Toolbox. I do try to minimize dependencies (e.g., iirc, my git package for AIX has no additional dependencies).
Anyway, I'll go back and review how I wrote that in my wiki. (i.e., been there - removing the word not)

Thanks for the feedback!Michael
48
AIXTOOLS / Re: What your goals are
« Last post by tmcgivern on June 10, 2020, 06:29:47 PM »
Thank you sir! 

But, back to my original question
in the "history" page you seem to imply that you are only repackaging what is NOT on perzl or bull.   Am I reading that wrong? 
can you please clarify which packages you plan to maintain here?

Thanks.  (now go enjoy the rest of your vacation! :) )
49
AIXTOOLS / Re: What your goals are
« Last post by Michael on June 10, 2020, 06:26:42 PM »
a) I would suggest you download the other packages - for now
b) I'll repackage - but that will be roughly two weeks.
50
AIXTOOLS / Re: What your goals are
« Last post by tmcgivern on June 10, 2020, 05:52:44 PM »
Happy you found the problem, hopefully not taking up too much of your vacation.
So.. next steps?
do you plan to repackage?
Or do I need to download those other packages, and install them?
Pages: 1 ... 3 4 [5] 6 7 ... 10