search for: frontend

...defined userdb in auth-ldap.conf.ext userdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext } the same config again in auth-system.conf.ext The problem is that dovecot always reports back that the user is unknown. I turned on ldap debug and got the following Sep 6 13:06:10 kolab-frontend dovecot: auth: Debug: ldap(tobi.szyndler at datapark.li,213.196.149.1,<88FSBrXlSQDVxJUB>): pass search: base=dc=datapark,dc=li scope=subtree filter=(&(objectClass=posixAccount)(uid=tobi.szyndler at datapark.li)) fields=mailHost Sep 6 13:06:10 kolab-frontend dovecot: auth: Error: ldap_sea...

...it is not currently part of xenbr0. I can see multiple instances of the domain''s vbds and vif if I use xenstore-ls: $ sudo xenstore-ls | less [...] local = "" domain = "" [...] 111 = "" 2049 = "" domain = "test1" frontend = "/local/domain/111/device/vbd/2049" dev = "sda1" state = "4" params = "mainvg/domu_test1_root" mode = "w" frontend-id = "111" type = "phy" physical-device = "fd:15"...

upstream commit 7e96287ddc4f42081e18248b6167041c0908004c Author: Vivek Goyal <vgoyal@in.ibm.com> [PATCH] kdump: introduce "reset_devices" command line option Resetting the devices during driver initialization can be a costly operation in terms of time (especially scsi devices). This option can be used by drivers to know that user forcibly wants the devices to

...i wrote: > > > On 11/06/2020 00:49, Michael Kruse wrote: >> Am Mi., 10. Juni 2020 um 10:04 Uhr schrieb Doerfert, Johannes via >> flang-dev <flang-dev at lists.llvm.org>: >>> I'm not against a subproject *but* if we also move the existing >>> llvm/lib/Frontend stuff, that would introduce a dependence from >>> llvm-core to this project, which I think is uncommon. We could also >>> have >>> both. At the end of the day it depends on the benefit we would get from >>> an independent subproject. >> >> If we have...

On 6/11/20 4:04 PM, James Y Knight wrote: > I think the expectation is that LLVM remains at the bottom of the > dependency tree, with frontend-support depending on LLVM, and Clang and > Flang depending on frontend-support (and LLVM). > > Not everything which makes sense to share between clang and flang makes > sense to be part of llvm core. E.g., implementation of a GCC-compatible > command-line compiler-driver seems like i...

...| 2 +- common/parallel/parallel.c | 2 +- common/progress/progress.c | 2 +- common/utils/Makefile.am | 2 +- common/utils/utils.c | 2 +- common/utils/{guestfs-internal-frontend.h => utils.h} | 6 +++--- common/visit/visit.c | 2 +- common/windows/windows.c | 2 +- docs/C_SOURCE_FILES | 2 +- erlang/main.c | 2 +- fish/fish.h...

I am trying to compile the Java frontend in https:/ llvm.org/svn/llvm-project/java/trunk If there are another preferred Java frontend available, and it is suited for translating Java bytecode to LLVM bytecode, I'd be happy to use that frontend instead. thanks, Andreas On Thu, Sep 17, 2009 at 4:03 PM, Chris Lattner <clattner a...

...arallel/parallel.c | 2 +- common/progress/progress.c | 2 +- common/utils/Makefile.am | 2 +- common/utils/cleanups.c | 2 +- .../utils/{guestfs-internal-frontend.h => guestfs-utils.h} | 6 +++--- common/utils/utils.c | 2 +- common/visit/visit.c | 2 +- common/windows/windows.c | 2 +- docs/C_SOURCE_FILES...

Am Mi., 10. Juni 2020 um 10:04 Uhr schrieb Doerfert, Johannes via flang-dev <flang-dev at lists.llvm.org>: > I'm not against a subproject *but* if we also move the existing > llvm/lib/Frontend stuff, that would introduce a dependence from > llvm-core to this project, which I think is uncommon. We could also have > both. At the end of the day it depends on the benefit we would get from > an independent subproject. If we have non-conditional dependencies llvm-core->frontend-su...

I am looking for a way to translate Java bytecode to LLVM bytecode and the LLVM Java frontend seem like a good match for initial testing. But after checking out the svn version of the Java frontend I get the following error when running configure configure: error: cannot find install-sh or install.sh in ../../autoconf ./../../autoconf This error persisted even after successfully regen...

I was hoping to introduce a new top level library in llvm/lib/Frontend for code that is (mainly) used by LLVM frontends but not by one exclusively. At first, I would place the OpenMP-IR-Builder [1] (and related code [0]) there. This Builder translates "OpenMP directives" to LLVM-IR and is supposed to be reused in Flang. First, I tried to place the OpenMP-IR...

Hi Andreas, Since you're only looking for a Java frontend, I suggest you only build the Java frontend of vmkit and don't pass any pnet or mono information to the configure script. I haven't updated the pnet part of the .Net frontend. On the other hand, the Java frontend is up-to-date. Nicolas Andreas Saebjoernsen wrote: > Thanks, I am now...

Some old Windows frontends fail to transition through the xenbus Closing state and move directly from Connected to Closed. Handle this case properly. Signed-off-by: Paul Durrant <paul.durrant@citrix.com> Cc: David Vrabel <david.vrabel@citrix.com> Cc: Wei Liu <wei.liu2@citrix.com> Cc: Ian Campbell <ian....

...extImpl have member variables with those names. Do you know how to solve this problem? thanks, Andreas On Thu, Sep 17, 2009 at 4:22 PM, Chris Lattner <clattner at apple.com> wrote: > > On Sep 17, 2009, at 4:17 PM, Andreas Saebjoernsen wrote: > > I am trying to compile the Java frontend in https:/ > llvm.org/svn/llvm-project/java/trunk > If there are another preferred Java frontend available, and it is suited > for translating Java bytecode to LLVM bytecode, I'd be happy to use that > frontend instead. > > > That is really old and out of date, I'm...

On 11/18, Chris Lattner wrote: > > > > On Nov 12, 2019, at 9:19 PM, Doerfert, Johannes via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > I was hoping to introduce a new top level library in llvm/lib/Frontend > > for code that is (mainly) used by LLVM frontends but not by one > > exclusively. At first, I would place the OpenMP-IR-Builder [1] (and related > > code [0]) there. This Builder translates "OpenMP directives" to LLVM-IR > > and is supposed to be reused in Flang...

On Sep 17, 2009, at 4:17 PM, Andreas Saebjoernsen wrote: > I am trying to compile the Java frontend in > https:/llvm.org/svn/llvm-project/java/trunk > If there are another preferred Java frontend available, and it is > suited for translating Java bytecode to LLVM bytecode, I'd be happy > to use that frontend instead. That is really old and out of date, I'm sure it do...

On Sep 17, 2009, at 3:59 PM, Andreas Saebjoernsen wrote: > I am looking for a way to translate Java bytecode to LLVM bytecode > and the LLVM Java frontend seem like a good match for initial > testing. But after checking out the svn version of the Java > frontend I get the following error when running configure > > configure: error: cannot find install-sh or install.sh in ../../ > autoconf ./../../autoconf > > This error...

...the parent directory which you can install Note: Please choose the following xen specific optiions in kernel configuration. Processor type and features ---> Subarchitecture Type (PC-compatible) ---> (X) Enable Xen compatible kernel Bus options (PCI etc.) ---> [*] PCI support [*] Xen PCI Frontend [ ] Xen PCI Frontend Debugging (NEW) Device Drivers ---> XEN ---> [*] Privileged Guest (domain 0) <*> Backend driver support (NEW) <*> Block-device backend driver (NEW) <*> Block-device tap backend driver (NEW) <*> Network-device backend driver (NEW) (8) Maximum simult...

...he stack for a thread you've created. > > > FWIW, *this* is what I was trying to get across. Not that it wouldn't be a > callback-based mechanism, but that it should be a fully general mechanism > rather than having something to do with warnings, errors, notes, etc. If a > frontend chooses to use it to produce such diagnostics, cool, but there are > other use cases that the same machinery should serve. > > > How about this: keep the jist of the current API, but drop the "warning"- or > "error"-ness of the API. Instead, the backend just incl...

...all: http://lists.llvm.org/pipermail/flang-dev/2020-June/000379.html -Andrzej On 11/06/2020 23:06, Doerfert, Johannes wrote: > On 6/11/20 4:04 PM, James Y Knight wrote: >> I think the expectation is that LLVM remains at the bottom of the >> dependency tree, with frontend-support depending on LLVM, and Clang and >> Flang depending on frontend-support (and LLVM). >> >> Not everything which makes sense to share between clang and flang makes >> sense to be part of llvm core. E.g., implementation of a GCC-compatible >> c...