On 7 Sep 2008, at 19:27, Robert Arkiletian wrote:

> New problem. (I feel like a newbie)
>
> #make install
>
> failed. Here is the end of the output.
>
> lcUniConv/cp1251.h:36: warning: 'cp1251_mbtowc' defined but not used
> Archiving ../lib/libfltk_xutf8.a...
> Installing libfltk_xutf8.a in /usr/local/lib...
> make[1]: execvp: /usr/local/lib: Permission denied
> make[1]: execvp: ../lib/libfltk_xutf8.a: Permission denied
> make[1]: *** [install] Error 127
> make: *** [install] Error 1
>
> But how can I have permission denied when I'm root?

Well, I'm not sure the answer to that one but...

I would *strongly* advise against installing the patched version in  
the default location.
Rather, use the --prefix option to configure to put the built libs  
and their headers in some private location. Or just keep them in the  
build locations.

The reason for this is that the modified header files have the same  
names as the "real" fltk-1.1.x headers, and describe objects with the  
same names, and "similar" properties. But different sizes and API.

If you also have a "regular" 1.1.x installed, you can get into a  
situation where your code compiles against the patched headers, links  
(apparently successfully) to the un-patched libs, then crashes oddly  
at runtime.
Trust me, I know this to be true!

Actually, we could be heading for similar pain with 1.3, if we are  
not careful...

What I do is keep my "utf8" patched versions only in their build  
directories, and link against them there (fltk-config and fltk-utf8- 
config are smart enough to make that painless to do.) Ditto my 1.3  
versions actually...
Nowadays, only my stable 1.1.9 is actually installed in the system  
default locations.

-- 
Ian





_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to