All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15730] New: 2023.08-rc1 gettext-gnu 0.20.1 failed to compile
Date: Fri, 18 Aug 2023 10:50:34 +0000	[thread overview]
Message-ID: <bug-15730-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 15730
           Summary: 2023.08-rc1 gettext-gnu 0.20.1 failed to compile
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: trung.le@ruby-journal.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

### Info

**buildroot branch**: 2023.02-op-build
**OS**: Fedora 39 (rawhide) Linux shrimp-paste
6.5.0-0.rc6.20230816git4853c74bd7ab.45.fc39.ppc64le
**gcc**: 13.2.1 20230728 (Red Hat 13.2.1-1) glibc 2.38
**g++**: 13.2.1 20230728 (Red Hat 13.2.1-1) glibc 2.38


### Build output:

```
../gnulib-lib/stdio.h:758:1: error: declaration for parameter
‘_gl_cxxalias_dummy’ but no such parameter
  758 | _GL_CXXALIASWARN (fgets);
      | ^~~~~~~~~~~~~~~~
../gnulib-lib/stdio.h:756:1: error: declaration for parameter
‘_gl_cxxalias_dummy’ but no such parameter
  756 | _GL_CXXALIAS_SYS (fgets, char *, (char *s, int n, FILE *stream));
      | ^~~~~~~~~~~~~~~~
../gnulib-lib/stdio.h:743:1: error: declaration for parameter
‘_gl_cxxalias_dummy’ but no such parameter
  743 | _GL_CXXALIASWARN (fgetc);
      | ^~~~~~~~~~~~~~~~
../gnulib-lib/stdio.h:741:1: error: declaration for parameter
‘_gl_cxxalias_dummy’ but no such parameter
  741 | _GL_CXXALIAS_SYS (fgetc, int, (FILE *stream));
      | ^~~~~~~~~~~~~~~~
/usr/lib/gcc/ppc64le-redhat-linux/13/include/stddef.h:436:3: error: declaration
for parameter ‘max_align_t’ but no such parameter
  436 | } max_align_t;
      |   ^~~~~~~~~~~
/usr/lib/gcc/ppc64le-redhat-linux/13/include/stddef.h:329:24: error:
declaration for parameter ‘wchar_t’ but no such parameter
  329 | typedef __WCHAR_TYPE__ wchar_t;
      |                        ^~~~~~~
/usr/lib/gcc/ppc64le-redhat-linux/13/include/stddef.h:145:26: error:
declaration for parameter ‘ptrdiff_t’ but no such parameter
  145 | typedef __PTRDIFF_TYPE__ ptrdiff_t;
      |                          ^~~~~~~~~
regex.c:82: error: expected ‘{’ at end of input
make[4]: *** [Makefile:2099: regex.o] Error 1
make[4]: Leaving directory
'/home/tle/Work/op-build/output/build/host-gettext-gnu-0.20.1/gettext-tools/libgrep'
make[3]: *** [Makefile:2043: all] Error 2
make[3]: Leaving directory
'/home/tle/Work/op-build/output/build/host-gettext-gnu-0.20.1/gettext-tools/libgrep'
make[2]: *** [Makefile:2177: all-recursive] Error 1
make[2]: Leaving directory
'/home/tle/Work/op-build/output/build/host-gettext-gnu-0.20.1/gettext-tools'
make[1]: *** [Makefile:2045: all] Error 2
make[1]: Leaving directory
'/home/tle/Work/op-build/output/build/host-gettext-gnu-0.20.1/gettext-tools'
make: *** [package/pkg-generic.mk:293:
/home/tle/Work/op-build/output/build/host-gettext-gnu-0.20.1/.stamp_built]
Error 2
```

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-08-18 10:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 10:50 bugzilla [this message]
2023-08-18 10:51 ` [Buildroot] [Bug 15730] 2023.08-rc1 gettext-gnu 0.20.1 failed to compile bugzilla
2023-08-18 10:53 ` bugzilla
2023-08-18 11:07 ` bugzilla
2023-08-18 14:43 ` bugzilla
2023-08-19  6:20 ` bugzilla
2023-08-28 23:45 ` bugzilla
2023-08-29  5:00 ` bugzilla

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-15730-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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.