search for: breakage

Normally the FreeBSD Project tries very hard to avoid ABI breakage in "Stable Branches". However occasionally the fix for a bug can not be implemented without ABI breakage, and it is decided that the fix warrants the impact of the ABI breakage. We have one of those situations coming along for RELENG_7 (what will become FreeBSD 7.1). The ABI breakage sh...

...h pci, today: - create 16 pci bridges - put one virtio device behind each boom Try it. I want to fix that. > > That's on x86. > > > > Besides x86, there are achitectures where IO is unavailable or very slow. > > > >> I don't think we should rush an ABI breakage if the only benefit is > >> claiming spec compliance. > >> > >> Regards, > >> > >> Anthony Liguori > > > > Why do you bring this up? No one advocates any ABI breakage, > > I only suggest extensions. > > It's an ABI breakage...

...h pci, today: - create 16 pci bridges - put one virtio device behind each boom Try it. I want to fix that. > > That's on x86. > > > > Besides x86, there are achitectures where IO is unavailable or very slow. > > > >> I don't think we should rush an ABI breakage if the only benefit is > >> claiming spec compliance. > >> > >> Regards, > >> > >> Anthony Liguori > > > > Why do you bring this up? No one advocates any ABI breakage, > > I only suggest extensions. > > It's an ABI breakage...

...IO ports in a system. That's why to make a pci express virtio device, we must allow MMIO and/or some other communication mechanism as the spec requires. That's on x86. Besides x86, there are achitectures where IO is unavailable or very slow. > I don't think we should rush an ABI breakage if the only benefit is > claiming spec compliance. > > Regards, > > Anthony Liguori Why do you bring this up? No one advocates any ABI breakage, I only suggest extensions. > > > > -- > > MST > > -- > > To unsubscribe from this list: send the line &...

...IO ports in a system. That's why to make a pci express virtio device, we must allow MMIO and/or some other communication mechanism as the spec requires. That's on x86. Besides x86, there are achitectures where IO is unavailable or very slow. > I don't think we should rush an ABI breakage if the only benefit is > claiming spec compliance. > > Regards, > > Anthony Liguori Why do you bring this up? No one advocates any ABI breakage, I only suggest extensions. > > > > -- > > MST > > -- > > To unsubscribe from this list: send the line &...

...> From: "Hal Finkel via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Richard Pennington" <rich at pennware.com> > Cc: llvm-dev at lists.llvm.org > Sent: Wednesday, September 7, 2016 7:37:50 AM > Subject: Re: [llvm-dev] [PowerPC] Recent branch too far breakage > > Hi Rich, > > It is hard to tell, but there was a bug fix made to the branch > relaxation code; perhaps the fix was not bug free -- Could this have > been caused by r280626? Is this a release or a debug build? -Hal > > -Hal > > ----- Original Message -----...

...Directory with ServicesForUnix 3.0 :) > -----Original Message----- > From: Daniel Eischen [mailto:eischen@vigrid.com] > Sent: Monday, July 14, 2003 2:13 PM > To: Robin P. Blanchard > Cc: John De Boskey; current@freebsd.org; Jacques A. Vidrine > Subject: RE: Help diagnosing NIS breakage ? > > > On Mon, 14 Jul 2003, Robin P. Blanchard wrote: > > > That did it.... > > > > Using latest -CURRENT sources, but backing out to > > src/lib/libc/gen/getpwent.c,v 1.81 gets NIS clients working again. > > Re-sync this in CVS ? > > The chan...

hello, klibc/include/signal.h include asm/signal.h which prefixes the __sighandler_t definition with a __user annotation. __user not being defined previously leads to a compilation breakage. It's the only occurrence for now, so the following dirty work-around works here : add a "#define __user" at klibc/include/signal.h head. regards, -- christophe varoqui <christophe.varoqui@free.fr>

All, The following patch fixes the build breakage on FreeBSD/powerpc: Index: lib/Target/PowerPC/PPCJITInfo.cpp =================================================================== --- lib/Target/PowerPC/PPCJITInfo.cpp (revision 51432) +++ lib/Target/PowerPC/PPCJITInfo.cpp (working copy) @@ -72,7 +72,7 @@ extern "C" void PPC64Compilati...

I'm using a recent revision of TOT (280704) to build clang/LLVM for PowerPC64 little endian. I'm getting an assembler error when building PPCInstPrinter.cpp: The error is: /tmp/PPCInstPrinter-84c835.s: Assembler messages: /tmp/PPCInstPrinter-84c835.s:7671: Error: operand out of range (0x0000000000008004 is not between 0xffffffffffff8000 and 0x0000000000007ffc) The offending line is

Ben Goodrich alerted me to some breakage coming from read.dcf() meaning you can no longer install or upgrade R packages. ChenLiang Xu was eagle-eyed and related this to gzfile() and he and Johannes Fichting confirmed that a downgrade to zlib1g from testing fixes things. Ben already filed a Debian bug report, you can see the gory detai...

Hi all, I know this issue has been discussed over and over again, but I'd like to voice my opinion while 3.0 is still fairly early-ish in the pipeline. So the issue is... API breakage. I understand and agree with the rationale why, namely faster development. But this principle should mean that for each breakage, the dude who makes the breakage should accompany the final commit (or something like that) with a *detailed* explanation about how to migrate existing codebases, relativ...

On Thu, Apr 12, 2018 at 6:29 PM, Josh Soref <jsoref at gmail.com> wrote: > Randall S. Becker <rsbecker at nexbridge.com> wrote: > >> >> -REGRESSTMP = "$(PWD)/regress" >> +REGRESSTMP = `pwd` >> >> tests interop-tests t-exec unit: regress-prep regress-binaries $(TARGETS) >> > > It looks like the problem is that pwd is in

Hi, The GStreamer flac plugin broke due to libflac 1.1.0 and libflac 1.1.1 not being ABI/API compatible. Skimming through the archives I see that this breakage was intentional. I think it is quite common understanding that when you have a stable release of something you don't break your API, you only add to it. If you want to break the API that should be done by going to a new major number, like libflac 2.0 and ideally make the two versions parallel i...

On Jul 13, 2011, at 8:09 AM, Jay Foad wrote: > On 13 July 2011 15:47, fly language <flylanguage at gmail.com> wrote: >> I don't really buy the manpower argument. Updating the release doc when >> breaking the frigging API is the Right Thing To Do and shouldn't take that >> long, when done when the change is fresh in memory. > > I regularly make small

...c filesystems introduces new VOP, vop_vptocnp. This would allow procstat(1) to work on devfs and pseudofs vnodes. As I understand, this would also improve Gnome experience on FreeBSD. All fs modules need to be recompiled. There was one very magisterial voice that objected against KBI breakage on stable branch in principle. In my opinion, the benefits of the bug fixes and functionality improvements with the proposed merges are much greater then inconvenience of the need to recompile out-of-tree fs modules. Changes were discussed with re@ to some extent. In case there is vocal objection...

...re not having trouble. For reference, I''m using RSpec and RSpec on Rails from trunk as of revision 1359. (Even more reference. I just took a five minute break and upgraded to RSpec 0.8.0 (r1440) and am having the same problem. Parallel Test::Unit tests aren''t showing any signs of breakage. I''ve put this in the tracker, as well. http://rubyforge.org/tracker/?func=detail&aid=8238&group_id=797&atid=3149 Best, Chris -- Chris Anderson http://jchris.mfdz.com

3.0.0pre2: non-recursive remote listing breakage Looks like pre1's fix broke something else. I noticed this when listing module/directory contents on servers known to be running versions 2.5.7 & 2.6.3. Not having (full) access to them, I replicated the errors using 2 machines on my home lan. # the machines lithium.elements.lan: the cl...

...roduced only for big-endian, little-endian ppc64 built ok. How can I fix it? I have no access to any PowerPC box to get to the bottom of issue. All the other tests are ok. Commit: https://github.com/llvm/llvm-project/commit/9c20156de39b377190d7a91783d61877b303fe35, svn revision: 359870. Reproduced breakage: http://lab.llvm.org:8011/builders/clang-ppc64be-linux-multistage/builds/18075 Thanks, Anton -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190514/ba6228c0/attachment.html>

I have just pushed out SYSLINUX 3.10-pre9. Please test it out, especially everyone who has been working with me on various systems trying to get them to work, or have had recent breakage. -hpa