From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11071] New: Building postgresql package on Debian 9.4 x64 for armel target fails
Date: Wed, 06 Jun 2018 10:23:18 +0000 [thread overview]
Message-ID: <bug-11071-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11071
Bug ID: 11071
Summary: Building postgresql package on Debian 9.4 x64 for
armel target fails
Product: buildroot
Version: 2018.02.2
Hardware: PC
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: dde at innovaphone.com
CC: buildroot at uclibc.org
Target Milestone: ---
I'm currently trying to build buildroot with the postgresql package.
I'm building on Debian Stretch x86_64.
The target configuration in buildroot is for armel:
BR2_ARCH="arm"
BR2_ENDIAN="LITTLE"
BR2_GCC_TARGET_ABI="aapcs-linux"
BR2_GCC_TARGET_CPU="arm926ej-s"
BR2_GCC_TARGET_FLOAT_ABI="soft"
BR2_GCC_TARGET_MODE="arm"
BR2_BINFMT_SUPPORTS_SHARED=y
BR2_READELF_ARCH_NAME="ARM"
BR2_BINFMT_ELF=y
BR2_ARM_CPU_MAYBE_HAS_VFPV2=y
BR2_ARM_CPU_HAS_ARM=y
BR2_ARM_CPU_HAS_THUMB=y
The configure script of postgresql throws an error for libxml2 (I build with
--with-libxml as a custom option) and libz (this is standard, not changed by
me):
output/host/lib/libz.so: file not recognized: File format not recognized
output/host/lib/libxml2.so: file not recognized: File format not recognized
Seems as if the host libraries are wrong.
If I replace these two libraries with the libs found in output/target/usr/lib,
the build finishes without an error.
I do not have this issue on Debian Stretch x86 (32bit).
Greetings,
Daniel
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-06-06 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 10:23 bugzilla at busybox.net [this message]
2018-06-06 10:24 ` [Buildroot] [Bug 11071] Building postgresql package on Debian 9.4 x64 for armel target fails bugzilla at busybox.net
2018-06-06 11:29 ` bugzilla at busybox.net
2018-06-06 12:01 ` bugzilla at busybox.net
2018-06-06 12:01 ` bugzilla at busybox.net
2018-06-06 12:32 ` bugzilla at busybox.net
2018-06-06 13:26 ` bugzilla at busybox.net
2018-06-06 13:29 ` bugzilla at busybox.net
2018-06-06 18:52 ` bugzilla at busybox.net
2018-06-06 19:33 ` bugzilla at busybox.net
2018-06-06 19:43 ` bugzilla at busybox.net
2018-06-07 6:16 ` bugzilla at busybox.net
2018-06-07 21:02 ` bugzilla at busybox.net
2018-06-08 6:50 ` bugzilla at busybox.net
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=bug-11071-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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.