%% Dan Espen <dane_at_mk.telcordia.com> writes:
de> Drew Lebauer <asl_at_evolving.com> writes:
>> Xpm installed itself into /u/asl/opt/usr/openwin. The include/X11/X11 directo
>> ry
>> really does exist. What it installed (under /u/asl/opt) is (ls -RF):
>>
>> > usr/openwin/include:
>> > X11/
>> >
>> > usr/openwin/include/X11:
>> > X11/
>> >
>> > usr/openwin/include/X11/X11:
>> > xpm.h
de> If this is the way your installation looks, somethings wrong.
I agree with Dan that this is kind of bogus; however, it should work.
I've seen people put symlinks like X11 -> . in their include/X11
directories, so they don't have to worry about this. Then you can use
include/X11/X11/X11/X11/X11/xpm.h and it'll still work.
Not that I'm recommending that in any way, mind you :). Symlink loops
are all kinds of hassle. It's easier to just get the flags right.
de> usr/openwin/include/X11/xpm.h
de> I suggest starting over. Get this part right before proceeding.
You could just move the xpm.h file, you don't need to reinstall or
anything. There's no magic about the placement of this header.
But, I don't _think_ that's your problem based on your description.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith_at_baynetworks.com> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Jan 31 2000 - 14:09:56 GMT