On 2009-05-19 09:51:08, Daniel Eischen wrote: > > Even so, you shouldn't need a cross-binutils, only a native > (amd64) binutils. Your port won't be a cross port, but a > native amd64 port. The native amd64 GNAT will need a native > binutils, not a cross binutils. The only thing you will have > to make is a minimal bootstrap (native amd64) compiler. > > Of course you can create a cross port if you want to facilitate > cross builds for ports that don't exist yet, but no one running > amd64 will want to make a cross build when they can make a > faster native build with less dependencies.
'lo, Sorry, I should have been a bit clearer there. I mean if in the very worst case, I can't get by with the system binutils, I can create a "native" set of recent binutils using the cross-binutils port: cd /usr/ports/devel/cross-binutils make TGTARCH=x86_64 TGTABI=freebsd7.2 install That way, the port can just depend on those and I won't have to create my own binutils port. Like I said, I'm hoping this won't happen. Current status is that I have a working native AMD64 GNAT using 2.19 binutils! $ gcc44 -v Using built-in specs. Target: x86_64-pc-freebsd7.2 Configured with: /usr/jails/i386/root/gcc-4.4.0/configure --build=x86_64-pc-freebsd7.2 --enable-languages=c,ada --disable-nls --with-system-zlib --with-libiconv-prefix=/usr/local --program-suffix=44 --bindir=/usr/local/bin/gcc44 --libdir=/usr/local/lib/gcc-4.4.0 --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/gcc44 Thread model: posix gcc version 4.4.0 (GCC) Needless to say, I'm pretty pleased. xw _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
