I found some more packages that will at least compile on amd64: app-sci/vis5d+-1.2.1 app-sci/netcdf-3.5.0-r3 dev-libs/szip-1.1 (needed for hdf) dev-libs/hdf-4.2.0 dev-libs/hdf5 I have been able to at least execute vis5d+ and some of the netcdf binaries, though I have not actually used them to work with data yet. Reproducible: Always Steps to Reproduce: 1. 2. 3.
In CVS, thanks!
Ok, as of 2/17/04, I only show these packages marked ~amd64: dev-libs/hdf-4.2.0(-r1) app-sci/netcdf-3.5.0-r3 the rest are completely missing any amd64 keywords: app-sci/vis5d+-1.2.1 dev-libs/szip-1.1 dev-libs/hdf5 Is this intentional, or is 10 days too quick for CVS to filter down?
Ok, scratch above comment for dev-libs/szip, I must have overlooked it. That still leaves: dev-libs/hdf5 app-sci/vis5d+
app-sci/vis5d+ was already marked ~amd64 for me. dev-libs/hdf5-1.6.1 has now been marked ~amd64. It compiled with lots of ugliness but maybe someone will test it.
Could you please check what's wrong with hdf4? See bug #52169, I can't reproduce this problem on x86
I had no problem emerging dev-libs/hdf-4.2.0-r3 on amd64. Using gcc-3.4.0-r4.
sorry, using gcc-3.3.3-r5. I forgot i switched profiles before the merge ;-)
Danny, could you try 3.4?
Ok, i can confirm the exact error with gcc-3.4.0-r4. LDFLAGS="-lm" is the proper way to handle it, though I don't know what triggers this.
Ok, it's a gcc 3.4 issue. Can reproduce it on x86 when using 3.4. Sorry for waking you up :-)
