emerging avifile, errors in Xft.h

H-Pi · Posted: Thu Dec 12, 2002 5:44 pm Post subject: emerging avifile, errors in Xft.h

when I try to emerge avifile-0.7.15.20020816 (dep from rhythmbox), the build fails and shows some errors:

chrish01 · Posted: Thu Dec 12, 2002 7:00 pm Post subject:

I just had the same problem...im gonna try to find that new (v 1.0 instead of .6 or so) xft.h file and see if that works.

sa · Guru Joined: 10 Jun 2002 Posts: 450

your problem seems to be that avifile is looking for the xft1 header files, but since the gentoo's xft2 ebuild deletes them, it see the xft2 headers and thinks that they are xft1....

not sure if this helps but at least you know what the problem is...

also, you could check /root/.Xft/ mabey your old xft headers are there, and you could temporaraly switch places with them and the xft2 ones and then switch back after avifile is compiled.

hth,
sa

H-Pi · Posted: Fri Dec 13, 2002 1:30 pm Post subject:

today there's a new version of aviplay(0.7.22.20021129) in portage, but now I get another error:

kENNy_ · Posted: Fri Dec 13, 2002 1:41 pm Post subject: ok, its not only my problem

I have got the same problem

sarnold · Posted: Tue Jan 28, 2003 6:08 am Post subject: I have a different problem...

But it´s still a problem with avifile:

Ladius · Posted: Tue Jan 28, 2003 9:53 am Post subject: Try this

Okay got this error myself, here's a log of what I did.

First a test of emerge "emerge -p avifile" showed qt should be installed before avifile which did occur. I did not at the time have "qt" in my "/etc/make.conf" file. Having had this problem for the last couple days I figured I'd try again with my newly clean system and it failed at the point quoted by sarnold above.

Okay, so its having problems so I thought lets try this manually and I went into the temp working directory at "/var/tmp/portage/avifile-X/work/avifile-X/". Did "make distclean" to try and "./configure". This went through but threw up errors about not being able to find qt's headers and libraries.

Did a "env-update" and verified that qt was found in my "/etc/ld.so.conf", it was. So I looked at the output of "./configure --help", avifile appears to try and autodetect the libraries it can build in so for some reason its not finding qt.

Just to make sure and tried "./configure --with-qt-dir=/usr/qt/3". This went through configure without giving me any errors regarding finding the qt libraries. Following this I did a manual make and it did complete without any problems. Unlike the results of previous ebuild which have failed with the "undefined reference to audio_init" error.

In my "/etc/make.conf" I had "-qtmt" in the "USE" variables, though when I put in "qt" along with "-qtmt" I still got this error. Removing the "-qtmt" and just having "qt" in my "USE" variable gives the same error as well.

I've started some hacking on the ebuild file for this as I suspect avifile is either being told or not told the correct information about qt. I'll let you know if I come up with anything (or at the very least I hope this helps others in their quest for a solution).

sarnold · Posted: Tue Jan 28, 2003 6:53 pm Post subject: Thanks

Okay, thanks for doing the homework that I didn't have time to do (last night was the first night of class, which I was busy getting ready for...).

I'm still a noob, but I think the ebuild file has the capability of passing specific parameter settings to configure (ie, the equivalent of --with-qt-dir=/usr/qt/3).

IIRC, there are plenty of examples in the e17-cvs ebuild. I'm trying to figure out how to setup a portage overlay for my own ebuild files, so this is probably a good opportunity to try that out.

I'll try and take a look at that tonight after work (unless you beat me too it ;-)

Steve

But setting the QT dir in the ebuild just seems like a workaround for the underlying issue (ie, why doesn't the avifile configure pick up the qt-dir path correctly?), but that's above my current paygrade...

Ladius · Posted: Tue Jan 28, 2003 7:16 pm Post subject: After Hacking and Some sleep...

Couple of updates on my end. Was up until about 4am hacking on this without success yet BUT I know for sure the error is being introduced via the ebuild file for this build. In total frustration I ran a manual configure and make. This was totally successful and installed without a problem.

I have come to the conclusion the ebuild is at fault, I don't believe the ebuild applying patches to the avifile distribution is at issue because those wouldn't have been removed by me doing a "make distclean" in the src directory of avifile.

Facts in evidence round up.

1) emerge avifile for 0.7.27.2003.... doesn't work and errors out fatally
2) the same source using what should be the same environment variables cleaned up (make distclean) and then configured using "./configure --with-qt-dir=/usr/qt/3" finishes the configure process without errors and builds without errors as well
3) at some time last night doing a distclean in the src directory and just a plain "./configure" resulted in the same build results found in fact 2 :!: :!:

Somehow, the ebuild isn't getting the correct environment variables and thusly isn't building avifile correctly. QT I think is related but it may just be the tip of the iceberge. What I suspect is that the ebuild is confusing itself with all the different declarations involving "/etc/make.conf" use variables. In intial testing of this theory I removed the check for "freetype" in the ebuild file which resulted in a good configure but failed compile (same error as normal).

I had to get some sleep so I stopped at that point.

As far as setting up the portage overlay just uncomment the "/usr/local/portage" line in your "/etc/make.conf" then make sure the directory exists itself. Put your ebuilds in that directory, ie for avifile you'd likely have the path "/usr/local/portage/media-video/avifile/avifile-test.ebuild" or something similar
it will want you to do a ebuild <file> digest before you can use it but that should work. I'm still cutting teeth on emerge and ebuilds so YMMV.

Brian

zhenlin · Veteran Joined: 09 Nov 2002 Posts: 1361

Quickfix: mv /usr/include/Xft /usr/include/Xft2; ln -s /usr/include/Xft1 /usr/include/Xft

When you're done emerging, change the symbolic link back. If you don't want to muck around with /usr/include directories, find a ./configure option for defining Xft directories.

Ladius · Posted: Thu Jan 30, 2003 3:24 am Post subject: Doesn't work for me

Did a quick search and the only xft1 libraries or headers inplace on my system reside in /usr/X11R6 directory. Specifically I've only got 2.0 libraries and headers save one instance of "libXft.so.1.1".

I'm not sure about any others and this system is a clean install but at least for me your solution doesn't work.

I've not had time to wade through this anymore work is keeping me a bit busy but perhaps this weekend I can look at it more. I still suspect the problem is related directly to the ebuild file because a manual configure/make works, but the use of the ebuild doesn't. I've not read much into emerge or ebuild but I assume they are pulling in the same environment variables my non-modified shell environment would have.

sarnold · Posted: Fri Jan 31, 2003 4:38 pm Post subject: Any movement?

Have you had any luck with this one yet? I've been busy too, so I haven't looked at it much either this week (but I did get e17 built last night, and my setup hacked a little).

I think you're right though; the ebuild should work, but it's not picking up all the right environment settings (and I'm not enough of a portage guru to know where to look).

I'll try and play with it this weekend too, but I also have many other things on my plate...

Steve

pilo · Posted: Sat Feb 01, 2003 12:58 am Post subject:

Ohohoh. I had the same error, and after some devastating editing in the ebuild, I decided to restore it from rsync, and try again. But instead, it updated avifile, from 0.7.27.20030122 to 0.7.17.20030130
Maybe you don't have to tweak your ebuilds after all. Test-merging now, will reply with results later.

One question: How could you relate the error to qt? It always found qt for me, and it configured it thesame in normal make as in emerge, even though emerge didn't work.

pilo · Posted: Sat Feb 01, 2003 1:08 am Post subject:

Dang. It still sucks.

Ladius · Posted: Sat Feb 01, 2003 8:24 am Post subject: Re QT

Well, I after doing the ebuild a couple of times, I canceled the ebuild just when it starting on the make process. Having installed/compiled lots of software on Solaris systems (where "interesting"* times can be had with path's , libraries and includes) I've learned to really watch any configure processes that I'm running.

Looking back into the configure lines I noted that qt wasn't found. Thats when I did some fiddling and tried compileing it from the var work directory manually as well as hacking on the ebuild file. I also made sure that qt (even though it was installed) was listed in my USE variables something that it wasn't at the time.

Still no joy, I'll try and use the new avifile that you mentioned is available.... maybe luck is smiling in my direction

* Interesting in the chinese curse sense of the word

pilo · Posted: Sat Feb 01, 2003 10:02 am Post subject:

The new was really 0.7.27.20030122-r1 but was called 0.7.27.20030130, I think, not seeing it before me.
It had some neat changes in the ebuild, but they didn't do shit. So I'll gather up some spare time when I can, and create my own, see if I can make it work this time. Btw, I get the error, even though it recognizes my qt path, and capabilities. I even tried to switch the /usr/kde/3/ and /usr/kde/3.1/ folders, no luck there. Maybe it isn't qt playing up, gonna closeread the log once more, now that I'm not dead tired.
Good luck to you, if you have the same prob. Will post an ebuild, as soon as it compiles.

Ladius · Posted: Sat Feb 01, 2003 10:08 am Post subject: yeah

As I said above I suspect its not qt anymore but rather environments not picking up properly...

ebuild fails
manual ./configure & make works producing a useable avifile

for me this limits the errors to either my environment or the ebuild..... unless I'm totally missing something (it is 210am so... thats not totally impossible)

pilo · Posted: Sat Feb 01, 2003 10:31 am Post subject:

Oh, well I can relate to that. I'll have to reboot into gentoo and start modding now..

pilo · Posted: Sat Feb 01, 2003 11:36 am Post subject:

Aha! I removed all configure options, but the linker's options at the end, and tada! It bloody worked! Shall I upload a testing ebuild? It might not work, but it certainly did for me! Whee!

pilo · Posted: Sat Feb 01, 2003 12:19 pm Post subject:

http://81.8.176.135/~mud/avifile-0.7.27.20030122-r1.ebuild
Try it, and please do change it if it sucks.

It should configure and compile without errors, I got some warnings for alocal, but that is selfinflicted.
Please tell me if it works, I would be so proud.. my first ebuild!

sarnold · Posted: Thu Feb 06, 2003 1:56 am Post subject: it's going now...

Okay, I'm trying it now. I'll let you know how it comes out...

Steve

Update: it worked for me too (but I didn't even look in your ebuild; I was busy and I just merged it and checked it later).

Thanks!

Steve

charlieg · Posted: Fri Feb 07, 2003 10:18 am Post subject: Hmm

I'm getting this error too.
_________________
Want Free games?
Free Gamer - open source games list & commentary

Open source web-enabled rich UI platform: Vexi

darktux · Posted: Fri Feb 07, 2003 9:19 pm Post subject: Re: Hmm

darktux · Posted: Fri Feb 07, 2003 9:49 pm Post subject: Re: Hmm

pilo · Posted: Sat Feb 08, 2003 8:11 pm Post subject:

Arghle. Now they released a new version with the new portage, and it fails the same way. How nasty, now I have to strip that one too. I'm getting seriously pissed with this avifile matter. Well, I'm glad it worked for some one else too, my work was not in vain.

_________________
"A stroll through a lunatic asylum shows that faith does not prove anything."