tfries_at_umr.edu writes:
} Forwarded message:
} > 2) XPM_INCLUDES is still not being passed down to some directories:
} >
} > making all in ./libs...
} > gcc -O -pipe -I/usr/X11R5/sun4/include -target sun4 -c Picture.c
} >
} > This dies because it doesn't see my xpm.h file in /u/ericding/include...
} > the variable *is* being used, as far as I can see, in ./xpmroot/Makefile,
} > though. For now, I've manually stuck /u/ericding/include in the include
} > path.
} >
}
} I have seen this personally myself. I was just about to get my sysadmin
} to install fvwm, and was standing there when he was compiling it, when
} he showed me that he was going to have to edit every single makefile
} for every single module. Then we left because he suddenly felt tired.
...same thing here. our xpm stuff is in a really non-standard place. i
usually just let make barf, and then edit the source files that make it
barf to reflect the path...i'd really like to see this fixed, and i'd
fix it if i had the know-how. :)
--chris
--
this thing is slowly taking me apart grey would be the color if i had a heart
crode_at_iastate.edu - http://www.public.iastate.edu/~crode/homepage.html - dM
saving energy through apathy - the grabbing hands grab all they can - is there
a tiny part of me untouched--unsoiled by misery - that'a f*ckin' woodchuck...
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Oct 17 1995 - 20:00:43 BST