search for: libwhatever

...ed the previous discussions on the plan here? > At this point I believe that this concern is non-existent per the read-only individual repo. The read-only repo is only useful if you don’t intend to contribute stuff back upstream. There is no convenient workflow for cloning libunwind / libc++ / libwhatever, hacking on it, and sending pull requests. > We can leave it there :) > There have been extensive discussions, a BoF, and documentations, please refer you to these first (granted we haven't really talked about libunwind, but I'm not sure many people will be strongly opposed to libunw...

...repo. > > The read-only repo is only useful if you don’t intend to contribute stuff back upstream. > > Your point was about CI... > (unless you're working on some CI that would fix bugs and send PR?) > > There is no convenient workflow for cloning libunwind / libc++ / libwhatever, hacking on it, and sending pull requests. > > We considered git-svn for this though. > > > > > We can leave it there :) > > There have been extensive discussions, a BoF, and documentations, please refer you to these first (granted we haven't really talked about...

I'm trying to run purify on CentOS on an Intel Pentium 4/630 processor. Purify does not like the 64bit code. Is there some way to compile and run programs so that they are only using the 32 bit model? I tried gcc -m32 but then the system libraries come up missing. Purify engine: Error: Couldn't open the file crt1.o Purify engine: Error: Couldn't open the file crti.o Purify

Hi, I'm completly new to linux and therefore I don't really have a clue about it. I'm using Debian Lenny 64bit with kde4.1 and I want to install wine 0.9.52 ... Now my question is, what do I have to do to get a working wine 0.9.52 with all dependencies and all that other stuff(libwine, libwhatever etc.) that it needs to run perfectly ? Thanks in advance.

On 9 May 2017, at 15:58, Mehdi AMINI <joker.eph at gmail.com> wrote: > I'd expect any CI system to be able to cache this. > Also if you're issue is archiving a lot of build artifacts, the constant cost of the checkout isn't gonna matter that much. > Finally, the read-only individual repo can still be used by CI, which address this entirely. If we want to pull in new