Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Problems with the package wget version 1.19.5
Date: Sat, 29 Sep 2018 19:49:28 +0200	[thread overview]
Message-ID: <20180929194928.0870faf5@gmx.net> (raw)
In-Reply-To: <CALtfCQayoGL14UFvd6g+X4A0bxJwYn9s5oN-hScxBrtYgbvNvw@mail.gmail.com>

Hello Oscar,

On Wed, 26 Sep 2018 12:53:52 +0200, Oscar Gomez Fuente <oscargomezf@gmail.com> wrote:

> Hi Peter,
> 
> Thank you in advanced for your help.
> 
> > Please post your .config/defconfig file (with the bare raspberrypi3_defconfig
> > wget is disabled because of the BR2_USE_WCHAR dependency (and BR2_PACKAGE_BUSYBOX_SHOW_OTHERS))?  
> 
> BR2_arm=y
> BR2_cortex_a53=y
> BR2_ARM_FPU_NEON_VFPV4=y
> BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_14=y
> BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_TARGET_GENERIC_HOSTNAME="tstpi"
> BR2_TARGET_GENERIC_ISSUE="Welcome to Buildroot 2018.02.5 by TST"
> BR2_TARGET_GENERIC_PASSWD_SHA512=y
> BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
> BR2_TARGET_GENERIC_ROOT_PASSWD="tstpi"
> BR2_SYSTEM_BIN_SH_BASH=y
> BR2_TARGET_GENERIC_GETTY_PORT="ttyAMA0"
> BR2_TARGET_GENERIC_GETTY_BAUDRATE_115200=y
> BR2_SYSTEM_DHCP="eth0"
> # BR2_ENABLE_LOCALE_PURGE is not set
> BR2_ROOTFS_POST_BUILD_SCRIPT="$(TOPDIR)/board/tst/tstpi/post-build-tstpi-3b.sh"
> BR2_ROOTFS_POST_IMAGE_SCRIPT="$(TOPDIR)/board/tst/tstpi/post-image.sh"
> BR2_ROOTFS_POST_SCRIPT_ARGS="tstpi-3p-pc --serial --ext-mon-wifi --bt"
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_GIT=y
> BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git"
> BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="865ddc1393f558198e7e7ce70928ff2e49c4f7f6"
> BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="$(TOPDIR)/board/tst/tstpi/linux-config/linux-tstpi-3b-pc.config"
> BR2_LINUX_KERNEL_DTS_SUPPORT=y
> BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2710-rpi-3-b bcm2710-rpi-3-b-plus
> bcm2710-rpi-cm3"
> BR2_PACKAGE_LINUX_TOOLS_CPUPOWER=y
> BR2_PACKAGE_LINUX_TOOLS_GPIO=y
> BR2_PACKAGE_LINUX_TOOLS_TMON=y
> BR2_PACKAGE_BUSYBOX_CONFIG="$(TOPDIR)/board/tst/tstpi/busybox-config/busybox-tstpi-pc.config"
> BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
> BR2_PACKAGE_BUSYBOX_WATCHDOG=y
> BR2_PACKAGE_CHECK=y
> BR2_PACKAGE_RPI_BT_FIRMWARE=y
> BR2_PACKAGE_RPI_FIRMWARE=y
> BR2_PACKAGE_RPI_WIFI_FIRMWARE=y
> BR2_PACKAGE_I2C_TOOLS=y
> BR2_PACKAGE_SPI_TOOLS=y
> BR2_PACKAGE_PYTHON3=y
> BR2_PACKAGE_PYTHON3_CURSES=y
> BR2_PACKAGE_PYTHON_SMBUS_CFFI=y
> BR2_PACKAGE_LIBSNDFILE=y
> BR2_PACKAGE_LIBUSB=y
> BR2_PACKAGE_WIRINGPI=y
> BR2_PACKAGE_BC=y
> BR2_PACKAGE_AIRCRACK_NG=y
> BR2_PACKAGE_BLUEZ_TOOLS=y
> BR2_PACKAGE_BLUEZ5_UTILS=y
> BR2_PACKAGE_BLUEZ5_UTILS_OBEX=y
> BR2_PACKAGE_BLUEZ5_UTILS_CLIENT=y
> BR2_PACKAGE_BLUEZ5_UTILS_EXPERIMENTAL=y
> BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_HEALTH=y
> BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_MIDI=y
> BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_NFC=y
> BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_SAP=y
> BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_SIXAXIS=y
> BR2_PACKAGE_BLUEZ5_UTILS_TEST=y
> BR2_PACKAGE_BLUEZ5_TOOLS_BDADDR=y
> BR2_PACKAGE_DROPBEAR=y
> BR2_PACKAGE_ETHTOOL=y
> BR2_PACKAGE_IW=y
> BR2_PACKAGE_NETCAT=y
> BR2_PACKAGE_NTP=y
> BR2_PACKAGE_NTP_NTPDATE=y
> BR2_PACKAGE_PPPD=y
> BR2_PACKAGE_WGET=y
> BR2_PACKAGE_WPA_SUPPLICANT=y
> BR2_PACKAGE_NANO=y
> BR2_TARGET_ROOTFS_EXT2=y
> BR2_TARGET_ROOTFS_EXT2_4=y
> BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
> BR2_PACKAGE_HOST_DOSFSTOOLS=y
> BR2_PACKAGE_HOST_GENIMAGE=y
> BR2_PACKAGE_HOST_MTOOLS=y
> 
> > Did you try a complete rebuild after changing your configuration (see [1])?  
> YES

I can confirm the Segmentation fault on RPi3 with your buildroot configuration:

	$ ./host/usr/bin/arm-buildroot-linux-uclibcgnueabihf-gdb /mnt/root/wget /mnt/root/core
Core was generated by `wget http://www.buildroot.org'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  rpl_gmtime (timep=0x7ebb390c, 
    timep at entry=<error reading variable: DWARF-2 expression error: Loop detected (257).>)
    at localtime-buffer.c:49
49	{
(gdb) where
#0  rpl_gmtime (timep=0x7ebb390c, 
    timep at entry=<error reading variable: DWARF-2 expression error: Loop detected (257).>)
    at localtime-buffer.c:49
#1  0x000487a8 in rpl_gmtime (
    timep=<error reading variable: DWARF-2 expression error: Loop detected (257).>)
    at localtime-buffer.c:50
#2  0x000487a8 in rpl_gmtime (
    timep=<error reading variable: DWARF-2 expression error: Loop detected (257).>)
    at localtime-buffer.c:50
#3  0x000487a8 in rpl_gmtime (
    timep=<error reading variable: DWARF-2 expression error: Loop detected (257).>)
    at localtime-buffer.c:50

...and so on (endless recursion)..., maybe by calling rpl_gmtime with
gmtime defined as rpl_gmtime:

build/wget-1.19.5/lib/localtime-buffer.c:

 47 struct tm *
 48 rpl_gmtime (time_t const *timep)
 49 {
 50   struct tm *tm = gmtime (timep);
 51 
 52   if (localtime_buffer_addr == &tm_zero_buffer)
 53     localtime_buffer_addr = tm;
 54 
 55   return tm;
 56 }

build/wget-1.19.5/lib/time.h:

675 # if 0 || 1
676 #  if 1
677 #   if !(defined __cplusplus && defined GNULIB_NAMESPACE)
678 #    undef gmtime
679 #    define gmtime rpl_gmtime
680 #   endif
681 _GL_FUNCDECL_RPL (gmtime, struct tm *, (time_t const *__timer)
682                                        _GL_ARG_NONNULL ((1)));
683 _GL_CXXALIAS_RPL (gmtime, struct tm *, (time_t const *__timer));
684 #  else
685 _GL_CXXALIAS_SYS (gmtime, struct tm *, (time_t const *__timer));
686 #  endif
687 _GL_CXXALIASWARN (gmtime);
688 # endif

Try with musl or glibc until a proper solution is found?

Regards,
Peter


> Best regards.
> 
> Oscar Gomez Fuente
> TST Sistemas
> www.tst-sistemas.es
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2018-09-29 17:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  8:09 [Buildroot] Problems with the package wget version 1.19.5 Oscar Gomez Fuente
2018-09-19 19:14 ` Peter Seiderer
2018-09-26 10:53   ` Oscar Gomez Fuente
2018-09-29 17:49     ` Peter Seiderer [this message]
2018-09-29 18:54       ` Oscar Gomez Fuente

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=20180929194928.0870faf5@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