Re: macOS status

"Chun Tian (binghe)" <[email protected]> Fri, 2 Feb 2024 09:45:36 +1100
Newsgroups	gmane.lisp.gcl.devel
Organization	The Australian National University
Message-ID	<[email protected]>
Greetings!

The command 'xcodebuild' can show the current active Xcode version, e.g.:

$ /usr/bin/xcodebuild -version
Xcode 15.2
Build version 15C500b

And I don't think gprof is available in the MacPorts-installed GCC.
Perhaps that's why Kirill used --disable-gprof when calling "./configure".

P.S. Very glad to hear the good news ("macports success")! I hope soon
the prebuilt GCL 2.7.0 binaries will be available to all MacPorts users
on various (recent) versions of macOS. (And I will use your debian
patches to build Axiom with external GCL.)

--Chun

On 02/02/24 04:18, Camm Maguire wrote:
> Greetings!
> 
> "Chun Tian (binghe)" <[email protected]> writes:
> 
>> @Camm, according to a 3rd-party Xcode release web site [1], the latest
>> Xcode supported on macOS Catalina is Xcode 12.4.  I think it won't hurt
>> your working macOS environment to install Xcode and its "command line
>> tools" if it prompts you to download and install on Xcode startup. (It's
>> the major and minor macOS version updates being dangerous.)  In short
>> words, to make the GCC installation from MacPorts actually work, the
>> command "xcode-select --install" must be executed once with the required
>> software installed, otherwise even "stdio.h" is not available to GCC.
>>
> 
> xcode-select --install
> 
> yields approximately
> 
> 'command line tools are already installed, use "Software Update" to
> install updates.'
> 
> How does one check the installed version?  What is "Software Update"?
> 
> -lgcrt1.o (gprof, -pg) is missing from the MacPorts gcc13 package -- is it anywhere
> else?
> 
> Take care,
> 
> 
> 
>> [1] https://xcodereleases.com
>>
>> Chun
>>
>> On 31/01/24 06:19, Kirill A. Korinsky wrote:
>>> Greetings,
>>>
>>> On Tue, 30 Jan 2024 17:28:11 +0100,
>>> Camm Maguire wrote:
>>>>
>>>> I have an old mac virtualbox which I never use except at the last point
>>>> in gcl releases.  Nonetheless I have fired it up, and run into the
>>>> problem that sed cannot put newlines into the replacement text.  You
>>>> guys are surely past this point.  I know next to nothing about macosx
>>>> versions and software installations -- perhaps you could point me to a
>>>> hopefully painless way to upgrade this virtualbox image to the latest
>>>> reasonable without destroying it.
>>>
>>> The simplest way is using image that you have without any upgrade.
>>>
>>> If you install MacPorts you may use my not published port to reproduce it.
>>>
>>> The simplest way after instalation (without switching MacPorts to git) is:
>>>
>>> 1. Replace content of
>>>    /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/lang/gcl/Portfile
>>>    into
>>>    https://raw.githubusercontent.com/catap/macports-ports/gcl-devel/lang/gcl/Portfile
>>>
>>> 2. Move to /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/port
>>>
>>> 3. Run portindex
>>>
>>> It adds gcl-devel port which you may build as `port build gcl-devel`.
>>>
>>> Portfile contains used gitcommit at line 78 and checksum at line 82.
>>>
>>> The simplest way to update it is:
>>> 1. Update git commit
>>> 2. Run `port bump gcl-devel`
>>>
>>> If you need access to a build folder you may find one as `port work gcl-devel`,
>>> and output log are available as `port logfile gcl-devel`.
>>>
>>> Keep in mind that after editing Portfile the work directory will be removed.
>>>
>>> --
>>> wbr, Kirill
>>>
>>
>
signature.asc (application/pgp-signature, 833 B)