From: Takashi Iwai <tiwai@suse.de>
To: thomas charbonnel <thomas@undata.org>
Cc: thewade <pdman@aproximation.org>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Alsa and hdspmixer segfault
Date: Tue, 08 Feb 2005 20:25:36 +0100 [thread overview]
Message-ID: <s5hzmyeua4v.wl@alsa2.suse.de> (raw)
In-Reply-To: <1107563842.10562.10.camel@localhost>
At Sat, 05 Feb 2005 01:37:22 +0100,
thomas charbonnel wrote:
>
> thewade wrote :
> > > > Should I rebuild fltk?
> > >
> > > Not always, but what shows the stack trace?
> >
> > I rebuilt fltk from source, then rebuilt hdspmixer.
> >
> > I started with fltk-1.1.5rc2. That built but had many warnings. I
> > moved the libraries installed by fltk-1.1.4-1.1.fc2.dag.x86_64.rpm
> > and re-ran ldconfig. I then rebuilt and ran hdspmixer but had the
> > same error as before, line 68 in hdspmixer.cxx (see end of email).
> >
> > I tried to rebuild fltk-1.2.x but it didnt build.
> > Then I tried fltk-2.0.x and that built fine, but hdspmixer
> > complained about the declaration (or lack thereof) of many items.
> >
> > What should I do?
> > Thanks!
> > -thewade
>
> Hi,
>
> Sorry for the very late answer, I guess you found a solution since then.
> I reply for the record. I just experienced the same problem while
> testing the hdsp tools on amd64. It appears that the cr2 helper function
> from fltk, called from fl_draw_pixmap, which I use both in hdspconf and
> hdspmixer, is badly broken on x86_64 in fltk 1.1.4 (the version shipped
> with your FC3, Gentoo and maybe some other distros). I appears to be
> fixed in the latest version (1.1.6). Takashi, is there some autoconf
> magic we could add to warn about the problem ? Or maybe we could just
> add a line to the README file ?
You can check the string of "fltk-config --version", then.
It'll return like "1.1.6".
And, yes, describing the problem in README is always helpful.
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-08 19:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 4:44 Alsa and hdspmixer segfault thewade
2005-02-05 0:37 ` thomas charbonnel
2005-02-08 19:25 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-01 23:03 thewade
2004-10-01 18:33 thewade
2004-10-01 19:31 ` Lee Revell
2004-10-01 18:19 thewade
2004-10-01 18:14 thewade
2004-10-01 18:08 thewade
2004-10-01 18:16 ` Lee Revell
2004-10-01 17:54 thewade
2004-10-01 18:11 ` Takashi Iwai
2004-10-01 15:26 thewade
2004-10-01 17:23 ` Takashi Iwai
2004-10-01 17:49 ` Lee Revell
2004-10-01 17:55 ` Lee Revell
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=s5hzmyeua4v.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pdman@aproximation.org \
--cc=thomas@undata.org \
/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