Menu
▾
▴
jazzplusplus-devel
|
From: D.B. M. <db...@ho...> - 2008-11-25 07:42:05
|
Greets, Are we happy with the revised build instructions? (I am ;) The reason I ask, is that a few sections in web-docs, notably the 'reporting bugs' page, has a few path and location statements which (now..) don't align with the new build instructions...might be a tad misleading for the uninitiated. I'll rework these sections and upload a patch, just as soon as Pete confirms this query. 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 |
|
From: Kevin C. <ke...@co...> - 2008-11-25 16:08:44
|
On 25 November 2008 at 7:42, "D.B. Moore" <db...@ho...> wrote: > Are we happy with the revised build instructions? I'm happy. -- Kevin |
|
From: Pete S. <pst...@gm...> - 2008-11-26 17:22:58
|
DB>> Are we happy with the revised build instructions? KC> I'm happy. So Kevin, Were you able to get a binary working? Don, Go ahead and make the other changes and send a patch. Thanks for doing this! On vacation in Colorado, Pete |
|
From: Kevin C. <ke...@co...> - 2008-11-26 17:35:02
|
On 26 November 2008 at 11:22, "Pete Stieber" <pst...@gm...> wrote: > Were you able to get a binary working? Not yet. I haven't had enough time to let one of my laptops stay running for hours on end -- the time it takes a PIII to compile all three packages. I've got a 4-day weekend, and can let a machine chug along. > On vacation in Colorado, Lucky guy. Where in CO? I've vacationed there about 4 times from the time I was a little kid. -- Kevin |
|
From: Pete S. <pst...@gm...> - 2008-11-26 17:40:11
|
PS>> On vacation in Colorado KC> Lucky guy. Where in CO? Loveland, near Ft. Collins. My daughter lives here. I'll be back with my normal development machines on Friday. Pete |
|
From: Kevin C. <ke...@co...> - 2008-11-26 22:37:33
Attachments:
_LOG.make.01
|
On 26 November 2008 at 11:22, "Pete Stieber" <pst...@gm...> wrote: > Were you able to get a binary working? I got wxWidgets built & installed. Likewise with tex2rft. Then I tried to build jazz. I have build logs, and environment setting stuff to look at. I could send it all. But, maybe you'd rather have just some special stuff? Anyway. I guess I'll poke at this a little more, maybe use more standard paths, e.g. /usr, to see if that helps. Thanks.... -- Kevin |
|
From: Pete S. <pst...@gm...> - 2008-11-27 18:53:40
|
Kevin, We build tex2rtf against a release version of the wxWidgets library. Did you build and install a release version of wx? Pete |
|
From: D.B. M. <db...@ho...> - 2008-11-27 00:06:39
|
Greets,
> To: jazzplusplus-devel
> Date: Wed, 26 Nov 2008 14:37:38 -0800
> From: kevinc
> Subject: Re: [jazzplusplus-devel] Revisiting web-docs after recent changes
>
>
> On 26 November 2008 at 11:22, "Pete Stieber" <pst...@gm...> wrote:
> > Were you able to get a binary working?
>
> Kevin wrote;
>
> I got wxWidgets built & installed. Likewise with tex2rft. Then I
> tried to build jazz.
>
> I have build logs, and environment setting stuff to look at. I could
> send it all. But, maybe you'd rather have just some special stuff?
>
> Anyway. I guess I'll poke at this a little more, maybe use more
> standard paths, e.g. /usr, to see if that helps.
>
> Thanks....
>
Hmm...when I checked the tex2rtf linkmap here, I discovered this ;
ldd /usr/local/bin/tex2rtf
linux-gate.so.1 => (0xffffe000)
libwx_gtk2_richtext-2.8.so.0 => /usr/lib/libwx_gtk2_richtext-2.8.so.0 (0xf7e80000)
libwx_gtk2_aui-2.8.so.0 => /usr/lib/libwx_gtk2_aui-2.8.so.0 (0xf7e18000)
libwx_gtk2_xrc-2.8.so.0 => /usr/lib/libwx_gtk2_xrc-2.8.so.0 (0xf7d8a000)
libwx_gtk2_qa-2.8.so.0 => /usr/lib/libwx_gtk2_qa-2.8.so.0 (0xf7d6c000)
libwx_gtk2_html-2.8.so.0 => /usr/lib/libwx_gtk2_html-2.8.so.0 (0xf7cd3000)
libwx_gtk2_adv-2.8.so.0 => /usr/lib/libwx_gtk2_adv-2.8.so.0 (0xf7c14000)
libwx_gtk2_core-2.8.so.0 => /usr/lib/libwx_gtk2_core-2.8.so.0 (0xf78db000)
libwx_base_xml-2.8.so.0 => /usr/lib/libwx_base_xml-2.8.so.0 (0xf78d1000)
libwx_base_net-2.8.so.0 => /usr/lib/libwx_base_net-2.8.so.0 (0xf78a5000)
libwx_base-2.8.so.0 => /usr/lib/libwx_base-2.8.so.0 (0xf777c000)
...blabla.....and, despite the fact that I didn't see the error you encountered, this
is actually wrong -- we *should* be linking against the custom wx libs installed
in /usr/local/wx289/.....yes??
Ergo, this is probably because in the tex2rtf build instructions, we don't actually
specify --with-wx-prefix=PREFIX at configure time, and the result is the tex2rtf
build ends up using system installed wx libs instead. This would seem counter-
intuitive, as we'd be expecting the tex2rtf build to see the LD_LIBRARY_PATH
variable in our ~/.bash_profile (which was set during the wx build phase), so my
best guess here is that the tex2rtf tree isn't honoring LD_LIBRARY_PATH variable.
As it turns out, my system-wide wx installation is indeed a debug version build, and
this would explain why I didn't encounter this same error building jazz itself.
Kevin, my suggestion is to rebuild/reinstall tex2rtf, but at configure time doing ;
../tex2rtf/configure --with-wx-prefix=/usr/local/wx289
This should result in tex2rtf being linked against our custom wx libs, and the
problem you found should go away.....
Regards,
Don
_________________________________________________________________
Your dream beach house escape for summer! Sign up for the Hotmail Road Trip today.
http://www.ninemsn.com.au/hotmailroadtrip |
|
From: Pete S. <pst...@gm...> - 2008-11-27 19:04:05
|
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?? 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. If you PATH and LD_LIBRARY_PATH are set correctly, you should need to use --with-wx-prefix. DM> As it turns out, my system-wide wx installation is indeed a debug DM> version build, This is not typical. DM> and this would explain why I didn't encounter this same error DM> building jazz itself. That's not my current guess. I believe Kevin's error was due to not finding release versions of the wxWidgets library. 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..... I don't think this will work. I think you need to install the release version of wxWidgets. Don, what was your PATH when you built tex2rtf? If our version of wx (/usr/local/wx289/bin) is first in your path, you will use the proper version of wx-config. Your ldd test seems to indicate this was not the case. Pete |
|
From: D.B. M. <db...@ho...> - 2008-11-27 20:28:44
|
> 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 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X