Summary: | update jack-audio-connection-kit to version 0.100.7 shows some strange poutput | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Cramer <portage> |
Component: | [OLD] Unspecified | Assignee: | Eldad Zack (RETIRED) <eldad> |
Status: | RESOLVED INVALID | ||
Severity: | minor | CC: | sound |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | 3658-jack-audio-connection-kit-0.100.7.log |
Description
Michael Cramer
2005-12-10 05:19:15 UTC
I don't see any of these. looks like documentation generation errors. I'll try to see if I get it with +doc. can't reproduce this. Can you show me exactly which useflags you're using with jack? here are my useflags for this package bigmichi1 ~ # emerge jack-audio-connection-kit -pv These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] media-sound/jack-audio-connection-kit-0.100.7 +alsa (-altivec) +caps (-coreaudio) -debug +doc +jack-tmpfs +mmx +oss +portaudio +sndfile +sse 0 kB Total size of downloads: 0 kB Created attachment 74945 [details]
3658-jack-audio-connection-kit-0.100.7.log
build log
I made another stab at it, building with gcc-3.4.4, with the exact useflags, ldflags and features. Also I have the scanelf on my system as a part of paxutils... The only difference is the "-fweb" cflag. (and -march...) But still I don't understand how a cflag can affect this... anyway, I can't replicate this... reemerged "media-sound/jack-audio-connection-kit-0.100.7" today and warnings are gone, maybe something was broken on my system |