LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Advertise
  • Mirrors
  • Logos
  • Contact us
  • Find Resources
  • Job Opportunity
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Openrisc > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: =?unknown-8bit?Q?Gy=F6rgy?= 'nog' Jeney<nog@j...>
    Date: Tue Jan 25 15:46:02 CET 2005
    Subject: [openrisc] [or1ksim] Fix generate.c
    Top
    On 0, Matjaz Breskvar <phoenix@o...> wrote:
    > > I sugest that the cpu/or32/execgen.c be removed from cvs as it is dynamicaly
    > > generated from insnset.c.
    >
    > That would actully break the build of or1ksim. If i'm not mistaken if you
    > do a build in seperate directory than the one with
    > source files the execgen.c from source files will be used... So we
    > should fix the makefiles too....

    I'll have a look at it.

    > > You may also want to update the configure script (and all the other files that
    > > depend on configure.in) in cvs as it is older than configure.in.
    >
    > Ok, the problem here is with automake tools on the opencores
    > server. They are quite old, and ussualy the ATS builds then fail.

    So the server should generate these dynamically? Wouldn't it suffice if the
    maintainer of or1ksim regenerated these files when needed? They really don't
    change that often.

    nog.

    ReferenceAuthor
    [openrisc] [or1ksim] Fix generate.cMatjaz Breskvar

     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.