Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] DEVELOPERS: add Nicholas Sielicki as contact for galileo_defconfig
Date: Wed, 1 Jan 2020 22:16:57 +0100	[thread overview]
Message-ID: <20200101211657.GP3519@scaer> (raw)
In-Reply-To: <BN6PR11MB4145B63CE33025809CB99F8490210@BN6PR11MB4145.namprd11.prod.outlook.com>

Ray, All,

On 2020-01-01 21:08 +0000, Kinsella, Ray spake thusly:
> Yup - a make clean and rebuild sorted it out.
> 
> So Yann/Thomas - what do you need someone to sign up to here?
> Is a nightly build or a regular checkin or ... ?

As I explained earlier, there is a weekly build of all the defconfigs on
gitlab-ci [0], and when there is a failure, an automatic my is sent to
whoever is registered in the DEVELOPPERS file for that defconfig.

So, that means no mail until there is a failure, and this is at most
once a week, until the failure is fixed.

Regards,
Yann E. MORIN.

> Ray K
> 
> > -----Original Message-----
> > From: Yann E. MORIN <yann.morin.1998@free.fr>
> > Sent: Wednesday 1 January 2020 16:11
> > To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> > Cc: Kinsella, Ray <ray.kinsella@intel.com>; buildroot at buildroot.org;
> > Nicholas Sielicki <sielicki@yandex.com>
> > Subject: Re: [Buildroot] [PATCH] DEVELOPERS: add Nicholas Sielicki as
> > contact for galileo_defconfig
> > 
> > Ray, All,
> > 
> > (removing Padraig from the loop, their email is bouncing)
> > 
> > On 2020-01-01 16:34 +0100, Thomas Petazzoni spake thusly:
> > > On Wed, 1 Jan 2020 11:11:53 +0000
> > > "Kinsella, Ray" <ray.kinsella@intel.com> wrote:
> > > > My buildroot skills are bit rusty, but I have been mean to dust
> > them off.
> > > > So I am  willing to give it a go.
> > > >
> > > > BTW is there a specific failure that is causing a problem at the
> > moment.
> > > > I have grub failing on what look to be Unicode related issues.
> > 
> > Is this really 'grub' (as in grub legacy), or 'grub2'?
> > We do not have the legacy grub in Buildroot anymore.
> > 
> > > > /build/buildroot/output/host/lib/gcc/i586-buildroot-linux-
> > uclibc/8.3.0/../../../../i586-buildroot-linux-uclibc/bin/ld: grub-
> > core/lib/gnulib/libgnu.a(mbrtowc.o): in function `mbrtowc':
> > > > mbrtowc.c:(.text+0x169): undefined reference to `mbtowc'
> > > > /build/buildroot/output/host/lib/gcc/i586-buildroot-linux-
> > uclibc/8.3.0/../../../../i586-buildroot-linux-uclibc/bin/ld:
> > mbrtowc.c:(.text+0x17a): undefined reference to `mbtowc'
> > > > /build/buildroot/output/host/lib/gcc/i586-buildroot-linux-
> > uclibc/8.3.0/../../../../i586-buildroot-linux-uclibc/bin/ld: grub-
> > core/lib/gnulib/libgnu.a(vasnprintf.o): in function `vasnprintf':
> > > > vasnprintf.c:(.text+0x566): undefined reference to `wctomb'
> > 
> > I've just tried to build the galileo_defconfig, and it completed
> > successfully here.
> > 
> > > Could you try enabling BR2_TOOLCHAIN_BUILDROOT_WCHAR and do a full
> > > rebuild? Maybe we're missing this dependency in the grub package.
> > 
> > We already have a dependency on BR2_USE_WCHAR in grub2.
> > 
> > Regards,
> > Yann E. MORIN.
> > 
> > --
> > .-----------------.--------------------.------------------.------------
> > --------.
> > |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics'
> > | conspiracy: |
> > | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___
> > |
> > | +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There
> > is no  |
> > | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v
> > conspiracy.  |
> > '------------------------------^-------^------------------^------------
> > --------'

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2020-01-01 21:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-11 12:07 [Buildroot] [PATCH] DEVELOPERS: add Nicholas Sielicki as contact for galileo_defconfig Thomas Petazzoni
2019-12-31 15:20 ` Yann E. MORIN
     [not found]   ` <BN6PR11MB4145284497C2AF782D307B3590260@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-01  9:08     ` Yann E. MORIN
     [not found]   ` <MN2PR11MB4160005AC798211088F160C090210@MN2PR11MB4160.namprd11.prod.outlook.com>
2020-01-01 15:34     ` Thomas Petazzoni
2020-01-01 16:11       ` Yann E. MORIN
     [not found]         ` <BN6PR11MB4145B63CE33025809CB99F8490210@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-01 21:16           ` Yann E. MORIN [this message]
2020-01-02  8:14             ` Thomas Petazzoni
     [not found]               ` <BN6PR11MB4145CB3739932D59E074FC1C90200@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-03  8:24                 ` Thomas Petazzoni
     [not found]                   ` <BN6PR11MB4145527DD926BC273CA3F6B7903C0@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-06  9:42                     ` Thomas Petazzoni

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=20200101211657.GP3519@scaer \
    --to=yann.morin.1998@free.fr \
    --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