Not symlinked, but renamed all the freebsd8.3-i386 dir in
freebsd8.1-i386 under the modules path
(/usr/local/lib/enlightenment/modules/) with:
sudo find . -name *freebsd8.3* -execdir mv {} freebsd8.1-i386 \;
So, all wrongs paths $modulename/freebsd8.3-i386/ become
$modulename/freebsd8.1-i386.
On Sat, 23 Jun 2012 00:21:32 +0200 M77 said:
autotools when compiling e decided the osname/major version was different
from compiling modules. either something is vastly different in the build env
or build has been patched to make this happen. i have never seen this vary
EXCEPT when build env act
you what?? symlinked to a lower version?? never done that in my debian or
the servers i work with *-)
2012/6/22 M77
> I'm compiling modules from ports tree.
> Maybe there is a compiling option to override the installation path?
>
> It 's just a few hours that are within this mailing list, and I'
I'm compiling modules from ports tree.
Maybe there is a compiling option to override the installation path?
It 's just a few hours that are within this mailing list, and I've
already done something unnatural and impure:
sudo find . -name *freebsd8.3* -execdir mv {} freebsd8.1-i386 \;
It works p
How are you installing the modules? If they are from a operating system
provided repo it sounds like some of the E packages contained there are out
of date.
You should be able to simply manually edit the module path to what the
system is looking for as a work around though.
Be sure to report this
Hi,
I've installed all modules recently, but when I try to load someone I
get an error about path.
Something like: cannot find alarm/FreeBSD8.1-i386/module.so.
That is right because the module is in alarm/FreeBSD8.3-i386/module.so
I searched inside the configuration files but nothing useful...
H
