Date: Thu, 16 Nov 2006 15:07:08 -0500 From: Dillon <lists@loveturtle.net> To: freebsd-current@freebsd.org Subject: Re: ZFS patches for FreeBSD. Message-ID: <455CC4EC.6060906@loveturtle.net> In-Reply-To: <455CBFD0.2020305@loveturtle.net> References: <1163701391.00638085.1163691003@10.7.7.3> <455CB8CA.8040603@icyb.net.ua> <455CBFD0.2020305@loveturtle.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Building shit in my vm is too slow to do it again to see if this is what
made the difference but i deleted the tree, resynced, patched, and
compiled again this time with -O1 instead of -O2 and it's working fine.
like i said, i don't know if that is what made the difference or if
something was screwed it up in my tree that went away when i deleted,
resynced, and repatched but i just thought i'd share that.
>
> Andriy Gapon wrote:
>> on 16/11/2006 17:21 Doug Ambrisko said the following:
>>
>>> I skipped the mkdir and used patch -p0. Everything looked to compile
>>> okay but when I kldload zfs is fails since the kernel doesn't
>>> have memset:
>>> %kldload zfs
>>> link_elf: symbol memset undefined
>>> kldload: can't load zfs: No such file or directory
>>> %
>>> Is there another change required?
>>>
>>
>> Hmm, I saw errors like this with some other 3rd party kernel module when
>> its sources had constructs like:
>>
>> struct some_struct s = {0};
>>
>> Changing the above initialization to explicit bzero() call helped in
>> that case, but I think that there should be some compiler flags or
>> something to handle this.
>>
>>
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?455CC4EC.6060906>