On 11/10/2011, at 19:16, Andrea D'Amore wrote:
> On Tue, Oct 11, 2011 at 09:40, Daniel O'Connor <[email protected]> wrote:
>> Unfortunately when I try and run autoconf it insists I need v2.64 (not 2.68
>> as I have installed). I note macports has 2.63 available but I presume it
>> will not let me use that either :-/
>
> Check [1], your most updated 2.64 port seems to be in r57375.
Ahh thanks that worked.
I also had to modify libobjc's configure like so..
---
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_cross_arm-none-eabi-gcc/arm-none-eabi-gcc/work/gcc-4.6.1/libobjc/configure.ac.orig
2011-10-18 08:44:57.000000000 +1030
+++
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_cross_arm-none-eabi-gcc/arm-none-eabi-gcc/work/gcc-4.6.1/libobjc/configure.ac
2011-10-18 08:37:28.000000000 +1030
@@ -217,7 +217,9 @@
fi
# Check if we have thread-local storage
+if test "x${with_newlib}" != "xyes"; then
GCC_CHECK_TLS
+fi
AC_MSG_CHECKING([for exception model to use])
AC_LANG_PUSH(C)
And I could build it, although I only tested C, not C++ or ObjC, however now I
don't get the multitude of duplicated symbols against my sys call file if it
happens to be missing a sys call libc needs.. :)
If I generated diffs for the various configure files that needed modifying
(since it needs a special autoconf version) would it be possible to create a
no-newlib variant?
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
