Fails, building Git on Intel, Tiger Mac Mini

[dgringo1@…]

Where to start; I do not like upgrading, as I generally do not need whatever they claim to offer :)

I restarted development, work after much time away generally. It seems I need support from resources such as Macports and or Tigerbrew... alas, I am having difficult getting a Git system working:

I need to build Git from (possibly only) Macports, but it seems "openssl" is blocking progress :( Specifically "curl" and "python27".

I came across "[MacPorts] #36752: trying to install git-core...nothing but errors" but, I too, am puzzled on how to progress. That is pretty the 'check for other tickets' :) I am seeking assistance / advice.

I am using an Intel Mac Mini, running Tiger (10.4.11). I had cleaned / uninstalled Macports sometime before, so I reinstalled, but ended up with these build failures again. I am using xcode 2.5, X11 and pretty much nothing else; truth is, I only now do shell programming, which requires very little.

Thanks.

[dgringo1@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

We need to see actual error messages, terminal transcripts, etc. in order to be able to begin to help you.

Are you having trouble building MacPorts itself, or have you successfully installed MacPorts and are having trouble building a port? MacPorts 2.2.0 itself should install on Tiger. MacPorts trunk currently ​will not but that may soon be fixed.

However, even if MacPorts can still be installed on Tiger today, Tiger is very old and MacPorts' Tiger support is on a rapid downward spiral. All Intel Macs support at least Snow Leopard and there's no good excuse not to upgrade. You'll have a much better MacPorts experience by upgrading your OS X.

[larryv (Lawrence Velázquez)]

Are you actually running MacPorts 2.1.3? The latest release is 2.2.0. Updating to that would be the first step.

[dgringo1@…]

Replying to ryandesign@…:

We need to see actual error messages, terminal transcripts, etc. in order to be able to begin to help you.

Are you having trouble building MacPorts itself, or have you successfully installed MacPorts and are having trouble building a port? MacPorts 2.2.0 itself should install on Tiger. MacPorts trunk currently ​will not but that may soon be fixed.

However, even if MacPorts can still be installed on Tiger today, Tiger is very old and MacPorts' Tiger support is on a rapid downward spiral. All Intel Macs support at least Snow Leopard and there's no good excuse not to upgrade. You'll have a much better MacPorts experience by upgrading your OS X.

Macports works fine, discounting some annoying port build failures. I shall try v2.2.0 first, then try sending detailed output. Bye-the-by, I do have a Snow-leopard laptop, but, again, I am not interested in it's 'new' features... still...

Oddly, this all came about for me by becoming interested in development, again, using rsync and doing a good 'TimeMachine' for myself. Having said the above, I have often been thwarted at getting and using Git.

David

PS. Usefulness and experiences are not the same things :)

[dgringo1@…]

Replying to larryv@…:

Are you actually running MacPorts 2.1.3? The latest release is 2.2.0. Updating to that would be the first step.

I just down loaded v2.2.0... well: MacPorts-2.2.0-10.5-Leopard.dmg by name, not soundng promising, but I shall try.

Sadly, it comes out with the only for Leopard :( Any clues or other suggests? (I had originally downladed the latest I could use -- I thought)

[larryv (Lawrence Velázquez)]

Replying to dgringo1@…:

I just down loaded v2.2.0... well: MacPorts-2.2.0-10.5-Leopard.dmg by name, not soundng promising, but I shall try.

Sadly, it comes out with the only for Leopard :( Any clues or other suggests? (I had originally downladed the latest I could use -- I thought)

You should be able to ​install from source.

[larryv (Lawrence Velázquez)]

Replying to dgringo1@…:

PS. Usefulness and experiences are not the same things :)

MacPorts is only as useful as the software it provides.

Our advice to update to Snow Leopard or newer is not about features. It’s about support. Remaining on Tiger will drastically reduce your options with regards to the software you can build and run, and your options will only shrink from here on out.

[dgringo1@…]

Replying to larryv@…:

Replying to dgringo1@…:

PS. Usefulness and experiences are not the same things :)

MacPorts is only as useful as the software it provides.

Our advice to update to Snow Leopard or newer is not about features. It’s about support. Remaining on Tiger will drastically reduce your options with regards to the software you can build and run, and your options will only shrink from here on out.

Great, 2.0.0 built and will hopefully allow myself to continue...

Having just said the above, it seems [ferreted away] I have a MacPorts-2.1.3-10.4-Tiger.dmg commented as "Tiger, last supporting?". Silly me, have I been here before?

Regardless, on I go...

(I shall seriously consider moving up to Snow Leopard...)

[ryandesign (Ryan Carsten Schmidt)]

Replying to dgringo1@…:

I just down loaded v2.2.0... well: MacPorts-2.2.0-10.5-Leopard.dmg by name, not soundng promising, but I shall try.

As the filename indicates, that version of the MacPorts installer is for Leopard only. If using pre-compiled MacPorts versions, always match the OS version exactly. That's why we make different versions available.

I simply never got around to making an installer for MacPorts 2.2.0 for Tiger. But installing any MacPorts pre-compiled package will automatically run selfupdate at the end. So, running the MacPorts 2.1.3 dmg installer for Tiger will result in you having MacPorts 2.2.0 (or whatever the latest version is) installed.

We still haven't heard any useful information in this bug report. If a port fails to build, attach the main.log so that we can begin to look into the problem.

[dgringo1@…]

Replying to ryandesign@…:

Replying to dgringo1@…:

I just down loaded v2.2.0... well: MacPorts-2.2.0-10.5-Leopard.dmg by name, not soundng promising, but I shall try.

As the filename indicates, that version of the MacPorts installer is for Leopard only. If using pre-compiled MacPorts versions, always match the OS version exactly. That's why we make different versions available.

I simply never got around to making an installer for MacPorts 2.2.0 for Tiger. But installing any MacPorts pre-compiled package will automatically run selfupdate at the end. So, running the MacPorts 2.1.3 dmg installer for Tiger will result in you having MacPorts 2.2.0 (or whatever the latest version is) installed.

We still haven't heard any useful information in this bug report. If a port fails to build, attach the main.log so that we can begin to look into the problem.

Argh, I realised the errors of my way -- getting confused by distractions here and all the version numbers, it would seem :( Whatever; I am definitely building 2.2.0 (again?)...

Sorry for my delay.

[dgringo1@…]

Replying to dgringo1@…:

Replying to ryandesign@…:

Replying to dgringo1@…:

I just down loaded v2.2.0... well: MacPorts-2.2.0-10.5-Leopard.dmg by name, not soundng promising, but I shall try.

As the filename indicates, that version of the MacPorts installer is for Leopard only. If using pre-compiled MacPorts versions, always match the OS version exactly. That's why we make different versions available.

I simply never got around to making an installer for MacPorts 2.2.0 for Tiger. But installing any MacPorts pre-compiled package will automatically run selfupdate at the end. So, running the MacPorts 2.1.3 dmg installer for Tiger will result in you having MacPorts 2.2.0 (or whatever the latest version is) installed.

We still haven't heard any useful information in this bug report. If a port fails to build, attach the main.log so that we can begin to look into the problem.

Argh, I realised the errors of my way -- getting confused by distractions here and all the version numbers, it would seem :( Whatever; I am definitely building 2.2.0 (again?)...

Sorry for my delay.

OK, I made sure I did the proper un-install. Installed 2.2.0 OK... Note: I have no configure script/application, for the first step, but proceeded with make and 'install' with no hitches! All seemed fine.

My attempt to (re)get the latest rsync:

mm:~ dgringo$ sudo port rsync
Password:
Warning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'.
Error: Unrecognized action "port rsync"
mm:~ dgringo$ man port
mm:~ dgringo$ sudo port install rsync
Password:
Warning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'.
Error: Unable to execute port: Could not open file: /Users/dgringo/src/MacPorts-2.2.0-archive/dports/net/rsync/Portfile
mm:~ dgringo$ sudo port selfupdate
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.2.0 installed,
MacPorts base version 2.2.0 downloaded.
--->  Updating the ports tree
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated
mm:~ dgringo$ sudo port install rsync
Warning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'.
Error: Unable to execute port: Could not open file: /Users/dgringo/src/MacPorts-2.2.0-archive/dports/net/rsync/Portfile

All sounds familiar as days back. Luckily I have already installed git seperately, but I do wish for an updated rsync. Where have I gone wrong -- all Macports was cleaned away nicely and reinstalled. Previously I was able to macports install rsync. As a minor point of interest, I have always failed to, say, port install 2Pong.

Hope I am now able to assist you assisting me.

David

[larryv (Lawrence Velázquez)]

Replying to dgringo1@…:

Note: I have no configure script/application, for the first step, but proceeded with make and 'install' with no hitches!

Wait, you installed MacPorts from source without running configure? There’s no way you have a working installation. You can’t just skip steps like that.

Please ​uninstall and follow the build instructions again. You must run the configure script that comes in the MacPorts tarball before running make and sudo make install. (You may have to adjust the uninstallation instructions, as I have no idea where your MacPorts could have installed itself.)

[dgringo1@…]

Replying to larryv@…:

Replying to dgringo1@…:

Note: I have no configure script/application, for the first step, but proceeded with make and 'install' with no hitches!

Wait, you installed MacPorts from source without running configure? There’s no way you have a working installation. You can’t just skip steps like that.

Please ​uninstall and follow the build instructions again. You must run the configure script that comes in the MacPorts tarball before running make and sudo make install. (You may have to adjust the uninstallation instructions, as I have no idea where your MacPorts could have installed itself.)

Thank goodness you said that. Following the installation again, there was no 'configure' program to run... although there had been for the previous efforts. I shall look into this effort more closely.

[larryv (Lawrence Velázquez)]

Replying to dgringo1@…:

Following the installation again, there was no 'configure' program to run... although there had been for the previous efforts.

So are you installing from source or from a package?

• If you are ​installing from source, you need to follow the instructions in the Guide exactly. That is, download the latest tarball, decompress it, and run configure/make/make install from inside the extracted directory. There most certainly is a configure script in there:

  % curl -s https://distfiles.macports.org/MacPorts/MacPorts-2.2.0.tar.bz2 | pax -j '*configure'
  MacPorts-2.2.0/configure
  %
  

• If you are ​installing from a package, you can't do the configure/make/make install dance, because there are no configure scripts or makefiles. You should be able to start using it right away.

Please describe exactly the steps you are taking to try and install MacPorts.

[dgringo1@…]

Replying to larryv@…:

Replying to dgringo1@…:

Note: I have no configure script/application, for the first step, but proceeded with make and 'install' with no hitches!

Wait, you installed MacPorts from source without running configure? There’s no way you have a working installation. You can’t just skip steps like that.

Please ​uninstall and follow the build instructions again. You must run the configure script that comes in the MacPorts tarball before running make and sudo make install. (You may have to adjust the uninstallation instructions, as I have no idea where your MacPorts could have installed itself.)

So here I am:

mm:~/src/MacPorts-2.2.0-archive dgringo$ ls
Makefile        doc             dports
base            doc-new         www
mm:~/src/MacPorts-2.2.0-archive dgringo$ ./configure
-bash: ./configure: No such file or directory

Where or what 'configure' should I be using (being that it is not working now, and I am not so silly as to rm odd things)?

[dgringo1@…]

Replying to larryv@…:

Replying to dgringo1@…:

Following the installation again, there was no 'configure' program to run... although there had been for the previous efforts.

So are you installing from source or from a package?

• If you are ​installing from source, you need to follow the instructions in the Guide exactly. That is, download the latest tarball, decompress it, and run configure/make/make install from inside the extracted directory. There most certainly is a configure script in there:

  % curl -s https://distfiles.macports.org/MacPorts/MacPorts-2.2.0.tar.bz2 | pax -j '*configure'
  MacPorts-2.2.0/configure
  %
  

• If you are ​installing from a package, you can't do the configure/make/make install dance, because there are no configure scripts or makefiles. You should be able to start using it right away.

Please describe exactly the steps you are taking to try and install MacPorts.

Wow, yourselves often surprise me being up. I am currently living in Chile, South America, so I erroneously think you've gone home or what-not -- discounting the 'delays' talking through your trac system. :-/ ( I am an Anglo/yank too)

I downloaded MacPorts-2.2.0-archive.tar.bz2 via Safari first, allowed the Mac to expand it and ran it from whatever directory it ended up being in (~/src/MacPorts-2.2.0-archive/). (By the way, thanks for working with me!) The time when configure worked, I just ran it and all was well, the second time it reported the confusion/missing application.

I am going to curl it, as you show... although that 'pax' command is new to me and checking it out via 'man', I could not find detail on the '-j' switch :(.

Same issue :( I ended up with a 2.0.0 version (with a configure program) Let is triple check this...

OK, I did the correct file BUT it does NOT have a configure program in it :( I notice that 'archive' ends up at the end of the subdirectory. Is that unexpected and related to why it is not working properly?

mm:~/Downloads dgringo$ cd /Volumes/MiscMac/basic\ settings/MacPorts-2.2.0-archive
mm:/Volumes/MiscMac/basic settings/MacPorts-2.2.0-archive dgringo$ ls
Makefile        doc             dports
base            doc-new         www
mm:/Volumes/MiscMac/basic settings/MacPorts-2.2.0-archive dgringo$ ll
total 8
-rw-r-----    1 dgringo  dgringo   445 Mar  1  2009 Makefile
drwxr-x--x   24 dgringo  dgringo   816 Sep  6 00:26 base/
drwxr-x--x    5 dgringo  dgringo   170 Sep  6 00:26 doc/
drwxr-x--x    7 dgringo  dgringo   238 Sep  6 00:26 doc-new/
drwxr-x--x   49 dgringo  dgringo  1666 Sep  6 00:25 dports/
drwxr-x--x   15 dgringo  dgringo   510 Jul 22 20:25 www/

Is there something very fundamentally wrong here, possibly at your end?

[larryv (Lawrence Velázquez)]

Replying to dgringo1@…:

Wow, yourselves often surprise me being up. I am currently living in Chile, South America, so I erroneously think you've gone home or what-not

I am at home :) …but not sleeping. It’s only 01:15 here in New York.

I downloaded MacPorts-2.2.0-archive.tar.bz2

Ah, that explains it. You need to download ​MacPorts-2.2.0.tar.bz2, not ​MacPorts-2.2.0-archive.tar.bz2. The archive is created as part of the MacPorts release process​ and is not intended to be used for source installations. (That doesn’t necessarily mean that using the archive has been causing your issues, but I certainly don’t know whether it works, and it’s best to make sure we’re on the same page.)

[dgringo1@…]

openssl log output

[dgringo1@…]

Replying to larryv@…:

Replying to dgringo1@…:

Wow, yourselves often surprise me being up. I am currently living in Chile, South America, so I erroneously think you've gone home or what-not

I am at home :) …but not sleeping. It’s only 01:15 here in New York.

I downloaded MacPorts-2.2.0-archive.tar.bz2

Ah, that explains it. You need to download ​MacPorts-2.2.0.tar.bz2, not ​MacPorts-2.2.0-archive.tar.bz2. The archive is created as part of the MacPorts release process​ and is not intended to be used for source installations. (That doesn’t necessarily mean that using the archive has been causing your issues, but I certainly don’t know whether it works, and it’s best to make sure we’re on the same page.)

Right, we are there... well, I got rsync back, having separately installed git, I ignored that for now and proceeded to install 2Pong (maybe a fun distraction). Alas, I am back on familiar ground, where I have been before -- after much building of required software, openssl fails. Here is the text:

...
--->  Fetching archive for openssl
--->  Attempting to fetch openssl-1.0.1e_1.darwin_8.i386.tbz2 from http://packages.macports.org/openssl
--->  Attempting to fetch openssl-1.0.1e_1.darwin_8.i386.tbz2 from http://lil.fr.packages.macports.org/openssl
--->  Attempting to fetch openssl-1.0.1e_1.darwin_8.i386.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/openssl
--->  Fetching distfiles for openssl
--->  Attempting to fetch openssl-1.0.1e.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/openssl
--->  Verifying checksums for openssl
--->  Extracting openssl
--->  Applying patches to openssl
--->  Configuring openssl
--->  Building openssl
Error: org.macports.build for port openssl returned: command execution failed
Error: Failed to install openssl
Please see the log file for port openssl for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_openssl/openssl/main.log
Error: The following dependencies were not installed: libsdl xorg-libXext xorg-libX11 xorg-libxcb python27 openssl python_select sqlite3 xorg-libpthread-stubs xorg-xcb-proto libxml2 xorg-util-macros xorg-xcmiscproto xorg-xextproto xorg-xf86bigfontproto xorg-xtrans xorg-libXrandr xorg-randrproto xrender xorg-renderproto libsdl_mixer flac libogg libmikmod libvorbis smpeg libsdl_net makeicns
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port 2Pong failed

So much was building that I was getting very happy... Oh yes, attached is the log for openssl.

[larryv (Lawrence Velázquez)]

You’ll want to look at #38561.

I’m closing this ticket, as it seems you have MacPorts itself working. Feel free to open new tickets to report any further issues you have building and installing ports.