public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Fernando Ortiz (e2k)" <eratos2000@gmail.com>
To: Bryan Hundven <bryanhundven@gmail.com>
Cc: Delta Tatham <delta.tatham@me.com>,
	 crossgcc maillist <crossgcc@sourceware.org>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [PATCH 1/2] Prevent zconf.gperf from throwing an error on OSX
Date: Wed, 06 Aug 2014 16:52:00 -0000	[thread overview]
Message-ID: <53E25D4C.6080404@gmail.com> (raw)
In-Reply-To: <CAJ+oik1aR5Lq8v=A+GxQZyPz=HYbudy1b83md9Qvtci7jThGNQ@mail.gmail.com>

Bryan, all,

On 08/05/2014 02:38 AM, Bryan Hundven wrote:
> Fernando, all,
>
> On Mon, Aug 4, 2014 at 10:42 PM, Fernando Ortiz (e2k)
> <eratos2000@gmail.com> wrote:
>> I can confirm this work as is using Mac OS X, ubuntu and debian.
> Was it a failing issue on ubuntu or debian? Did it add a warning? I'm
> not around my computer, or I'd just test it myself.

The computer I'm using was built recently so not all the packages were 
there when I first tested, I know it fails the first time, but cannot 
recreate the problem now tested again on trusty and works without this 
patch.  I had installed many packages since I first tested that it may 
have fixed the original problem.

However it still fails on Mac OS X with: 
https://gist.github.com/nandub/fd91fcfcc751149fe7ba
>
>> On Aug 5, 2014, at 12:20 AM, Bryan Hundven <bryanhundven@gmail.com> wrote:
>>
>>> Daniel, List,
>>>
>>> On Sun, Aug 3, 2014 at 8:06 AM, Delta Tatham <delta.tatham@me.com> wrote:
>>>> From: Daniel Zauner <delta.tatham@me.com>
>>>>
>>>> Grabbed this one from the homebrew formula. Might need further adaption for non-OSX
>>>> Signed-off-by: Daniel Zauner aka Delta Tatham <delta.tatham@me.com>
>>>> ---
>>>> kconfig/zconf.gperf | 4 ++++
>>>> 1 file changed, 4 insertions(+)
>>>>
>>>> diff --git a/kconfig/zconf.gperf b/kconfig/zconf.gperf
>>>> index c9e690e..21e79e4 100644
>>>> --- a/kconfig/zconf.gperf
>>>> +++ b/kconfig/zconf.gperf
>>>> @@ -7,6 +7,10 @@
>>>> %pic
>>>> %struct-type
>>> Can we ifdef on Darwin/BSD here? If it works on other platforms, then
>>> only the ones mentioned need stddef.h included here.
>>>
>>>> +%{
>>>> +#include <stddef.h>
>>>> +%}
>>>> +
>>>> struct kconf_id;
>>>>
>>>> static struct kconf_id *kconf_id_lookup(register const char *str, register unsigned int len);
>>>> --
>>>> 1.9.3 (Apple Git-50)
>>>>
>>>>
>>>> --
>>>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>>>
>>> Otherwise: +1
>>>
>>> -Bryan
>>>
>>> --
>>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>>
> Thanks,
>
> -Bryan


--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2014-08-06 16:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03 15:07 [PATCH 0/2] OSX: Patches to make ct-ng compile & build on OSX 10.10 Delta Tatham
2014-08-03 15:07 ` [PATCH 2/2] Patches to enable compilation " Delta Tatham
2014-08-03 15:07 ` [PATCH 1/2] Prevent zconf.gperf from throwing an error on OSX Delta Tatham
2014-08-05  5:20   ` Bryan Hundven
2014-08-05  5:42     ` Fernando Ortiz (e2k)
2014-08-05  7:38       ` Bryan Hundven
2014-08-06 16:52         ` Fernando Ortiz (e2k) [this message]
2014-10-16 16:27 Jason T. Masker
2014-10-16 16:30 ` Bryan Hundven
2014-10-16 20:54   ` Gmail
2014-10-16 16:32 ` Bryan Hundven
2014-10-16 16:45   ` Jason T. Masker

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=53E25D4C.6080404@gmail.com \
    --to=eratos2000@gmail.com \
    --cc=bryanhundven@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=delta.tatham@me.com \
    --cc=yann.morin.1998@free.fr \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).