public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+cert@blue-labs.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Kay Sievers <lkml@vrfy.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.60 defconfig+CONFIG_MODVERSIONS=y -> syntax error
Date: Tue, 11 Feb 2003 19:26:38 -0500	[thread overview]
Message-ID: <3E4994BE.2040101@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0302101523130.3320-100000@chaos.physics.uiowa.edu>

$ sed --version
GNU sed version 4.0.5

(patch works for me too)

-d

Kai Germaschewski wrote:

>On Mon, 10 Feb 2003, Kay Sievers wrote:
>
>  
>
>>On Mon, Feb 10, 2003 at 02:49:36PM -0600, Kai Germaschewski wrote:
>>    
>>
>>>On Mon, 10 Feb 2003, Kay Sievers wrote:
>>>      
>>>
>>>>  ld:arch/i386/kernel/.tmp_time.ver:1: syntax error
>>>>        
>>>>
>>>Interesting. Thanks for testing CONFIG_MODVERSIONS. I cannot reproduce it
>>>here, unfortunately (not even with the same .config). What does
>>>arch/i386/kernel/.tmp_time.ver look like?
>>>      
>>>
>>pim:/usr/src/linux-2.5.60# cat arch/i386/kernel/.tmp_time.ver
>>__crc_i = 0x_lock ;     ac2d2492
>>    
>>
>
>Okay, that's not a problem with ld, but (most likely) sed.
>
>I hope the appended patch fixes it. For the record, what version of sed do 
>you have? (sed -V)
>
>--Kai
>
>
>===== scripts/Makefile.build 1.27 vs edited =====
>--- 1.27/scripts/Makefile.build	Sat Feb  8 14:30:33 2003
>+++ edited/scripts/Makefile.build	Mon Feb 10 15:25:44 2003
>@@ -94,7 +94,7 @@
> 	else								      \
> 		$(CPP) -D__GENKSYMS__ $(c_flags) $<			      \
> 		| $(GENKSYMS) -k $(VERSION).$(PATCHLEVEL).$(SUBLEVEL)	      \
>-		| sed -n 's/\#define __ver_\(\w*\)\W*\(\w*\)/__crc_\1 = 0x\2 ;/gp' \
>+		| sed -n 's/\#define __ver_\([^ 	]*\)[ 	]*\([^ 	]*\)/__crc_\1 = 0x\2 ;/gp' \
> 		> $(@D)/.tmp_$(@F:.o=.ver);				      \
> 									      \
> 		$(LD) $(LDFLAGS) -r -o $@ $(@D)/.tmp_$(@F) 		      \
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>  
>

-- 
I may have the information you need and I may choose only HTML.  It's up to you. Disclaimer: I am not responsible for any email that you send me nor am I bound to any obligation to deal with any received email in any given fashion.  If you send me spam or a virus, I may in whole or part send you 50,000 return copies of it. I may also publically announce any and all emails and post them to message boards, news sites, and even parody sites.  I may also mark them up, cut and paste, print, and staple them to telephone poles for the enjoyment of people without internet access.  This is not a confidential medium and your assumption that your email can or will be handled confidentially is akin to baring your backside, burying your head in the ground, and thinking nobody can see you butt nekkid and in plain view for miles away.  Don't be a cluebert, buy one from K-mart today.

When it absolutely, positively, has to be destroyed overnight.
                           AIR FORCE



      parent reply	other threads:[~2003-02-12  0:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 20:37 2.5.60 defconfig+CONFIG_MODVERSIONS=y -> syntax error Kay Sievers
2003-02-10 20:49 ` Kai Germaschewski
2003-02-10 20:57   ` Kay Sievers
2003-02-10 21:26     ` Kai Germaschewski
2003-02-10 21:44       ` Kay Sievers
2003-02-12  0:26       ` David Ford [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=3E4994BE.2040101@blue-labs.org \
    --to=david+cert@blue-labs.org \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@vrfy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox