On 08/12/2010, at 10:13 PM, john skaller wrote:

> 
> On Linux (Ubuntu 10.5 LTS, slicehost):
> 
> checking build/release-optimized/test/regress/drt/main1: failed: output does 
> not match
>  Starting ..
> + lib1 running
> + lib2 running
> + Its run
> 
> 
> The following tests failed:
>  test/regress/drt/main1.flx
> 
> main1 says:
> 
> print "Starting .."; endl;
> Dynlink::run_lib(Env::getenv "lib1");
> Dynlink::run_lib(Env::getenv "lib2");
> print "Its run"; endl;
> 
> So this looks like a bug in the build system because it works just fine when 
> I run it by hand:
> 
> skal...@skaller:~/felix/felix$ env 
> lib1=./build/release-optimized/test/regress/drt/lib1.so 
> lib2=./build/release-optimized/test/regress/drt/lib2.so flx 
> ./build/release-optimized/test/regress/drt/main1
> Starting ..
> lib1 running
> lib2 running
> Its run
> 



Added debugging print:

lib1=build/release-optimized/test/regress/drt/lib1.so, 
lib2=build/release-optimized/test/regress/drt/lib2.so
checking build/release-optimized/test/regress/drt/main1: failed: output does 
not match
  Starting ..
+ lib1 running
+ lib2 running
+ Its run
  
so the library names are correct. I checked this variant too (without the ./ on 
the lib name)
and it also works by hand. It also works on OSX.. maybe the environment isn't 
being passed?
And it just works by luck on osx? :)

Perhaps Erick has a clue .. hmm .. this is nonsense .. with debugging in the 
program too:

lib1=build/release-optimized/test/regress/drt/lib1.so, 
lib2=build/release-optimized/test/regress/drt/lib2.so
checking build/release-optimized/test/regress/drt/main1: failed: output does 
not match
  Starting ..
- lib1=build/release-optimized/test/regress/drt/lib1.so
- lib2=build/release-optimized/test/regress/drt/lib2.so
+ lib1 running
+ lib2 running
+ Its run
  
so the environment is getting to the program fine.

It WORKS from the command line but not in the test suite .. why??

--
john skaller
skal...@users.sourceforge.net





------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
_______________________________________________
Felix-language mailing list
Felix-language@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/felix-language

Reply via email to