[E-devel] make dist and engage--wrong path!
Hi there, Previously to install packages I used: ./autogen.sh make make install But now Fedora requires to do: ./autogen.sh make dist then take the resulting tarball then do a: ./configure make make install For all the packages this seem to be fine except for engage and probably e_modules which then install the modules at /usr/lib/enlightenment/modules_extra/engage/linux-gnu-i386/* which is NOT what we want. I want it to be installed at: /usr/lib/enlightenment/modules_extra/engage/linux-gnu-i686/* which can then be loaded by DR17. In rpm building I can specify --target=i686 which will go to the correct directory but will then give me an i686 package which I do not want either. Is there a way to specify make dist in order than it install correctly in the *i686* path? Thanks for any info. -- With kind regards, Didier. Yum/apt repository for DR17/EFL: http://sps.nus.edu.sg/~didierbe Didier F.B Casse PhD candidate, Singapore Synchrotron Light Source (SSLS) National University of Singapore. -- With kind regards, Didier. Yum/apt repository for DR17/EFL: http://sps.nus.edu.sg/~didierbe Didier F.B Casse PhD candidate, Singapore Synchrotron Light Source (SSLS) National University of Singapore. --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] make dist and engage--wrong path!
Didier Casse wrote:
Hi there,
Previously to install packages I used:
./autogen.sh
make
make install
But now Fedora requires to do:
./autogen.sh
make dist
then take the resulting tarball then do a:
./configure
make
make install
For all the packages this seem to be fine except for engage and
probably e_modules which then install the modules at
/usr/lib/enlightenment/modules_extra/engage/linux-gnu-i386/*
which is NOT what we want. I want it to be installed at:
/usr/lib/enlightenment/modules_extra/engage/linux-gnu-i686/*
which can then be loaded by DR17. In rpm building I can specify
--target=i686 which will go to the correct directory but will then
give me an i686 package which I do not want either.
Is there a way to specify make dist in order than it install
correctly in the *i686* path?
Thanks for any info.
Didier,
Isn't this the same problem that I hit with x86_64 ?My fix was just to
have rpm install whatever directory make generates:
--- engage.spec.old 2005-05-29 05:32:34.0 -0400
+++ engage.spec 2005-05-30 10:35:01.0 -0400
@@ -44,7 +44,7 @@
%defattr(-,root,root)
%{_bindir}/engage
%{_libdir}/engage*
-%{_libdir}/enlightenment/modules_extra/engage/linux-gnu-i686/*
+%{_libdir}/enlightenment/modules_extra/engage/
%{_datadir}/engage*
%doc AUTHORS ChangeLog COPYING README
John
---
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] make dist and engage--wrong path!
On Thursday, 02 June 2005, at 10:05:06 (-0400),
John Ellson wrote:
Isn't this the same problem that I hit with x86_64 ?My fix was just to
have rpm install whatever directory make generates:
-%{_libdir}/enlightenment/modules_extra/engage/linux-gnu-i686/*
+%{_libdir}/enlightenment/modules_extra/engage/
John wins again.
Michael
--
Michael Jennings (a.k.a. KainX) http://www.kainx.org/ [EMAIL PROTECTED]
n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org)
---
Can we leave the world outside just for awhile, just for awhile?
Spend some time, you and I, under this bright, glorious sky? It's
been so long since I first saw you, but I still love the smile in
your eyes. -- Roxette, Church of Your Heart
---
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] make dist and engage--wrong path!
On 6/2/05, Michael Jennings [EMAIL PROTECTED] wrote:
On Thursday, 02 June 2005, at 10:05:06 (-0400),
John Ellson wrote:
Isn't this the same problem that I hit with x86_64 ?My fix was just to
have rpm install whatever directory make generates:
-%{_libdir}/enlightenment/modules_extra/engage/linux-gnu-i686/*
+%{_libdir}/enlightenment/modules_extra/engage/
John wins again.
Yes I indeed made the change recommended by John as he's very
enlightened. It's now
%{_libdir}/enlightenment/modules_extra/engage*
in my spec since the first time he mentionned it. C'mmon I'm not retarded.
But the problem is that when you do this:
enlightenment_remote -module-unload engage
followed by
enlightenment_remote -module-load engage
The system will simply tells you the following:
There was an error loading module named: engage
The full path to this module is:
engage/linux-gnu-i686/module.so
(See the attached screenshot)
It means that DR17 always look for the modules in the *linux-gnu-i686*
path and now my engage is as
([EMAIL PROTECTED]:SPECS)$ rpm -ql engage
[SNIP]
/usr/lib/enlightenment/modules_extra/engage/linux-gnu-i386/module.a
/usr/lib/enlightenment/modules_extra/engage/linux-gnu-i386/module.la
/usr/lib/enlightenment/modules_extra/engage/linux-gnu-i386/module.so
[SNIP]
For John it's probably *linux-gnu-x86_64*, but can DR17 load modules
which are in the paths other than *linux-gnu-i686*?
The core modules from the enlightenment package still are in the
*linux-gnu-i686* path by the way even after a make dist.
Is my question clearer now? Of course John wins but the question was
not about fighting with him or competing with him or whatever.
--
With kind regards,
Didier.
Yum/apt repository for DR17/EFL: http://sps.nus.edu.sg/~didierbe
Didier F.B Casse
PhD candidate, Singapore Synchrotron Light Source (SSLS)
National University of Singapore.
---
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] make dist and engage--wrong path!
Hi,
raster just enlightenment me on this puzzle and he just fixed it
in CVS. In engage configure.in:
- MODULE_ARCH=$target_os-$target_cpu
+ MODULE_ARCH=$host_os-$host_cpu
ok problem solved now. :)
With kind regards,
Didier.
Yum/apt repository for DR17/EFL: http://sps.nus.edu.sg/~didierbe
Didier F.B Casse
PhD candidate, Singapore Synchrotron Light Source (SSLS)
National University of Singapore.
On 6/3/05, Didier Casse [EMAIL PROTECTED] wrote:
whoops forgot to attach the screenshot. Here it is!
On 6/3/05, Didier Casse [EMAIL PROTECTED] wrote:
On 6/2/05, Michael Jennings [EMAIL PROTECTED] wrote:
On Thursday, 02 June 2005, at 10:05:06 (-0400),
John Ellson wrote:
Isn't this the same problem that I hit with x86_64 ?My fix was
just to
have rpm install whatever directory make generates:
-%{_libdir}/enlightenment/modules_extra/engage/linux-gnu-i686/*
+%{_libdir}/enlightenment/modules_extra/engage/
John wins again.
Yes I indeed made the change recommended by John as he's very
enlightened. It's now
%{_libdir}/enlightenment/modules_extra/engage*
in my spec since the first time he mentionned it. C'mmon I'm not retarded.
But the problem is that when you do this:
enlightenment_remote -module-unload engage
followed by
enlightenment_remote -module-load engage
The system will simply tells you the following:
There was an error loading module named: engage
The full path to this module is:
engage/linux-gnu-i686/module.so
(See the attached screenshot)
It means that DR17 always look for the modules in the *linux-gnu-i686*
path and now my engage is as
([EMAIL PROTECTED]:SPECS)$ rpm -ql engage
[SNIP]
/usr/lib/enlightenment/modules_extra/engage/linux-gnu-i386/module.a
/usr/lib/enlightenment/modules_extra/engage/linux-gnu-i386/module.la
/usr/lib/enlightenment/modules_extra/engage/linux-gnu-i386/module.so
[SNIP]
For John it's probably *linux-gnu-x86_64*, but can DR17 load modules
which are in the paths other than *linux-gnu-i686*?
The core modules from the enlightenment package still are in the
*linux-gnu-i686* path by the way even after a make dist.
Is my question clearer now? Of course John wins but the question was
not about fighting with him or competing with him or whatever.
--
--
---
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
