#40382: Fails, building Git on Intel, Tiger Mac Mini -------------------------+--------------------------------------- Reporter: dgringo1@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: git openssl curl python27 Port: Git | -------------------------+--------------------------------------- Comment (by 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 [https://lists.macosforge.org/pipermail/macports- dev/2013-September/024240.html 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. -- Ticket URL: <https://trac.macports.org/ticket/40382#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X

#40382: Fails, building Git on Intel, Tiger Mac Mini -------------------------+-------------------------------- Reporter: dgringo1@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: git-core | -------------------------+-------------------------------- Comment (by dgringo1@…): Replying to [comment:2 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 [https://lists.macosforge.org/pipermail/macports- dev/2013-September/024240.html 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 :) -- Ticket URL: <https://trac.macports.org/ticket/40382#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X

#40382: Fails, building Git on Intel, Tiger Mac Mini -------------------------+-------------------------------- Reporter: dgringo1@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: git-core | -------------------------+-------------------------------- Comment (by larryv@…): Replying to [comment:5 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 [http://guide.macports.org/#installing.macports.source install from source]. -- Ticket URL: <https://trac.macports.org/ticket/40382#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X

#40382: Fails, building Git on Intel, Tiger Mac Mini -------------------------+-------------------------------- Reporter: dgringo1@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: git-core | -------------------------+-------------------------------- Comment (by dgringo1@…): Replying to [comment:7 larryv@…]:

Replying to [comment:4 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...) -- Ticket URL: <https://trac.macports.org/ticket/40382#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X

#40382: Fails, building Git on Intel, Tiger Mac Mini -------------------------+-------------------------------- Reporter: dgringo1@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: git-core | -------------------------+-------------------------------- Comment (by dgringo1@…): Replying to [comment:9 ryandesign@…]:

Replying to [comment:5 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. -- Ticket URL: <https://trac.macports.org/ticket/40382#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X

#40382: Fails, building Git on Intel, Tiger Mac Mini -------------------------+-------------------------------- Reporter: dgringo1@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: git-core | -------------------------+-------------------------------- Comment (by larryv@…): Replying to [comment:11 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 [http://guide.macports.org/#installing.macports.uninstalling 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.) -- Ticket URL: <https://trac.macports.org/ticket/40382#comment:12> MacPorts <http://www.macports.org/> Ports system for OS X

#40382: Fails, building Git on Intel, Tiger Mac Mini -------------------------+-------------------------------- Reporter: dgringo1@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: git-core | -------------------------+-------------------------------- Comment (by larryv@…): Replying to [comment:13 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 [http://guide.macports.org/#installing.macports.source 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 [http://guide.macports.org/#installing.macports.binary 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. -- Ticket URL: <https://trac.macports.org/ticket/40382#comment:14> MacPorts <http://www.macports.org/> Ports system for OS X

#40382: Fails, building Git on Intel, Tiger Mac Mini -------------------------+-------------------------------- Reporter: dgringo1@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: git-core | -------------------------+-------------------------------- Comment (by dgringo1@…): Replying to [comment:14 larryv@…]:

Replying to [comment:13 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 [http://guide.macports.org/#installing.macports.source 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 [http://guide.macports.org/#installing.macports.binary 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? -- Ticket URL: <https://trac.macports.org/ticket/40382#comment:16> MacPorts <http://www.macports.org/> Ports system for OS X

#40382: Fails, building Git on Intel, Tiger Mac Mini -------------------------+-------------------------------- Reporter: dgringo1@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: git-core | -------------------------+-------------------------------- Comment (by dgringo1@…): Replying to [comment:17 larryv@…]:

Replying to [comment:16 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 [https://distfiles.macports.org/MacPorts/MacPorts-2.2.0.tar.bz2 MacPorts-2.2.0.tar.bz2], not [https://distfiles.macports.org/MacPorts/MacPorts-2.2.0-archive.tar.bz2 MacPorts-2.2.0-archive.tar.bz2]. The archive is created as part of the [[source:tags/release_2_2_0/base/portmgr/ReleaseProcess#L115|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. -- Ticket URL: <https://trac.macports.org/ticket/40382#comment:18> MacPorts <http://www.macports.org/> Ports system for OS X