| Summary: | x11-base/xorg-x11-6.8.2-r1 can't find libfl | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | postmodern <brodigan> |
| Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | CC: | christian.korff, contact, craig, danielok, firestrand, ivan.piazza, juanmanuelmedina, killorbekilled, lami, mastertux, smileaf |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
postmodern
2005-04-01 17:04:26 UTC
Does "/usr/lib/libfl.a" exist? /usr/lib/libfl* does not exist. Could you try "emerge --oneshot sys-devel/flex", and see if that fixes the issue? Xorg-x11 depends on this, and it is the package that provides the libfl* files. I dunno why it isn't installed, as it should have been pulled in as part of the xorg emerge. It looks like you didn't read the documentation when you installed. http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6 Note the --emptytree argument. You can alternately use --newuse. oneshoting dev-lang/flex in then emerging xorg-x11 solved the problem. As for not reading the documentation, your going to have to be alittle more specific on what the mistake and solution were. Nevermind, I see my mistake now. I will adjust my scripts to the new stage2 -> stage3 procedure. *** Bug 88005 has been marked as a duplicate of this bug. *** *** Bug 88092 has been marked as a duplicate of this bug. *** *** Bug 88566 has been marked as a duplicate of this bug. *** *** Bug 89087 has been marked as a duplicate of this bug. *** *** Bug 89171 has been marked as a duplicate of this bug. *** *** Bug 92837 has been marked as a duplicate of this bug. *** *** Bug 93459 has been marked as a duplicate of this bug. *** *** Bug 98011 has been marked as a duplicate of this bug. *** *** Bug 98577 has been marked as a duplicate of this bug. *** *** Bug 99032 has been marked as a duplicate of this bug. *** the problem was fixed after I did: emerge flex I believe I have found the problem! I started from stage 2 and in that stage file libfl.a does not exist! however if I do a emerge -p flex it says it's already installed. thus the reason why flex is not brought in by an emerge xorg-x11 So the problem does not exist in the ebuild itself but rather the stage tarballs it includes an incomplete install of flex. This is all done from a chroot'ed stage2 tarball. here you'll see that flex is installed. both flex and flex++ exist but the libfl.a does not. hotaru / # emerge -p flex These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] sys-devel/flex-2.5.4a-r5 hotaru / # emerge -ep xorg-x11 | grep flex [ebuild N ] sys-devel/flex-2.5.4a-r5 hotaru / # nano a.cpp hotaru / # gcc -lfl a.cpp /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lfl collect2: ld returned 1 exit status hotaru / # flex flex flex++ hotaru / # ls -l /usr/lib/libfl.a ls: /usr/lib/libfl.a: No such file or directory hotaru / # find / | grep libfl.a hotaru / # It's not a problem, it's intentional. That's what comment #4 is about. Is it documented on why you intentionally do this? is there any *good* reason to intentionally break packages? It's not broken, if you follow the instructions. flex doesn't install static libraries under USE=build (among some other packages), because that takes up room on the stages/LiveCD's. That's why we specifically tell you what you need to do in the documentation. *** Bug 100433 has been marked as a duplicate of this bug. *** *** Bug 100517 has been marked as a duplicate of this bug. *** *** Bug 101072 has been marked as a duplicate of this bug. *** (In reply to comment #21) > It's not broken, if you follow the instructions. IMHO it is broken. If you use --newuse (as stated in comment #4 and in the docs), flex gets rebuilt after xorg-x11, so error stands. You have to do emerge flex to get rid of it, which is NOT in docs. Also, if you begin at stage1, it is IMHO not necessary to do even --newuse, because you did everything from scratch and din't change USE flags after bootstrap. And result is same (as I wrote in Bug 101072, sorry for the dup, didn't find this one). If it is necessary, maybe it should be documented, too. I would kind of view this as borkage also... Guessing the solution would be a use dep on flex though? *** Bug 102589 has been marked as a duplicate of this bug. *** |
