[overture] Re: _tnl_run_pipeline undefined
- From: "Henshaw, Bill" <henshaw1@xxxxxxxx>
- To: Barak Galanti <galanti@xxxxxxxxxxxx>
- Date: Tue, 16 Oct 2012 21:22:19 +0000
Hi Barak:
I checked, and you are currently not a member of the overture freelists
newsgroup.
Maybe you need to join gain.
It looks like you found the problem. Likely another version of OpenGL was
being
found in $(MOTIF)/lib64.
The errors you now get look familiar. I have fixed check.p so in the next
version it
will run through correctly in parallel. I think you may be ok now.
...Bill
________________________________________
From: Barak Galanti [galanti@xxxxxxxxxxxx]
Sent: Tuesday, October 16, 2012 2:02 AM
To: Henshaw, Bill
Cc: overture@xxxxxxxxxxxxx
Subject: Re: _tnl_run_pipeline undefined
Hi Bill,
According to our previous emails, we were communicating using the
freelists newsgroup. So I guess there another problem.
Now in the business of Overture:
It seems that the error is indeed a problem due to the LD_LIBRARY_PATH
I changed the definition in the following way:
export
LD_LIBRARY_PATH=${HDF}/lib64:${OpenGL}/lib64:${MOTIF}/lib64:${XLIBS}/lib64:${HDF}/lib64:${OpenGL}/lib64:$Overture/lib64:${APlusPlus}/lib64
That means OpenGL should appear firstly in the list of the libraries in
this environment variable. I had also to add the location of HDF, since
it is defined in an unusual place.
Now, when running the check.p (perl check.p) there are 2 tests. One of
them succeeded, but the second not. In the attachment you will find the
output of my check.
Many thanks,
Barak
On 10/15/2012 04:07 PM, Henshaw, Bill wrote:
> Hi Barak,
> If you want to submit questions to the freelists newsgroup you need
> to join the newsgroup. Perhaps you didn't do that yet.
>
> Since the error only occurs at run time I wonder if your
> LD_LIBRARY_PATH includes the Mesa directory. Have
> you googled this error?
>
> Regards,
> Bill
>
>
> ________________________________________
> From: Barak Galanti [galanti@xxxxxxxxxxxx]
> Sent: Monday, October 15, 2012 1:00 AM
> To: Henshaw, Bill
> Subject: Re: overture: galanti@xxxxxxxxxxxx post needs approval
>
> Hi Bill,
> I have not changed my email address, so it is quite surprising.
> Nevertheless, I see that you have got at least one of my 2 messages.
> The problem in my setup is that non of the test works: for all I get a
> problem with the Mesa library (see the attached file in my previous email).
>
> Any idea what I can do?
> Best regards,
> Barak
>
> On 10/15/2012 03:58 AM, Henshaw, Bill wrote:
>> Hi Barak,
>> Your posts are being rejected. Did you change your email address
>> from when you joined the mailing list?
>>
>> Not all the checks work in parallel. You will have to manual run
>> some examples to see if things are working.
>>
>> ...Bill
>>
>
>>
>> Hi All,
>> I am resending a message which was sent few days ago, but I have not
>> received any response.
>>
>> I am trying to build the parallel version of the Overture package.
>> In seems to be compiled and built correctly. However, in the check stage
>> (perl check.p), I get a strange error: _tnl_run_pipeline (undefined
>> symbol in the package libOSMesa). See the attached log file.
>> Many thanks,
>> Barak
>>
>>
>
>> Using the grid generator ../bin/ogen
>> checking square5.cmd...
>> mpirun -np 1 ../bin/ogen noplot nopause abortOnEnd ./square5.cmd> ogen.o=
>> ut
>> =2E./bin/ogen: symbol lookup error: /home/galanti/Overture/Mesa-7.2/lib64=
>> /libOSMesa.so.7: undefined symbol: _tnl_run_pipeline
>> -------------------------------------------------------------------------=
>> -
>> mpirun noticed that the job aborted, but has no info as to the process
>> that caused that situation.
>> -------------------------------------------------------------------------=
>
> This mail was received via Mail-SeCure System.
>
>
>
>
>
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals& computer
> viruses.
> ************************************************************************************
>
>
>
>
>
Other related posts:
