From owner-freebsd-current@FreeBSD.ORG Fri Dec 17 16:54:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A437216A4CE for ; Fri, 17 Dec 2004 16:54:08 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42CF443D2F for ; Fri, 17 Dec 2004 16:54:08 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iBHGv3Tg061695; Fri, 17 Dec 2004 09:57:03 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41C30F0F.3080302@freebsd.org> Date: Fri, 17 Dec 2004 09:53:35 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt Rowley References: <20041211004038.GC50516@dragon.nuxi.com> <11A4B937C9C745F2DD5B75EC@elric.arin.net> <20041217081458.GB10368@dan.emsphone.com> <41C30321.5060209@freebsd.org> <22C3670E71A83C719BAC25E9@elric.arin.net> In-Reply-To: <22C3670E71A83C719BAC25E9@elric.arin.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org cc: Dan Nelson Subject: Re: FreeBSD 5.3 and Adaptec raidutils (again) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2004 16:54:08 -0000 Matt Rowley wrote: >>> Yes; you can work around it by declaring a temp variable, assigning it >>> the value of attachedTo, making whatever modification is necessary, >>> then assigning attachedTo=temp. Do this every time you get that error. >>> You /might/ also be able to just remove the PACKed attribute from the >>> attachedTo field, but that will cause havoc if the struct is supposed >>> to line up with something generated by the card. >>> >> >> I'd highly recommend against removing the packed attribute. > > > :) It does compile, when you remove packed. After commenting out the > unneeded semaphore union struct in basic.hh, the whole thing compiles. > The resulting raidutil binary spews out the same error as the one from > the current binary port about "Engine connect failed: COMPATIBILITY > number"... but that's to be expected. > > Scott, is Dan's suggestion about using a temp variable and to stop > passing by reference the right way to go? > > --Matt I agree with Dan's temp variable solution. I'm also open to discussion on the compatibility number thing. If you can make it work with the value provided by the current driver, then please do. Otherwise we can discuss reverting the value. Scott