http://bugs.openembedded.org/show_bug.cgi?id=2030
------- Comment #2 from [EMAIL PROTECTED] 2007-03-25 04:19 ------- I've done some research on this and its not a simple problem. The problem occurs due to the way we append to paths to create the directory structure. Starting with TOPDIR, we then append framents like "/tmp", "/work" and a host of other fragments. If any single one of these is a symlink, we have this problem. Anthing below TOPDIR should be created by bitbake and hence should not be a symlink, the only way they become symlinks is if someone creates them. As I read the code, TOPDIR shouldn't contain symlinks. The only way symlinks therefore occur is if people create them or set a path for something like TMPDIR in their local.conf which contain them. I therefore propose that we add some checks to sanity.bbclass which checks if TOPDIR and TMPDIR contain symlinks and error if they're found (since bitbake shouldn't intoduce them on its own). That would make this an OE bug rather than a bitbake one. -- Configure bugmail: http://bugs.openembedded.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ Bitbake-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bitbake-dev
