(sorry for breaking the Cc: earlier, I used the opensolaris-arc forum, which apparently is missing some functionality)
On Feb 12, 2009 5:23pm, George Vasick <George.Vasick at sun.com> wrote: > No, they are all part of the same binutils package. Gnu tools can be configured to support cross development in addition to native development. The machine/architecture dependent paths are provided to allow tools for multiple target systems to coexist on a single host system. Note that Debian provides a Z80 cross-linker which is doing fine without the /usr/$target directory. But that does not matter. > usr/gnu/i386-pc-solaris2.11 Project private I guess. > usr/gnu/i386-pc-solaris2.11/bin As long as this path is private, it does not do any harm, so ok. > usr/gnu/i386-pc-solaris2.11/lib/ldscripts Yes, I think I prefer this. If gnu programs want /$target, /libexec etc directories, it makes sense to let them do it in /usr/gnu (and be more strict for /usr). > usr/gnu/include/ansidecl.h > usr/gnu/include/bfd.h > usr/gnu/include/bfdlink.h > usr/gnu/include/dis-asm.h > usr/gnu/include/symcat.h Hmm, I just noticed this, does it make sense to ship the headers when you are not shipping the corresponding libraries? ansidecl.h is just macros, but some others declare functions (they might still have some use without the libs though, I don't know). In any case, I think /usr/include was a better location for them. By the way, I guess with this change you'll end up with /usr/gnu/(share/)man/man1/ld.1, so you'll need links from /usr/share/man/man1/gld.1. Good luck with this gcc update project, which I am very happy to see.
