Re: Wine 20041201 on FreeBSD 5.3-RELEASE

From: Jim Durham (jimd_at_nepinc.com)
Date: 12/31/04

  • Next message: Micheal Patterson: "Re: Mounting smbfs"
    To: freebsd-questions@freebsd.org, Matthew Bluestone <matthew.bluestone@gmail.com>
    Date: Fri, 31 Dec 2004 10:43:27 -0500
    
    

    On Wednesday 29 December 2004 12:05 am, Matthew Bluestone wrote:
    > (I apologize for replying to jason henson rather than the list; either
    > his reply-to was set individually, gmail doesn't correctly respect
    > reply-to (though it seems to in other cases), or I made an error.)
    >
    > Some of my response to jason and his later reply are included.
    >
    > > > (I didn't think that was so clear from the page.) I applied the
    > > > patch, rebuilt, and installed my kernel, and I continue to get the
    > > > same error.
    >
    > [snip]
    >
    > > > # patch <filename
    > > > and got normal-looking messages about discarding junk headers and
    > > > footers and applying patches in two spots. I checked the source file
    > > > /usr/src/sys/vm/vm_mmap.c and found the appropriate sections updated.
    > > > I had also edited a custom kernel config file in preparation for
    > > > building a custom kernel anyway, and I did
    > > > # cd /usr/src
    > > > # make buildkernel KERNCONF=MYKERNELNAME
    > > > # make installkernel KERNCONF=MYKERNELNAME
    > > > (substituting the appropriate name, of course).
    > > > The commands finished successfully, and I rebooted and got a
    > > > functioning system without a hitch.
    > >
    > > Looks like you did the right patch command.
    >
    > [snip]
    >
    > > Ok, first Kris responded to the thread with "It also clearly states (in
    > > the followup) that the kernel patch is no longer needed."
    > >
    > > Sounds like what Kris was saying was you just needed to cvsup your
    > > ports system and not do the patch anymore.
    > >
    > > "The wine-mmap.patch is no longer needed since that code has been
    > > #ifdef'd=20 out in the wine CVS."
    > >
    > > So you could just rm vm_mmap.c and cvsup your source then update your
    > > system and kernel. Depending on hold old your release is you should
    > > read UPDATING very carefully.
    >
    > As I said in my original post, my ports tree was updated the day
    > before I tried all that (which is well after the bug is listed as
    > being closed). Since I have apparently the latest port of wine and
    > have tried both with and without the kernel patch, I'm at a loss. I
    > thought this may be an issue with common enough components that
    > somebody on this list might have encountered and solved the same
    > problem.
    >
    > I figured that maybe I had misunderstood about the kernel patch no
    > longer being needed; maybe it was merged into CURRENT, but I'd have to
    > do it myself with my 5.3-RELEASE system.
    >
    > Incidentally, if I should *undo* this patch (I'm not a kernel hacker;
    > it intuitively seems that messing with the virtual memory manager,
    > esp. w/ code marked "this is messy; somebody who knows what he's doing
    > should fix it", could be a bad idea), I'd appreciate somebody's
    > letting me know.
    >
    > > Try emailing gerald@FreeBSD.org, he's the port maintainer for wine.
    >
    > I will also email gerald directly. Thank you.
    >

    I have basically the same setup (5.3 patchlevel 2 and Wine 120104) and get the
    same error.

    However, strangely enough, the error shows up on some apps that actually run.
    I was able to run Mozilla's Sunbird calendar program with no apparent errors
    on-screen, but , if I start it from a terminal window I see the heap error,
    but it runs anyway...

    I looked at the vm_mmap.c in the latest sources and the patch would not apply,
    so I assume the code has been merged, but couldn't really verify that. I
    searched for some of the variables from the patch and they weren't in the
    file. So, now I'm really confused as to what needs to be done.

    -Jim Durham

    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: Micheal Patterson: "Re: Mounting smbfs"

    Relevant Pages

    • Re: Wine 20041201 on FreeBSD 5.3-RELEASE
      ... (I apologize for replying to jason henson rather than the list; ... >> patch, rebuilt, and installed my kernel, and I continue to get the ... As I said in my original post, my ports tree was updated the day ... have tried both with and without the kernel patch, ...
      (freebsd-questions)
    • Re: problems with KB951746
      ... Blocking legitimate IP addresses responding on ports the firewall doesn't expect will cause problems. ... What I suspect is happening is that the patch is doing what it is supposed to do. ... It is also possible, but less likely, that your ISP's DNS servers are misconfigured and are unable to reply on odd source ports. ...
      (microsoft.public.windows.server.sbs)
    • Re: problems with KB951746
      ... Blocking legitimate IP addresses responding on ports the ... using the net will cause the firewall to block IPs more rapidly. ... I doubt the patch, or SBS, is the problem here. ... tried different forwarders, different DNS servers, and root hints only. ...
      (microsoft.public.windows.server.sbs)
    • Re: [PATCH] for acpi S1 power cycle resume problems
      ... > I was told that if I had a patch to submit for a baseline change that ... > have 3 RWC bits, ... whoever did that RWC patch for UHCI ports certainly should ...
      (Linux-Kernel)
    • Re: Patch available for shared em interrupts (Re: em, bge, network problems survey.)
      ... Note that this patch will not help you if you are not using the em ... shared irq that can be studied separately. ... <ACPI PCI bus> on pcib0 ... 2 ports with 2 removable, ...
      (freebsd-stable)