From: Rob Landley <rob@landley.net>
To: buildroot@busybox.net
Subject: [Buildroot] Busybox & Gcc
Date: Mon, 31 Jul 2006 20:35:14 -0400 [thread overview]
Message-ID: <200607312035.14923.rob@landley.net> (raw)
In-Reply-To: <44C989A9.5070103@kulak.ca>
On Thursday 27 July 2006 11:51 pm, Kim Kulak wrote:
> I had a problem with that too. Here are some patches:
> -#ident "$Id: insmod.c,v 1.126 2004/12/26 09:13:32 vapier Exp $"
Already did that.
> -#ident "$Id: insmod.c,v 1.126 2004/12/26 09:13:32 vapier Exp $"
And that.
> struct module_info info;
> - char *module_names, *mn, *deps, *dn;
> + union
> + {
> + char *buf;
> + void *ptr;
> + } module_names, deps;
> + char *mn, *dn;
That's not going in.
> + void *bufptr = (void *)bb_common_bufsiz1;
Nor is that.
> - pkt->icmp_seq = htons(ntransmitted++);
> + pkt->icmp_seq = htons(ntransmitted); ntransmitted += 1;
What exactly is wrong with this one? (Argh, maybe it'll like SWAP_BE16
(ntransmitted++) better? Yes. Yes it does. Sigh. (Applied.)
> Busybox built clean after this for me with gcc 3.4.2.
And yet 4.0 isn't warning about this?
I need some time alone with select gcc developers and a whiffle bat...
So you're not seeing all the crazy "X could be used uninitialized
because 'if(a) X=0; else X=1' just isn't good enough!" messages?
> Kim
Rob
--
Never bet against the cheap plastic solution.
next prev parent reply other threads:[~2006-08-01 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 11:50 [Buildroot] Busybox & Gcc don
2006-07-27 21:52 ` Kim Kulak
2006-08-01 0:35 ` Rob Landley [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-27 12:46 Drew Cohan
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=200607312035.14923.rob@landley.net \
--to=rob@landley.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 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.