Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Help: error LONG_BIT definition appears wrong for platform
Date: Sat, 14 Mar 2020 11:21:10 +0100	[thread overview]
Message-ID: <20200314112110.2d8ce39a@gmx.net> (raw)
In-Reply-To: <20200313150443.682fdc5a@windsurf>

Hello Mark,

On Fri, 13 Mar 2020 15:04:43 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> Hello,
>
> On Fri, 13 Mar 2020 18:26:38 +0800
> Mark Leo Sumadero <fryu771@gmail.com> wrote:
>
> > /home/falcon/Documents/pisokonek-project/pisokonek/installer/buildroot-2019.02.1/output/host/bin/arm-buildroot-linux-uclibcgnueabihf-gcc
>
> This is the cross-compiler: good!
>
> > -prefer-pic -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> > -D_FILE_OFFSET_BITS=64 -Os  -DLINUX -D_REENTRANT -D_GNU_SOURCE
> >  -I/home/falcon/Documents/pisokonek-project/pisokonek/installer/buildroot-2019.02.1/output/host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/include
> >  -I/home/falcon/Documents/pisokonek-project/pisokonek/installer/buildroot-2019.02.1/output/host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/bin/../../usr/include/apr-1
> >
> > -I/home/falcon/Documents/pisokonek-project/pisokonek/installer/buildroot-2019.02.1/output/host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/bin/../../usr/include/apr-1
> > -I/home/falcon/Documents/pisokonek-project/pisokonek/installer/buildroot-2019.02.1/output/host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/bin/../../../../arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/include
> > -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os
> > -I/home/falcon/Documents/pisokonek-project/pisokonek/installer/buildroot-2019.02.1/output/host/include/python3.7m
>
> This is a path to header of host components: BAD!
>
> And this is where your problem is, this header path should *NOT* be
> there when you cross-compile.

The following worked for me (python3 case only):

MOD_WSGI_VERSION = 61359e67448bdfc5fefb1692fd2a97f76394b20c
MOD_WSGI_SITE = $(call github,GrahamDumpleton,mod_wsgi,$(MOD_WSGI_VERSION))
MOD_WSGI_LICENSE = Apache-2.0
MOD_WSGI_LICENSE_FILES = LICENSE
MOD_WSGI_DEPENDENCIES = apache

MOD_WSGI_CONF_OPTS = \
--with-apxs=$(STAGING_DIR)/usr/bin/apxs

ifeq ($(BR2_PACKAGE_PYTHON3),y)
MOD_WSGI_DEPENDENCIES += python3
MOD_WSGI_CONF_ENV += \
        CPPFLAGS="-I$(STAGING_DIR)/usr/include/python$(PYTHON3_VERSION_MAJOR)" \
        LDFLAGS="-L$(STAGING_DIR)/usr/lib"
endif

$(eval $(autotools-package))

Regards,
Peter

>
> Best regards,
>
> Thomas Petazzoni

  parent reply	other threads:[~2020-03-14 10:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 10:26 [Buildroot] Help: error LONG_BIT definition appears wrong for platform Mark Leo Sumadero
2020-03-13 14:04 ` Thomas Petazzoni
2020-03-14  3:17   ` Mark Leo Sumadero
2020-03-14 10:21   ` Peter Seiderer [this message]
2020-03-14 12:30     ` Mark Leo Sumadero
2020-03-14 13:37       ` Mark Leo Sumadero
2020-03-14 13:54       ` Peter Seiderer
2020-03-14 14:33         ` Mark Leo Sumadero
2020-03-14 14:38           ` Mark Leo Sumadero
2020-03-14 14:43             ` Mark Leo Sumadero
2020-03-14 17:10               ` Mark Leo Sumadero
2020-03-15 17:33                 ` Peter Seiderer
2020-03-15 17:27             ` Peter Seiderer

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

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

  git send-email \
    --in-reply-to=20200314112110.2d8ce39a@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox