[coreboot] Building AMD Persimmon in MinGW

[Zheng Bao]

http://sourceforge.net/projects/gnuwin32/files/regex/2.7/

Here is the link for regex library.

There are lib and dll in regex-2.7-bin.zip.

Kconfig is a seperated tool. If we want to leverage the regex.c in Kconfig, we need to submit a patch.

Zheng

Date: Tue, 7 May 2013 15:30:02 +0200
From: wvervoorn at eltan.com
To: coreboot at coreboot.org
Subject: Re: [coreboot] Building AMD Persimmon in MinGW

Hello, I noticed that KConfig includes the regex.c and .h files to solve this issue. I did the same for nvramtool.exe and now it seems to work. (At least I can build it and run it without errors).  Regards,
Wim From: coreboot-bounces at coreboot.org [mailto:coreboot-bounces at coreboot.org] On Behalf Of Wim Vervoorn
Sent: dinsdag 7 mei 2013 13:09
To: Zheng Bao; coreboot at coreboot.org
Subject: Re: [coreboot] Building AMD Persimmon in MinGW Hello Zheng,
Any suggestions where I can find this? I haven’t been able to locate it until now. Wim From: Zheng Bao [mailto:fishbaoz at hotmail.com] 
Sent: dinsdag 7 mei 2013 11:12
To: Wim Vervoorn; coreboot at coreboot.org
Subject: Re: [coreboot] Building AMD Persimmon in MinGW You need to find a regex2.dll. Just putting it in folder coreboot is OK.

Zheng> Date: Tue, 7 May 2013 09:07:18 +0200
> From: wvervoorn at eltan.com
> To: coreboot at coreboot.org
> Subject: Re: [coreboot] Building AMD Persimmon in MinGW
> 
> Hello,
> 
> This is the fragment where it fails:
> 
> It seems that the call to regcomp is causing the issue.
> 
> I don't think this has anything to do with direct access to the
> hardware. It seems to be some kind of pointer issue, the call seems to
> access data it can't reach.
> 
> 
> /***********************************************************************
> *****
> * compile_reg_expr
> *
> * Compile a regular expression.
> 
> ************************************************************************
> ****/
> void compile_reg_expr(int cflags, const char *expr, regex_t *reg)
> {
> static const size_t ERROR_BUF_SIZE = 256;
> char error_msg[ERROR_BUF_SIZE];
> int result;
> 
> -->>>> if ((result = regcomp(reg, expr, cflags)) != 0) { <<---------
> 
> regerror(result, reg, error_msg, ERROR_BUF_SIZE);
> fprintf(stderr, "%s: %s\n", prog_name, error_msg);
> exit(1);
> }
> 
> printf( "compile_reg_expr 3\n");
> 
> }
> 
> 
> Regards,
> 
> Wim
> 
> -----Original Message-----
> From: coreboot-bounces at coreboot.org
> [mailto:coreboot-bounces at coreboot.org] On Behalf Of Patrick Georgi
> Sent: dinsdag 7 mei 2013 8:51
> To: coreboot at coreboot.org
> Subject: Re: [coreboot] Building AMD Persimmon in MinGW
> 
> Am 2013-05-07 01:56, schrieb Peter Stuge:
> > Sounds right. Would be great to find out more details about why and 
> > how nvramtool is being used during the build!
> During the handling of cmos.layout and cmos.settings (if present and
> used).
> 
> We don't need any special hardware access for that and should not use
> any such code while building coreboot.
> One place to look at is the win32mmap implementation, which _is_ used.
> 
> 
> Patrick
> 
> -- 
> coreboot mailing list: coreboot at coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot
> 
> 
> 
> -- 
> coreboot mailing list: coreboot at coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot
-- 
coreboot mailing list: coreboot at coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20130508/28e86cf9/attachment-0001.html>