unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Werner LEMBERG <wl@gnu.org>
To: mattiase@acm.org
Cc: dports@macports.org, eggert@cs.ucla.edu, fgunbin@fastmail.fm,
	emacs-devel@gnu.org
Subject: Re: Emacs 28.1 doesn't compile on Mac OS 10.7.5
Date: Sat, 16 Apr 2022 07:35:56 +0000 (UTC)	[thread overview]
Message-ID: <20220416.093556.1218054977410547553.wl@gnu.org> (raw)
In-Reply-To: <20220416.071837.1688848337648253277.wl@gnu.org>


>> Looks like directory configuration issues that I know nothing about.

I've now submitted a first PR for MacPorts

  https://github.com/macports/macports-ports/pull/14594

so that it can eventually be used by admins for triggering builds on
older macOS versions (this isn't done automatically AFAIK).

Lo and behold, it also reports problems with current git on recent
macOS versions (10.15 and 11.0) :-)

```
sysdep.c:4147:41: error: implicit declaration of function
  'timeval_to_timespec' is invalid in C99
  [-Werror,-Wimplicit-function-declaration]
struct timespec t = timespec_add (timeval_to_timespec (rusage->ru_utime),
```

This is from the logfiles for subports 'emacs-devel' and
'emacs-app-devel' based on emacs commit 8259e368001a6e3; the above PR
also contains links to the full logs if needed.


    Werner



  reply	other threads:[~2022-04-16  7:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 11:55 Emacs 28.1 doesn't compile on Mac OS 10.7.5 Werner LEMBERG
2022-04-15 13:16 ` Mattias Engdegård
2022-04-15 13:48   ` Mattias Engdegård
2022-04-15 15:23     ` Werner LEMBERG
2022-04-15 15:54       ` Eli Zaretskii
2022-04-15 16:48         ` Werner LEMBERG
2022-04-15 16:22       ` Mattias Engdegård
2022-04-15 16:41         ` Mattias Engdegård
2022-04-15 16:51         ` Werner LEMBERG
2022-04-15 17:13           ` Mattias Engdegård
2022-04-15 17:40             ` Werner LEMBERG
2022-04-15 18:34               ` Mattias Engdegård
2022-04-15 19:47                 ` Eli Zaretskii
2022-04-16  5:18                 ` Werner LEMBERG
2022-04-16  7:35                   ` Werner LEMBERG [this message]
2022-04-16 10:30                     ` Mattias Engdegård
2022-04-16 15:25                       ` Werner LEMBERG
2022-04-17  2:21         ` Paul Eggert
2022-04-17  3:28           ` Jeffrey Walton
2022-04-17  7:54             ` Paul Eggert
2022-04-17 11:09               ` Werner LEMBERG
2022-04-17 14:33               ` Ryan Schmidt
2022-04-17 14:51                 ` Jeffrey Walton
2022-04-17  9:13           ` Mattias Engdegård
2022-04-17  9:32             ` Po Lu
2022-04-17  9:38               ` Mattias Engdegård
2022-04-17 11:33             ` Eli Zaretskii
2022-04-17 12:27               ` Mattias Engdegård
2022-04-17 17:54             ` Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220416.093556.1218054977410547553.wl@gnu.org \
    --to=wl@gnu.org \
    --cc=dports@macports.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=fgunbin@fastmail.fm \
    --cc=mattiase@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).