From: "Andrew N. Balahonov" <sspp@cityline.ru>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hci.c:885: storage size of `iv' isn't known
Date: Tue, 3 Jan 2006 02:07:13 +0300 (MSK) [thread overview]
Message-ID: <Pine.LNX.4.63.0601030202140.23868@sundust> (raw)
In-Reply-To: <1136230278.24985.4.camel@localhost>
Yes, it helps.
Did you commit it for next release?!
--
Yours sincerely, Andrew N. Balahonov
1024D/3C340684 94B4 C3C5 8936 9DF5 A2B8 3E5C DB3A CC66 3C34 0684
On Mon, 2 Jan 2006, Marcel Holtmann wrote:
> Hi Andrew,
>
>> OS: Openwall GNU/*/Linux., http://www.openwall.com/Owl/
>>
>> ls -l /lib/libc[.-]*
>> -rwxr-xr-x 1 root root 3.9M 20 2003 /lib/libc-2.1.3.so
>> lrwxrwxrwx 1 root root 13 23 2004 /lib/libc.so.6 -> libc-2.1.3.so
>>
>> $ gcc -v
>> Reading specs from /usr/lib/gcc-lib/i386-unknown-linux/2.95.3/specs
>> gcc version 2.95.3 20010315 (release)
>
> check if the attached patch helps.
>
> Regards
>
> Marcel
>
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-01-02 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051231185308.E3D14130C8@sc8-sf-spam2.sourceforge.net>
2005-12-31 19:10 ` [Bluez-devel] hci.c:885: storage size of `iv' isn't known Andrew N. Balahonov
2006-01-02 11:31 ` Marcel Holtmann
2006-01-02 18:32 ` Andrew N. Balahonov
2006-01-02 19:31 ` Marcel Holtmann
2006-01-02 23:07 ` Andrew N. Balahonov [this message]
2006-01-03 9:56 ` Marcel Holtmann
2006-01-04 1:29 ` [Bluez-devel] the bluetooth-alsa driver tom
2006-01-04 1:36 ` Brad Midgley
2006-01-04 2:33 ` tom
2006-01-04 4:43 ` Brad Midgley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0601030202140.23868@sundust \
--to=sspp@cityline.ru \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox