Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10996] bogus musl ARM toolchain
Date: Sun, 13 May 2018 20:05:59 +0000	[thread overview]
Message-ID: <bug-10996-163-ZnUpb6PrXo@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10996-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=10996

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yann.morin.1998 at free.fr

--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
(In reply to Thomas Petazzoni from comment #1)
> this happens because we don't pass -static.

But the autobuild failure that is referenced does use -static (with \ and
newlines added for readability):

   
home/peko/autobuild/instance-1/output/host/bin/arm-buildroot-linux-musleabihf-gcc
\
        -c -D_FILE_OFFSET_BITS=64 -Os \
        -static \
        -I. -DUNIX -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT
-DNO_MKTIME \
        -DNO_DIR -DHAVE_DIRENT_H -DHAVE_TERMIOS_H util.c

Regards,
Yann E. MORIN.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2018-05-13 20:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 12:41 [Buildroot] [Bug 10996] New: bogus musl ARM toolchain bugzilla at busybox.net
2018-05-11 15:53 ` [Buildroot] [Bug 10996] " bugzilla at busybox.net
2018-05-13 20:05 ` bugzilla at busybox.net [this message]
2018-05-13 20:16 ` bugzilla at busybox.net
2018-08-14 20:25 ` bugzilla at busybox.net
2018-08-14 22:31 ` bugzilla at busybox.net
2018-08-15 11:38 ` 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-10996-163-ZnUpb6PrXo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox