search for: cffi

...n of the IR (which is less memory efficient than the LLVM one), and 3) each llvmlite version supports a single LLVM version. Considering that my need is to load modules of hundreds of MiB, this is was kind of a problem. So I've come up with a "Python API generator". Basically it uses CFFI [4] to parse the LLVM-C API headers and automatically generate (using some heuristics) a Pythonic API, with classes, properties and the like. I've quickly tested it with LLVM 3.4, 3.8 and 3.9, and, for its simplicity, does a good job. It also supports multiple LLVM installations (it uses the o...

Hello, I have the following error when checking for GPOs for a single user, listing all GPOs is working: ------------------ root at tn2-debian1:~# samba-tool gpo listall GPO : {31B2F340-016D-11D2-945F-00C04FB984F9} display name : Default Domain Policy path : \\example2.net\sysvol\example2.net\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9} dn :

...sion 37840 (this morning, Seattle time) for R-2-3-patches. I've not tried Thomas' suggested fixes, as I'm hesistant to go down the road of fixing R in such a way that would require constant patching. (so for those counting, neither CLISP, CMUCL, nor SBCL can embed R-2-3-patches using CFFI on (2 distros of) i386 Linux; all abort and offer to dump core nearly instantly after initialization). All work with R-2-2-patches. For me, this is a serious bug. I suppose other people can define it in other ways, using terms such as "feature" or "documented". For various...

>>>>> Laurent Gautier >>>>> on Sun, 15 Sep 2019 15:01:09 -0400 writes: > In case a search engine leads someone with the same issue > here, I am documenting the point I reached: > I can reproduce the issue with a small example when > forcing R to not load any package at startup time (using > an Renviron file): ``` package <-

...ubekki at gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: Drivers/DRI/nouveau Product: Mesa Created attachment 75991 --> https://bugs.freedesktop.org/attachment.cgi?id=75991&action=edit example script with cffi I bound gbm_create_device with both cffi and cython of gbm_create_device and they both fail at the same place error: Program received signal SIGSEGV, Segmentation fault. stacktrace: #0 0x00007fffee18af07 in PUSH_DATA (push=0x13c0410, data=536952832) at ../../../../src/gallium/drivers/nouveau/n...

...3.5.3-1 > amd64 interactive high-level object-oriented > language (default python3 version) > > ii python3-apt 1.4.0~beta3 > amd64 Python 3 interface to libapt-pkg > > ii python3-cffi 1.9.1-2 > all Foreign Function Interface for Python 3 > calling C code > > ii python3-cffi-backend 1.9.1-2 > amd64 Foreign Function Interface for Python 3 > calling C code - runtime...

...are installed : ii python3 3.5.3-1 amd64 interactive high-level object-oriented language (default python3 version) ii python3-apt 1.4.0~beta3 amd64 Python 3 interface to libapt-pkg ii python3-cffi 1.9.1-2 all Foreign Function Interface for Python 3 calling C code ii python3-cffi-backend 1.9.1-2 amd64 Foreign Function Interface for Python 3 calling C code - runtime ii python3-crypto...

...476931 Alloc PE / Size 139520 / 545.00 GiB Free PE / Size 337411 / 1.29 TiB VG UUID ymYQtb-Xjnd-OBNv-xnUQ-w9gi-5uxm-kjzo not created libvirt /dev/LVM_MAIN/os_mirror VG Name LVM_MAIN LV UUID iPfekp-PN1C-rPHP-Bo3K-TljL-cffi-NdDvpi LV Write Access read/write LV Status available # open 1 LV Size 500.00 GiB Current LE 128000 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 25...

...? We are otherwise aware that the error is not occurring in the R console, but can be traced to a call to R_ParseVector() in R's C API:( https://github.com/rpy2/rpy2/blob/master/rpy2/rinterface_lib/_rinterface_capi.py#L509 ). Our specific setup is calling an embedded R from Python, using the cffi library. An error on end was the first possibility considered, but the puzzling specificity of the error (as shown below other parsing errors are handled properly) and the difficulty tracing what is in happening in R_ParseVector() made me ask whether someone on this list had a suggestion about the...

On 02/12/2019 10:07, Stefan G. Weichinger via samba wrote: > Am 02.12.19 um 08:47 schrieb L.P.H. van Belle via samba: >> Hai, >> >> Sorry for the late reply. > Never mind, weekend is important ... > >> Here its just apt-get distupgrade --autoremove --purge >> Without the autoremove libldb1 is not removed so libldb2 can be installed. > # apt-get distupgrade

...m starting to sound like a broken record, but I'd just like to point out that for python bindings at least, you can quite easily manipulate the LLVM infrastructure via ctypes as a shared object / dll -- no C required! Those of us interested in talking to LLVM from Lisps, either Common Lisp (via CFFI) or a scheme like PLT/Mzscheme, can also use the shared library interface. In fact, for the Common Lisp case, this is the _only portable_ (cross-implementation) way of talking to LLVM. If anyone's interested in Here is a one-off example of python using the shared library approach and Gor...

....org/devmtg/2018-04/) is this Friday, February 9th. Adrien Guinet has released [DragonFFI](https://github.com/aguinet/dragonffi/), a C Foreign Function Interface (FFI) library based on Clang/LLVM. It aims to provide broader ABI support than libffi and to work around the limitations of Python's cffi C parser through the use of Clang. ## On the mailing lists * Fāng-ruì Sòng started a discussion on [moving the LLVM developer-facing utility scripts to Python 3](http://lists.llvm.org/pipermail/llvm-dev/2018-January/120826.html). * Tanya Lattner is [looking for help](http://lists.llvm.org/piper...

...not occurring in the R console, >> but can be traced to a call to R_ParseVector() in R's C API:( >> https://github.com/rpy2/rpy2/blob/master/rpy2/rinterface_lib/_rinterface_capi.py#L509 >> ). >> >> Our specific setup is calling an embedded R from Python, using the cffi >> library. An error on end was the first possibility considered, but the >> puzzling specificity of the error (as shown below other parsing errors are >> handled properly) and the difficulty tracing what is in happening in >> R_ParseVector() made me ask whether someone on t...

...sh-client openssh-server openssh-sftp-server perl perl-base pinentry-curses procps python python-all python-all-dev python-apt python-cryptography python-dev python-keyring python-minimal python-pip python-pip-whl python-pycurl python2.7 python2.7-dev python2.7-minimal python3 python3-apt python3-cffi-backend python3-crypto python3-cryptography python3-dbus python3-dev python3-gi python3-keyring python3-minimal python3-pip python3-pkg-resources python3-pycurl python3-requests python3-setuptools python3-urllib3 python3-virtualenv ranger rsyslog rsyslog-gnutls systemd udev unattended-upgrades...

...re that the error is not occurring in the R console, > but can be traced to a call to R_ParseVector() in R's C API:( > https://github.com/rpy2/rpy2/blob/master/rpy2/rinterface_lib/_rinterface_capi.py#L509 > ). > > Our specific setup is calling an embedded R from Python, using the cffi > library. An error on end was the first possibility considered, but the > puzzling specificity of the error (as shown below other parsing errors are > handled properly) and the difficulty tracing what is in happening in > R_ParseVector() made me ask whether someone on this list had a s...

If SWIG can be made to do a good job with Python/Ruby/Perl etc bindings around LLVM, I would be very interested in this. I'm personally interested in seeing both Python and Ruby bindings, and in having them be as easily maintained as possible. I think it would be interesting to see what the SWIG-style solution can do in this direction as opposed to the C-binding approach. If it results in

...e that the error is not occurring in the R > console, but can be traced to a call to R_ParseVector() in R's C > API:(https://github.com/rpy2/rpy2/blob/master/rpy2/rinterface_lib/_rinterface_capi.py#L509). > > Our specific setup is calling an embedded R from Python, using the > cffi library. An error on end was the first possibility considered, > but the puzzling specificity of the error (as shown below other > parsing errors are handled properly) and the difficulty tracing what > is in happening in R_ParseVector() made me ask whether someone on this > list had...

...penssh-sftp-server perl perl-base pinentry-curses procps python > python-all python-all-dev python-apt python-cryptography python-dev > python-keyring python-minimal python-pip python-pip-whl > python-pycurl > python2.7 python2.7-dev python2.7-minimal python3 python3-apt > python3-cffi-backend python3-crypto python3-cryptography python3-dbus > python3-dev python3-gi python3-keyring python3-minimal python3-pip > python3-pkg-resources python3-pycurl python3-requests > python3-setuptools > python3-urllib3 python3-virtualenv ranger rsyslog rsyslog-gnutls > systemd...

...gt; openssh-sftp-server perl perl-base pinentry-curses procps python > python-all python-all-dev python-apt python-cryptography python-dev > python-keyring python-minimal python-pip python-pip-whl python-pycurl > python2.7 python2.7-dev python2.7-minimal python3 python3-apt > python3-cffi-backend python3-crypto python3-cryptography python3-dbus > python3-dev python3-gi python3-keyring python3-minimal python3-pip > python3-pkg-resources python3-pycurl python3-requests python3-setuptools > python3-urllib3 python3-virtualenv ranger rsyslog rsyslog-gnutls > systemd ude...

Hi, I've been lurking around the LLVM project for a couple of months now. The two recent threads about python bindings for LLVM ([1] and [2]), combined with the fact that I am looking for at GSoC project at the moment. Lead to the idea of making the "public" parts of LLVM SWIG[3]-friendly and basing a set of python bindings on this. My reasoning for doing it this way, is that it