All of 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: Sun, 15 Mar 2020 18:27:26 +0100	[thread overview]
Message-ID: <20200315182726.50af9ad7@gmx.net> (raw)
In-Reply-To: <CAA0OSwhHKHs+cNh4=0r7-U79wY-SrEL75=bXYjKX5nuvjSsY7g@mail.gmail.com>

Hello Mark,

On Sat, 14 Mar 2020 22:38:31 +0800, Mark Leo Sumadero <fryu771@gmail.com> wrote:

> Or i really don't know why i my python was compiled with pymalloc i'm just
> yung using the compiled python of buildroot.

Re-tested with buildroot 2019.02.1, seems for python-3.7.2 the compile
with pymalloc seems to be the default, no explicit '--with-pymalloc'
given, but config.log states:

	configure:11486: checking for --with-pymalloc
	configure:11506: result: yes

And from configure:

	if test -z "$with_pymalloc"
	then
	    with_pymalloc="yes"
	fi

So for your case add the 'm', in case you want to provide your
package patch for upstream buildroot then without 'm'....

Regards,
Peter

>
> On Sat, Mar 14, 2020 at 10:33 PM Mark Leo Sumadero <fryu771@gmail.com>
> wrote:
>
> > Hi Peter,
> >
> > You are correct no need to patch but if  i remove the 'm' on my
> > configuration i got the same error. How can i force it to use python3.7
> > only without 'm'?
> >
> > On Sat, Mar 14, 2020 at 9:54 PM Peter Seiderer <ps.report@gmx.net> wrote:
> >
> >> Hello Mark,
> >>
> >> On Sat, 14 Mar 2020 20:30:01 +0800, 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  config.log
> >> > --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?
> >>
> >> Tested against buildroot master, but should not make any difference,
> >> the important part is a full rebuild (configure/compile) of the
> >> package (best achieved by rm -rf
> >> build/mod_wsgi-61359e67448bdfc5fefb1692fd2a97f76394b20c)...
> >>
> >> No need to patch configure or configure.ac (there is already enough
> >> logic/magic that the
> >> given custom CPPFLAGS/LDFLAGS are used first)...
> >>
> >> According to [1] the 'm' in 'python3.7m' comes from a python
> >> configuration with --with-pymalloc,
> >> does not happen with stock buildroot configuration...
> >>
> >> Regards,
> >> Peter
> >>
> >> [1]
> >> https://stackoverflow.com/questions/41589655/whats-the-difference-between-python3-x-and-python3-xm
> >>
> >>
> >> >
> >> > 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
> >> > >
> >> > >
> >>
> >>

      parent reply	other threads:[~2020-03-15 17:27 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
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 [this message]

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=20200315182726.50af9ad7@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 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.