> Sorry that I was not of more help. It does seem necessary to specify
> the linker path to 64-bit libraries on the system. The fixes in
> libtool 2.2 seem to primarily be to assure that the correct compiler
> support and system libraries are used. Libtool queries GCC for the
> built-in linker s
> If you know of a fully automatic way that works, and that not only for
> your system your distribution your current version, but for strictly
> more systems, distributions, versions, compilers and compiler versions
> for which the current method works then we're all ears.
Are there any chances
> It would be nice if there were standard file naming conventions. On
> my Solaris 10 system, the operating system uses one convention and GCC
> uses another. Packages may use another.
Do you see chances for a mapping between the available approaches?
Can the file system hierarchy standard hel
>> http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
> The same sort of folks who were involved in developing this standard
> could help with an architecture rules specification format.
Did you discuss this idea with any software developers before?
> Up to now, I have not heard of any
> My idea is to put this in one config file at a standard location which
> can include site specific information. This could include information
> such as special compile/link flags required for a particular
> architecture format and expected subdirectory or library file naming.
> It would list ar
> It does not seem likely that anything as exotic as data structures and
> programming interfaces would be required. What is necessary is to get
> the right people interested.
Would you like to introduce more software developers and designers into the
topic for useful discussion of the details?
W
