Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot compilation error "extra tokens at end of #ident directive"
Date: Tue Jul 25 13:40:18 2006	[thread overview]
Message-ID: <200607251639.25663.rob@landley.net> (raw)
In-Reply-To: <bf61e79a0607251106n321c6f1dgf2c3187cef783163@mail.gmail.com>

On Tuesday 25 July 2006 2:06 pm, Drew Cohan wrote:
> CC modutils/insmod.o
> /home/pkuser/buildroot/build_i686/busybox/modutils/insmod.c:352:10: extra
> tokens at end of #ident directive
> /home/pkuser/buildroot/build_i686/busybox/modutils/insmod.c:515:10: extra
> tokens at end of #ident directive

Huh, that would be my problem.  (Rummages.)  svn 15743 should fix this, which 
should be in tonight's snapshot.

> The two offending lines in the source code are identical:
> 
> #ident "$Id: insmod.c,v 1.126 2004/12/26 09:13:32 vapier Exp $"
> #ident "$Id: insmod.c,v 1.126 2004/12/26 09:13:32 vapier Exp $"

They have been yanked.

I take it this is a gcc 4.1 issue?  (I've tested rather a lot with gcc 4.0, 
but only got a gcc 4.1 environment set up while I was at OLS, and have been 
too busy to play with it since I got back...)  Alas, -Werror is a bit harsh 
but it does catch the warnings early...

Let me know if you hit anything else in busybox.

Rob
-- 
Never bet against the cheap plastic solution.

      reply	other threads:[~2006-07-25 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25 11:14 [Buildroot] buildroot compilation error "extra tokens at end of #ident directive" Drew Cohan
2006-07-25 13:40 ` Rob Landley [this message]

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=200607251639.25663.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox