thanks,
ken
--
middlespot.com - see + save + share your search
> trying to compile mplayer from source i get a bunch of i2c.h errors.
> has anybody else encountered this? resolution?
Find out which kernel version people have successfully compiled mplayer
with and try with that. It might be that mplayer is intended to be
compiled for an older or newer kernel version.
If a kernel downgrade is needed, you might prefer to install using your
distro's package manager and wait until mplayer is updated to work with
the new kernel header for i2c.
thanks white. actually, i found my problem was an old version of i2c
headers sitting in /usr/local/include/linux which i removed. then i
started getting vo_ivtv errors. i did a middlespot.com search
(shameless plug for my new visual search interface) and found others
having the same error, the fix simply to disable ivtv. however, now i'm
getting the following error:
libao2/ao_openal.c:100: error: 'ALCint' undeclared (first use in this
function)
any ideas on fixing that? i don't really want to revert my kernel if i
don't have to.
thanks again!
Nope, works like a glove in 12.2 and has since 8.0 IMHO. I could build a
package, but not tonight. Just did enough physical labor to make my
lower back grunt warnings.
--
Virtue is a relative term.
-- Spock, "Friday's Child", stardate 3499.1
> trying to compile mplayer from source i get a bunch of i2c.h errors.
> has anybody else encountered this? resolution?
I have had no troubles but I use the svn MPlayer, the rc2 version is
pretty badly out of date.
Andrew
--
echo 'hfrarg...@tznvy.pbz' | \
tr 'a-m n-z' 'n-z a-m'
It build for me on Gentoo, using a customized K486 kernel, but this was
about six or seven months ago. I haven't tried a build since.
Mark.
--
Mark Hobley
Linux User: #370818 http://markhobley.yi.org/
> trying to compile mplayer from source i get a bunch of i2c.h errors.
> has anybody else encountered this? resolution?
>
> thanks,
> ken
>
>
Grab the most relevant and supported code via svn. That might be part
of the problem you're seeing. I use a new kernel and the svn compiled
fine. Granted, I'm not using Slackware at this time myself (I'm
repling to your post in comp.os.linux.misc).
--
Tim Greer, CEO/Founder/CTO, BurlyHost.com, Inc.
Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers
and Custom Hosting. 24/7 support, 30 day guarantee, secure servers.
Industry's most experienced staff! -- Web Hosting With Muscle!
> trying to compile mplayer from source i get a bunch of i2c.h errors. has
> anybody else encountered this? resolution?
Use the Slackbuild for it from SB.org:
http://slackbuilds.org/repository/12.2/multimedia/mplayer/
Works like a champ here.
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
The Usenet Improvement Project: http://improve-usenet.org
Ahhhhhhh!: http://brandybuck.site40.net/pics/relieve.jpg
Hi All, thank you so much for the suggestions and advice. It helped to
know others weren't having the same problems so I dug a little further.
I had the i2c error with both the 1.0rc2 and svn sources but the problem
was having old i2c headers in /usr/local/linux/include. Deleted those
but still had openal errors with the svn source which I fixed by doing a
configure --disable-openal. then it compiled through without errors and
now works well.
Thanks again,
Ken
Hi All, thank you so much for the suggestions and advice. It helped to
know others weren't having the same problems so I dug a little further.
I had the i2c error with both the 1.0rc2 and svn sources but the problem
was having old i2c headers in /usr/local/linux/include. Deleted those
but still had openal errors with the svn source which I fixed by doing a
configure --disable-openal. then it compiled through without errors and
now works well.
Thanks again,
Ken
--
Hi All, thank you so much for the suggestions and advice. It helped to
know others weren't having the same problems so I dug a little further.
I had the i2c error with both the 1.0rc2 and svn sources but the problem
was having old i2c headers in /usr/local/linux/include. Deleted those
but still had openal errors with the svn source which I fixed by doing a
configure --disable-openal. then it compiled through without errors and
now works well.
Thanks again,
Ken
--
thanks,
ken
--
I actually didn't have those issues myself, but I'm glad to hear the
issue was resolved. Often, if it's not the fact someone's missing
certain header files, it's common for it to be an issue of them being
out of sync or being too old. Sometimes people will install new
libraries or binaries, but there will be old copies in another path and
it, too, can cause issues with building (depending on where it's
looking for the headers).
--
http://middlespot.com - see + save + share your search
> anyway, thanks again, and apologies for the multiple posts on
> my previous message,
No problem, my ISP causes a lot of problems with who they outsource
their news services to (and I get errors, delays, and end up having
multiple posts myself sometimes).