search for: nixpkgs

I applied the patch Gene wrote here: https://github.com/triton/nixpkgs/commit/06e146b2ce5eaaa54ebea061dd5797f89ae2c37c The tree after that commit is entirely based on gcc5. In order to do a test with gcc4.9, I reverted: https://github.com/triton/nixpkgs/commit/8ccc1f121f379f4d66ce0a66f581c49d25fb4e15#diff-d7222640d82ff920625e9311d05a0137 and then built two images,...

...ists.llvm.org/pipermail/llvm-dev/2016-January/094463.html Along with a downstream issue that needed to work around it: https://github.com/Homebrew/legacy-homebrew/issues/47149 And another downstream issue that outright patches out LLVM's @rpath support (authored by me): https://github.com/NixOS/nixpkgs/pull/30150 Anyway, I'm curious what the use case is for a relocatable libLLVM.dylib at the cost of downstream confusion. If it is indeed essential, could it be made an option in the build so that those of us who don't need relocatable LLVM libraries don't need to hack at the build file...

Hi all, I'm a maintainer for the llvm ecosystem for nixpkgs[1]. Currently only clang and llvm are up-to-date, but I'd like to move to building all of the packages listed on the release page for the latest version (and in particular, have libc++ and compiler RT integrated in with llvm/clang). Right now we're using the CMake build, with llvm and c...

An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20230405/bc2e0ea7/attachment-0001.htm>

On 4/5/23 10:31, Aki Tuomi wrote: > Hi! > The crash occurs inside libldap. > Aki Thanks Aki, It was against openldap 2.6.3. Subsequently, I tried openldap 2.6.4 which is in nixpkgs unstable, but I wasn't able to test this because of an issue at the Portunus/openldap end of things. I think I'm out of time for experimenting with ldap for now, but I may come back around to this later. In addition to Portunus/openldap, there is some movement in NixOS to package lldap...

Hi, I just tried to upgrade Nixpkgs to R 3.5.0, but unfortunately the new version fails its regression test suite. We configure the build using the flags "--without-recommended-packages", in case that's relevant. You can see a complete build log with all relevant information at [1]. Anyway, the test failures look like t...

...ot something that can be done with a stub library. This allows easy absolute or relative (with R(UN)PATH) linking. Comparatively, passing the right -rpath and -rpath link is manual and (in my opinion) harder to understand and cumbersome, and also not a solution for absolute linking. I work with Nixpkgs of NixOS, where absolute path linking is frequently an objective as part of a general principle of avoiding indirection. - YAML. The option for line-oriented structure allows for easy diffing with conventional line-based diffing tools, which is useful for debugging compatability issues. (e.g...

...DoS attack on the machine. The module repeatedly crashes when in this mode with a message similar to the one below. [root at keepalive:~]# uname -a Linux keepalive 4.15.17 #1-NixOS SMP Thu Apr 12 10:31:21 UTC 2018 x86_64 GNU/Linux It is the same problem as described on https://github.com/NixOS/nixpkgs/issues/39078. [ 782.525457] ------------[ cut here ]------------ [ 782.525467] refcount_t hit zero at ip_vs_conn_put+0x31/0x40 [ip_vs] in sh[15519], uid/euid: 497/497 [ 782.525477] WARNING: CPU: 0 PID: 15519 at .....

> On Apr 9, 2018, at 3:23 PM, James Y Knight via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > I'm not really clear on the actual benefits of the TBD file, and why Apple migrated to them in the first place. Shouldn't a dynamic library containing only the relevant parts (e.g. the dynamic symbol table) be roughly comparable in size? And, much simpler to support? I assume

On 23/04/2018 6:33 AM, Peter Simons wrote: > Hi, > > I just tried to upgrade Nixpkgs to R 3.5.0, but unfortunately the new > version fails its regression test suite. We configure the build using > the flags "--without-recommended-packages", in case that's relevant. You > can see a complete build log with all relevant information at [1]. > Anyway, the test...