[flashrom] I have problem making latest flashrom

[guy lacroix]

idwer provided
http://qa.coreboot.org/snapshots/flashrom-0.9.1-r792.tar.bz2
I unpacked it to /home/guy/flashrom-0.9.1-r792 and sudo make ./flashrom
was successful.  It took me a while before I realised I kept
executing /usr/sbin/flashrom (r706) even when current dir
is /home/guy/flashrom-0.9.1-r792 until I included the path in the
command.
guy at asus-p4b:~/flashrom-0.9.1-r792$
sudo /home/guy/flashrom-0.9.1-r792/flashrom -r 1008.bin
flashrom v0.9.1-r792
No coreboot table found.
Found chipset "Intel ICH2", enabling flash write... OK.
This chipset supports the following protocols: Non-SPI.
Disabling flash write protection for board "ASUS P4B266"... 
Intel ICH LPC Bridge: Raising GPIO22.
OK.
Calibrating delay loop... OK.
Found chip "SST SST49LF002A/B" (256 KB, FWH) at physical address
0xfffc0000.
Reading flash... done.
guy at asus-p4b:~/flashrom-0.9.1-r792$
sudo /home/guy/flashrom-0.9.1-r792/flashrom -w 1012.bin
flashrom v0.9.1-r792
No coreboot table found.
Found chipset "Intel ICH2", enabling flash write... OK.
This chipset supports the following protocols: Non-SPI.
Disabling flash write protection for board "ASUS P4B266"... 
Intel ICH LPC Bridge: Raising GPIO22.
OK.
Calibrating delay loop... OK.
Found chip "SST SST49LF002A/B" (256 KB, FWH) at physical address
0xfffc0000.
Flash image seems to be a legacy BIOS. Disabling checks.
Writing flash chip... Programming page: 0000 at address: 0x00000000ERASE
FAILED at 0x00000000! Expected=0xff, Read=0x25, failed byte count from
0x00000000-0x00003fff: 0x3fc0
ERASE FAILED!
ERASE FAILED!
FAILED!
Your flash chip is in an unknown state.
Get help on IRC at irc.freenode.net (channel #flashrom) or
mail flashrom at flashrom.org!
-------------------------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!
guy at asus-p4b:~/flashrom-0.9.1-r792$ 

Now I run r792 but this also fails erase.

I am quite sure the mobo can flash, as I was able to hotflash version
1012 in a SST49LF002A from a scrap mobo (using awdflash, and boot from
it.  Now I want to overwrite the 1008 bios with the 1012.bin image using
flashrom.  I realise the above assumption is only valid if bios 1012 has
not introduced additional protection against flashing, compared to bios
1008.




Op zaterdag 05-12-2009 om 15:38 uur [tijdzone +0100], schreef Adrian
Glaubitz:
> Hi,
> 
> On Sat, Dec 5, 2009 at 3:22 PM, guy lacroix <glx at skynet.be> wrote:
> > Dear Sirs,
> > i learned how to install libpcidev,(zlib1g-dev), libftdi-dev. That is
> > done.  I did not install subversion.
> > Source code folder flashrom-0.9.1 is in /home/guy and there I type make
> > flashrom.  Then I get output as in included error make flashrom.
> >
> > When I type sudo make flasrom I get
> > guy at asus-p4b:~/flashrom-0.9.1$ sudo make flashrom
> > [sudo] password for guy:
> > Checking for a C compiler... found.
> > Checking for FTDI support... found.
> > cc -Os -Wall -Werror  -D'SERPROG_SUPPORT=1' -D'FT2232_SPI_SUPPORT=1'
> > -D'FLASHROM_VERSION="0.9.1-r710"' -o physmap.o -c physmap.c
> > cc1: warnings being treated as errors
> > physmap.c: In function ‘rdmsr’:
> > physmap.c:146: error: dereferencing type-punned pointer will break
> > strict-aliasing rules
> > make: *** [physmap.o] Fout 1
> > guy at asus-p4b:~/flashrom-0.9.1$
> 
> I think the problem is this message:
> 
> cc1: warnings being treated as errors
> 
> The compilers treats normal warnings as errors and will therefore
> stop. Usually a warning shouldn't be a problem though.
> I can reproduce the error on Fedora 12, didn't test on Debian yet.
> However, when using the latest code from svn, everything compiles
> fine.
> 
> So please checkout the latest code from svn:
> 
> svn co svn://coreboot.org/flashrom/trunk flashrom
> 
> Install subversion prior to that.
> 
> 
> Adrian