unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Takesi Ayanokoji <ayanokoji.takesi@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 66507@debbugs.gnu.org
Subject: bug#66507: 30.0.50; Cannot build some modules without adding LOCAL_EXPORT_CFLAGS=-isystem ... on Android port.
Date: Fri, 13 Oct 2023 13:30:19 +0900	[thread overview]
Message-ID: <CAN7WbiaD0m93230NGT83yUoOtvL8PJ7YH1Wuom+zJJMMvx0U+A@mail.gmail.com> (raw)
In-Reply-To: <8734yfbabg.fsf@yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

Hello Po- san.

Unfortunately it doesn't seem to be mentioned in the java/INSTALL.

Thanks,

2023年10月13日(金) 午前10:06 Po Lu <luangruo@yahoo.com>:

> Takesi Ayanokoji <ayanokoji.takesi@gmail.com> writes:
>
> > Hello,
> >
> > Duaring building Emacs Android port, I encountered some modules that
> could not build without specifying system include header file by -isystem.
> >
> > These modules are
> >
> > libxml2:
> > add LOCAL_EXPORT_CFLAGS := -isystem $(LOCAL_PATH)/include
> >  to its Android.mk.
> >
> > lbjansson:
> > add LOCAL_EXPORT_CFLAGS := -isystem $(LOCAL_PATH)/src -I
> $(LOCAL_PATH)/android
> >  to its Android.mk
> >
> > core/libpackagelistparser:
> > add LOCAL_EXPORT_CFLAGS := -isystem $(LOCAL_PATH)/../include
> > (I installed it from core/libpackagelistparser)
> >
> > Thanks,
>
> IIRC all three of these changes are mentioned in java/INSTALL, but
> please correct me if I'm wrong.
>

[-- Attachment #2: Type: text/html, Size: 1482 bytes --]

  reply	other threads:[~2023-10-13  4:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 21:17 bug#66507: 30.0.50; Cannot build some modules without adding LOCAL_EXPORT_CFLAGS=-isystem ... on Android port Takesi Ayanokoji
2023-10-13  1:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-13  4:30   ` Takesi Ayanokoji [this message]
2023-10-13  5:01     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-13  6:40       ` Takesi Ayanokoji
2023-10-15 17:35         ` ayatakesi

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=CAN7WbiaD0m93230NGT83yUoOtvL8PJ7YH1Wuom+zJJMMvx0U+A@mail.gmail.com \
    --to=ayanokoji.takesi@gmail.com \
    --cc=66507@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    /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).