prc-tools fails to build on Leopard

[clubjuggler@…]

Attempting to install prc-tools on leopard I get an error message. I believe the relevant error message is "Configuration i386-apple-darwin9.1.0 not supported" but here is the entire log:

--->  Fetching prc-tools
--->  Attempting to fetch prc-tools-2.3.tar.gz from http://downloads.sourceforge.net/prc-tools
--->  Attempting to fetch binutils-2.14.tar.gz from http://ftp.gnu.org/gnu/binutils
--->  Attempting to fetch gdb-5.3.tar.gz from http://ftp.gnu.org/gnu/gdb
--->  Attempting to fetch gcc-everything-2.95.3.tar.gz from http://ftp.gnu.org/gnu/gcc/gcc-2.95.3
--->  Attempting to fetch gcc-3.3.1.tar.gz from http://ftp.gnu.org/gnu/gcc/gcc-3.3.1
--->  Verifying checksum(s) for prc-tools
--->  Extracting prc-tools
Applying prc-tools patches...
Creating symbolic links for build...
Custom prc-tools pre-build steps complete.
--->  Configuring prc-tools
--->  Building prc-tools with target all
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_palm_prc-tools/work/prc-tools-2.3" && make all " returned error 2
Command output: checking for working vfork... (cached) yes
checking whether malloc must be declared... no
checking whether realloc must be declared... no
checking whether calloc must be declared... no
checking whether free must be declared... no
checking whether bcopy must be declared... no
checking whether bzero must be declared... no
checking whether bcmp must be declared... no
checking whether index must be declared... no
checking whether rindex must be declared... no
checking whether getenv must be declared... no
checking whether atol must be declared... no
checking whether sbrk must be declared... no
checking whether abort must be declared... no
checking whether atof must be declared... no
checking whether strerror must be declared... no
checking whether getcwd must be declared... no
checking whether getwd must be declared... no
checking whether strsignal must be declared... no
checking whether putc_unlocked must be declared... no
checking whether fputs_unlocked must be declared... yes
checking whether strstr must be declared... no
checking whether getrlimit must be declared... no
checking whether setrlimit must be declared... no
checking for sys_siglist declaration in signal.h or unistd.h... yes
checking if mkdir takes one argument... no
Configuration i386-apple-darwin9.1.0 not supported
Configure in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_palm_prc-tools/work/prc-tools-2.3/m68k-palmos/gcc295/gcc failed, exiting.
configure: error: ../.././gcc295/configure failed for gcc295
make: *** [m68k-palmos/config.status] Error 1

Error: Status 1 encountered during processing.

It looks like perhaps the older gcc doesn't support this OS/platform configuration.

[ryandesign (Ryan Carsten Schmidt)]

Assigning to port's maintainer.

[cssdev]

I do not yet have Leopard, so unfortunately this will need some outside help until I'm able to get my hands on it. :)

I really don't know even then if it will be possible to build gcc 2.95...

[clubjuggler@…]

I don't think Leopard has changed things enough that it wouldn't compile. I have a hope that it will just be a simple matter of duplicating the Tiger config for gcc. I've been meaning to try just that myself but with the holidays haven't had a chance yet. I'll see if I can do that within the next couple of days and if it works I'll post a patch.

[clubjuggler@…]

Ok, researching this more, it looks like gcc 2.95 is not supported under i386-apple-darwin*. The 2.95 compiler, though, is only used for the m68k-palmos compiler so conceivably we could not configure that and things should work. I don't know how many m68k palms are still out there, though.

The other options are to

1. Port gcc 2.95 to the i386-apple-darwin* platform. Might be able to use stuff from gcc 3. Might not. Don't know.

2. Port the m68k patches from gcc 2.95 to gcc 3.0. The prc-tools building page ( ​http://prc-tools.sourceforge.net/install/BUILDING.html ) says "In the future, the m68k patches will be ported to GCC 3.x, and the gcc295 directory will disappear." but it doesn't look like they ever were. I have no idea how hard it would be to do this.

For now, I'll look into building just the arm compiler and see how that works, but I don't think that's a very good solution since there's probably tons of older palms out there and it would be a shame to exclude them.

[cssdev]

Did you ever have any luck building just the arm compiler?

[clubjuggler@…]

No, sorry.

[(none)]

Milestone Port Bugs deleted

[cssdev]

I'm closing this ticket as wontfix ... the level of complication to fix this port would be too significant. I question whether this port sees any use anymore. Please reopen this ticket if you make any progress.