On 10/11/06, Sean D. Rafferty <[EMAIL PROTECTED]> wrote:
--- Dan Nicholson <[EMAIL PROTECTED]> wrote:
> Thanks for the post, Sean. Opening a ticket is helpful because things
> aren't forgotten about there. But you've got my attention, so...
>
Firstly, thanks, Dan, for your quick reply. And the tips you provided.
Shall I still open the ticket, then, and apply the changes you suggested?
Yes, please open a ticket. I'm not really in a position to verify the
fix right now, and I'll forget about it.
> Typically with make, you can pass in any variable changes you want as
> arguments on the command line. Make will prefer the values you've told
> it about. So, rather than running sed on all the Makefiles to set the
> proper default, you can just tell make about it at build time.
>
> Could you see if this works?
>
> make JAVA_LIBS="$JAVA_HOME/lib" JAVA_INCLUDES="$JAVA_HOME/include"
>
Yes, it builds, and it's simple! Elegant even. Kinda makes me feel a tad
foolish for contriving my roundabout newbie method, but then again, I did learn
a bit about sed (like passing env. variables). I just assumed that make
followed Makefiles to the letter, didn't know I could override variables.
Glad to help. The nice thing about info like this is that you only
need to find out once. Be careful with the power, though. You can
completely hammer important variables that are set in other Makefiles
within the tree. The variable effectively becomes global when you pass
it in. There are some tricks to writing Makefiles so the variables are
protected, but I rarely see it done in practice.
Thanks again for reporting the issue.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
