Re: [jazzplusplus-devel] Revisiting web-docs after recent changes

[D.B. M. <db...@ho...>]

> Date: Thu, 27 Nov 2008 13:04:00 -0600
> From: pstieber
> To: jazzplusplus-devel
> Subject: Re: [jazzplusplus-devel] Revisiting web-docs after recent changes
> 
> DM> Hmm...when I checked the tex2rtf linkmap here, I discovered this ;
> DM>
> DM>  ldd /usr/local/bin/tex2rtf
> DM>     linux-gate.so.1 =>  (0xffffe000)
> DM>     libwx_gtk2_richtext-2.8.so.0 => /usr/lib/libwx_gtk2_richtext-2.8.so.0
> DM> (0xf7e80000)
> DM>
> DM> ...blabla.....and, despite the fact that I didn't see the error you
> DM> encountered, this is actually wrong -- we *should* be linking
> DM> against the custom wx libs installed in /usr/local/wx289/.....yes??
> 
>PS> Correct.
> 
> DM> Ergo, this is probably because in the tex2rtf build instructions, we don't
> DM> actually specify --with-wx-prefix=PREFIX at configure time, and the
> DM> result is the tex2rtf build ends up using system installed wx libs instead.
> 
> PS>If you PATH and LD_LIBRARY_PATH are set correctly, you should need to
> PS>use --with-wx-prefix.
> 

I suppose you meant shouldn't here....and I agree....the prepended PATH &
LD_LIBRARY_PATH should take precedence..


> DM> As it turns out, my system-wide wx installation is indeed a debug
> DM> version build,
> 
> PS>This is not typical.
> 

Indeed....very little is 'typical' on my own system builds - it's part of the reason
I also test&check against something typical...like Debian...


> DM> and this would explain why I didn't encounter this same error
> DM> building jazz itself.
> 
> PS>That's not my current guess.  I believe Kevin's error was due to not
> PS>finding release versions of the wxWidgets library.
> 

I gave that consideration....if so, how come the jazz build found the right version?
(or a different version as the case may be)

> DM> Kevin, my suggestion is to rebuild/reinstall tex2rtf, but at configure time
> DM> doing ;
> DM>
> DM> ../tex2rtf/configure --with-wx-prefix=/usr/local/wx289
> DM>
> DM> This should result in tex2rtf being linked against our custom wx libs, and
> DM> the problem you found should go away.....
> 
> PS>I don't think this will work.  I think you need to install the release
> PS>version of wxWidgets.
> 

Well, I suppose if Kevin didn't install debug + release versions of wx. that 
-may- explain it...but then, going by his log, the jazz build -did- find the
release version???....so I presumed he did build both...otherwise things
wouldn't have complained?

>PS> Don, what was your PATH when you built tex2rtf?  If our version of wx
>PS> (/usr/local/wx289/bin) is first in your path, you will use the proper
>PS> version of wx-config.  Your ldd test seems to indicate this was not
>PS> the case.

$export

declare -x PATH="/usr/local/wx289/bin:/bin:/usr/bin:/usr/local/bin:/usr/bin:/opt/qt4/bin:/opt/gnome/bin:/opt/jdk/jdk/bin:/opt/wine/bin"
declare -x LD_LIBRARY_PATH="/usr/local/wx289/lib:"

as expected and looks good to me. A bit of a weird one, but in the end
I figured that it didn't -hurt- to throw tex2rtf the --with-wx-prefix switch,
and such might obviate (other) problems with the wx build (if any 
existed).  My best guess here is human error (mine ;-), probably part
of the human condition (laziness)....ie; didn't leave su before building
tex2rtf....certainly the deb build looks good (just checked).

Regards,

Don



_________________________________________________________________
Time for change? Find your ideal job with SEEK.
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2F%3Ftracking%3Dsk%3Atl%3Ask%3Anine%3A0%3Ahottag%3Achange&_t=757263783&_r=SEEK_tagline&_m=EXT