All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Leo Sumadero <fryu771@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help: error LONG_BIT definition appears wrong for platform
Date: Sat, 14 Mar 2020 21:37:46 +0800	[thread overview]
Message-ID: <CAA0OSwhvuPwRFW9H7+tF9G-caWw2sbBeV2Zgi6Yk0YYJPcaXaQ@mail.gmail.com> (raw)
In-Reply-To: <CAA0OSwgZGQOKOv-11BxahH+Ht9Koxx=MEpfiuM-B-ZVVgQyLaw@mail.gmail.com>

Hi,

I made it worked by using this by adding "m"  after PYTHON3_VERSION_MAJOR:

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)m"
\
        LDFLAGS="-L$(STAGING_DIR)/usr/lib"
endif

$(eval $(autotools-package))

Then patching the configure and configure.ac of the package.
Question why is that python name is python3.7m not python3.7?

On Sat, Mar 14, 2020 at 8:30 PM Mark Leo Sumadero <fryu771@gmail.com> wrote:

> Hi Peter,
>
> Thanks for the reply. I just used your configuration but i got the same
> error
>
> /home/falcon/Documents/pisokonek-project/pisokonek/installer/buildroot-2019.02.1/output/host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/bin/../../usr/build-1/libtool
> --silent --mode=compile
> /home/falcon/Documents/pisokonek-project/pisokonek/installer/buildroot-2019.02.1/output/host/bin/arm-buildroot-linux-uclibcgnueabihf-gcc
> -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/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/include/python3.7
> -I/home/falcon/Documents/pisokonek-project/pisokonek/installer/buildroot-2019.02.1/output/host/include/python3.7m
> -DNDEBUG  -c -o src/server/mod_wsgi.lo src/server/mod_wsgi.c && touch
> src/server/mod_wsgi.slo
> In file included from
> /home/falcon/Documents/pisokonek-project/pisokonek/installer/buildroot-2019.02.1/output/host/include/python3.7m/Python.h:53:0,
>                  from src/server/wsgi_python.h:24,
>                  from src/server/mod_wsgi.c:22:
> /home/falcon/Documents/pisokonek-project/pisokonek/installer/buildroot-2019.02.1/output/host/include/python3.7m/pyport.h:699:2:
> error: #error "LONG_BIT definition appears wrong for platform (bad
> gcc/glibc config?)."
>  #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc
> config?)."
>
> Did i miss something? I am currently using Buildroot-2019.02.01 and
> python3.7, what version did you use?
> Are we the same of header path?
>
> Thanks,
>
> Mark Leo
>
> On Sat, Mar 14, 2020 at 6:21 PM Peter Seiderer <ps.report@gmx.net> wrote:
>
>> Hello Mark,
>>
>> On Fri, 13 Mar 2020 15:04:43 +0100, Thomas Petazzoni <
>> thomas.petazzoni at 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
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200314/6d9680e2/attachment.html>

  reply	other threads:[~2020-03-14 13:37 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
2020-03-14 12:30     ` Mark Leo Sumadero
2020-03-14 13:37       ` Mark Leo Sumadero [this message]
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=CAA0OSwhvuPwRFW9H7+tF9G-caWw2sbBeV2Zgi6Yk0YYJPcaXaQ@mail.gmail.com \
    --to=fryu771@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.