We should probably hold off on patching right now? The submission compiles and runs fine with XP V2, msvc VC7 and with SUSE 9.2 and GCC 3.3.4. We should pick the Linux/GCC version that we run Harmony builds regularly on and make all the changes in one shot to fix the compile on that. Has this version already been identified?
Thanks, Rana Dasgupta Intel Middleware Development On 5/4/06, Ivan Volosyuk <[EMAIL PROTECTED]> wrote:
Great! Good progress. Here is mine: gcc (GCC) 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9) Gcc-4.x is masked in gentoo, so I have started with gcc-3.4.6. It was harder then before. I have made number of changes in jitrino/**/Set.h to get it compile. A few more changes in other places in jitrino, and it builds and eclipse works again. I am not sure it still builds on gcc-3.3.6. All changes should be portable to 3.3.6 IMHO except for renaming "ext/stl_hash_map.h" to "ext/hash_map.h". Looks like the compile-time check for GCC version is needed here. Is it ok to attach patch here or should I use JIRA? -- Ivan On 5/4/06, Mark Hindess <[EMAIL PROTECTED]> wrote: > > > On 4 May 2006 at 21:43, "Ivan Volosyuk" <[EMAIL PROTECTED]> wrote: > > > > DRLVM compiled fine on my home computer. Eclipse works. > > Configuration: > > Gentoo stable, not much up to date. > > gcc (GCC) 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8) > > Binutils: 2.16.1 > > Kernel: 2.6.15.6 > > I'm using Debian testing and I'd tried downgrading everything except > binutils which would have been a little too much trouble. So I ended up > building a chroot image with Debian sarge/stable. I then installed the > ant and ant-optional packages from testing. The build then worked! > > The key package versions required were: > > ant-optional/testing 1.6.5-5 > ant/testing 1.6.5-5 > binutils-dev/stable 2.15-6 > binutils/stable 2.15-6 > g++-3.3/stable 1:3.3.5-13 > g++/stable 4:3.3.5-3 > gcc-3.3-base/stable 1:3.3.5-13 > gcc-3.3/stable 1:3.3.5-13 > gcc/stable 4:3.3.5-3 > libstdc++5-3.3-dev/stable 1:3.3.5-13 > libstdc++5/stable 1:3.3.5-13 > > > One build issue: > > When using /usr/bin/ant compilation failed even for ant-1.6.5, I have > > compiled custom ant in home directory and it worked for me. > > > > I'm going to upgrade to Gcc 4.x and fix the compilation on it. > > Cool. Keep us posted with progress. > > Regards, > Mark. > > > On 5/4/06, Mark Hindess <[EMAIL PROTECTED]> wrote: > > > > > > > > > On 4 May 2006 at 13:58, "Andrey Chernyshev" < [EMAIL PROTECTED]> > > > wrote: > > > > > > > > Mark Hindess wrote: > > > > > Using gcc 3.3.6, I'm stuck building native of vm.jitrino with link > > > > > errors: > > > > > > > > I can suggest that link errors may be result of previous compilation > > > > with GCC 4.0 and then subsequent attempt to link with GCC 3.3.6. > > > > You may do the "build clean" first if you are changing the things > like > > > > compiler, or, manually delete the directory > > > > Harmony/build/lnx_ia32_gcc_release before rebuilding. > > > > > > Yeah, that was the first thing I tried. That got rid of some errors > but > > > left me with the ones I posted. > > > > > > > We didn't check that this can be built on a whole variety of > existing > > > > Linux distributions and different GCC versions, this would be a huge > > > > task that only Harmony can afford to do :) > > > > > > Absolutely. I'm certainly not complaining. I'm just trying to help > > > others avoid tripping over the same problems that I'm seeing ... and > > > hopefully fixing. ;-) > > > > > > > One of the configurations that worked fine was: > > > > SuSE Linux 9.2 (i586) > > > > kernel release: 2.6.8-24-smp > > > > gcc (GCC) 3.3.4 (pre 3.3.5 20040809) > > > > > > This is v. useful. Thanks. > > > > > > Hmm. That is a slightly older gcc than the version I'm using. As a > > > first step, I might try to build with that exact version. If/when I > get > > > something that works, I can start to investigate the differences. > > > > > > Regards, > > > Mark. > > > > > > > > > > > > > ------=_Part_3248_11123540.1146764639573-- > > >
