Mike, I was just about to work on your problem when I saw your second email. All I can say is "Wow!" It's not often the compiler's at fault. Kudos for figuring that out. > Steve, Iâve spent all day trying to get LDM to build on a i386 solaris > machine. > > If I untar LDM 6.12.6 and run configure and make install, I get a nice 32 bit > addressing version of the software which doesnât give me a sufficient PQ > size. > > If I do it again and add the -m64 option to the compiler, I get regutil > linking errors. Iâve scanned the directories and logs and canât manage > to find a solution that works. > > Iâm attaching log files from the config and install. config.log.1 and > install.log.1 are the successful 32 bit installs and versions 2 are the > unsuccessful logs. > > Iâm also giving you the results of dumping c99 -flags to a file called > cflags.info. > > This is the results of running isainfo -v on the machine. Iâve built a > successful 64 bit version on three sparc machines but today wasnât my day > for getting the i386 running. I have abandoned the idea of doing this > without MMAP so thatâs not the problem, Iâm trying to keep this as simple > as possible to get LDM up and running. Any suggestions you have would be > appreciated. > > > isainfo -v > 64-bit amd64 applications > cx16 mon sse3 sse2 sse fxsr mmx cmov amd_sysc cx8 tsc fpu > 32-bit i386 applications > cx16 mon sse3 sse2 sse fxsr mmx cmov sep cx8 tsc fpu > > -Mike > > I have solved the problem with compiling LDM on my i386 machine. Itâs a > compiler bug on the local machine and not an LDM problem. I was able to > compile on a different machine with a newer compiler and it works on both > machines. You may close this ticket. > -Mike Rost Regards, Steve Emmerson Ticket Details =================== Ticket ID: ZCO-613432 Department: Support LDM Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.