[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bug related to LIBPATH and %ConsVars???
From: |
Warren_Baird |
Subject: |
Bug related to LIBPATH and %ConsVars??? |
Date: |
Thu, 11 Apr 2002 10:07:56 -0400 |
I just came across something weird that looks like a bug to me. If I define a
construction variable LIBS=>"#lib", and then have something like:
LIBS=> "-lfoo -lbar",
LIBPATH=>"%LIBS"
in my environment, my "Program" command does the right thing (I see "-Llib
-lfoo -lbar as I would expect), but there is no dependancy created on libfoo.so
and libbar.so... If however, I manually expand the construction variable
LIBPATH=>"#lib"
or even
LIBPATH=>"$env->{LIBS}"
Then the exact same commands are executed, *AND* the dependancy on libfoo.so and
libbar.so is created as well.
Is it possible that % construction variables aren't expanded until after library
dependancies are created? that seems to be what I am seeing...
Warren
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Bug related to LIBPATH and %ConsVars???,
Warren_Baird <=