[CUWiN-Dev] Re: [CU-Wireless-Support] Problems Compiling CUWireless Software...

Sun Oct 29 13:27:30 CST 2006

I'm not sure.  I've CC'ed our conversation to our developers mailing list.
Perhaps one of them will know whats going on.

On 10/29/06, Mark Cather <mark.cather at umbc.edu> wrote:
>
> Thanks for the instructions.  The pxe instructions are much clearer than
> the others.
>
> Unfortunately, I'm still getting the same error.  Is there supposed to be
> something in the modules.d directory?  The only file in the modules.ddirectory is the .svn file.
>
> What do we try next?
>
> Mark
>
> On Oct 28, 2006, at 12:24 PM, Matt Isaacs wrote:
>
> Thanks for the extra info Mark.  That helps a lot in pinpointing the
> trouble.  I'm sorry about the state of the developer instructions on our
> site; we're working on updated versions that reflect our current build
> process and that are clearer and easier to understand.
>
> You may check out the somewhat confusing
> http://cuwireless.net/files/pxe4526instr.txt or, in pdf:
> http://cuwireless.net/files/pxe4526instr.pdf documents on our website.
>
> Typically, we make a .mkstabootrc file in our home directories.  This file
> sets all the required environment variables for the build process and is
> automatically sourced by it.  Manually setting these environment variables
> should also work, and most of them have a corresponding commandline switch
> as well.  Here is a typical .mkstabootrc file:
>
>  BUILDDIR=$HOME/cuwin/scratch
>  SRC=$HOME/cuwin/scratch/src
>  LOWER_FAT=yes
>  MACHINE_ARCH=i386
>
> The BUILDDIR variable holds the path to the location you wish to place the
> object files and other intermediary compile-time files.  SRC specifies the
> path to the NetBSD source code.  LOWER_FAT instructions the build process to
> not compile certain portions of NetBSD ( i.e. Games and X11).  The
> MACHINE_ARCH variable is used to allow the build process to build the
> appropriate cross-compiler for your machine.
>
> You should then  be able to run the 'buildiso' command with no problems.
> Once you have a successful compile, you may use the '-u' command switch to
> instruct the build process to only recompile things that have changed (so it
> won't recompile NetBSD).  The build process also supports beginning at
> certain steps.  So, for instance, once you have a working building you may
> pass 'users' as an arguement to the build process and it will begin with the
> step of insert the user and password database in the build.
>
> Hope this helps.
>
> On 10/27/06, Mark Cather <mark.cather at umbc.edu> wrote:
> >
> > I've tried the precompiled ISOs, but I need to make some changes.  For
> > our testing, I'm trying to use atheros 802.11a cards.  In a final
> > version, I would also like to use the Ubiquity Superrange 9 card.  I am
> > located just outside of Baltimore, MD; and we have a lot of trees in our
> > area.  It is my hope that the 900MHz Superrange 9 will help us penetrate the
> > trees and reach houses.  We also may use 802.11a to provide backbone
> > links between local radio towers.  In my area, the trees and interference
> > kill any hopes of using 2.4GHz.
> >
> > I have read almost all the instructions that I can find at your
> > website.  I've especially focused on the Building From Source and Developers
> > Guide documents.  I found what looks like instructions imbedded in the
> > mkstaboot file.  I've also gone through and read most of the makefiles and
> > the files with the names in all caps.  The documentation has been a little
> > hard to follow.  If I'm looking in the wrong spots, please let me know.
> >
> > I have been starting the build by setting up the environment variables.
> > The variables that I'm using are listed in my first message (see below).
> > Once I setup the environment variables, I have been running "./buildiso"
> > from the boot-image directory.  It runs for a couple of hours and then gives
> > me the error that I listed.  I don't have a .mkstabootrc file.  My build
> > machine is NetBSD 3.0.1.  The NetBSD and CUWireless source files are the
> > ones from your download site.
> >
> > Thank you for your quick reply and any help you can provide.  Your
> > installation looks like a great build.  If I can tweak the drivers, ssid,
> > password and other details; it should suit our needs in Baltimore very well.
> >
> >
> > Mark
> >
> >
> > On Oct 27, 2006, at 11:07 PM, Matt Isaacs wrote:
> >
> > Mark,
> >
> > Glad to hear your trying software.  Hopefully we can get you up and
> > running with it soon.
> >
> > A couple questions, so we know exactly whats happening.  First, what
> > instructions are you following to compile the software?  Second, what was
> > the command line you used to start the compile process?  And last, do you
> > have a .mkstabootrc file in your home directory?
> >
> > This information will help us determine where the problem may be
> > located.
> >
> > Also, I just wanted to let you know that there are precompiled images
> > and iso's available for our software, should you consider to take that
> > route.
> >
> >
> > --
> > Matthew Isaacs
> >
> > CUWiN Network Engineer
> >
> >
> > On 10/27/06, Mark Cather < mark.cather at umbc.edu> wrote:
> > >
> > > I am trying to compile CUWinware from source and I'm running into
> > > some trouble.  I have a NetBSD box up and running.  I have downloaded
> > > the cuwin-0.7.0-netbsd-src.tar and cuwin-0.7.0-src.tar files from
> > > your website.  When running the buildiso script, it crashes with the
> > > error:
> > >
> > > running modules.d/* obj
> > > .: Can't open ./modules.d/*
> > > ./mkstaboot: exiting prematurely
> > > obj ===> viz/daemon
> > > obj ===> viz/tile
> > > obj ===> viz/images
> > > obj ===> athtools
> > > obj ===> athtools/athstats
> > > obj ===> utd
> > > running modules.d/* obj
> > > .: Can't open ./modules.d/*
> > > ./mkstaboot: exiting prematurely
> > > #
> > >
> > > cuwin-0.7.0-src/src/boot-image/modules.d does exist.  The only thing
> > > in the directory is .svn.  I have tried to set the environment
> > > variables correctly.  I have set the following variables:
> > >
> > > setenv REBUILD_ALL yes
> > > setenv BUILDDIR /root/CUWIN/BUILDDIR
> > > setenv CUWSRC /root/CUWIN/cuwin-0.7.0-src/src/boot-image
> > > setenv SRC /root/CUWIN/nbsd/src
> > > setenv EXTSRC /root/CUWIN/cuwin-0.7.0-src/src
> > > setenv MACHINE_ARCH i386
> > >
> > > Am I missing something?  Any help would be greatly appreciated.
> > >
> > > Thanks,
> > >
> > > Mark Cather
> > > Office of Information Technology / UMBC
> > >
> > >
> > > _______________________________________________
> > > CU-Wireless-Support mailing list
> > > CU-Wireless-Support at lists.cuwireless.net
> > > http://lists.chambana.net/cgi-bin/listinfo/cu-wireless-support
> > >
> >
> >
> >
> >
> >
>
>
> --
> Matthew Isaacs
>
> CUWiN Network Engineer
>
>
>

-- 
Matthew Isaacs

CUWiN Network Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.chambana.net/mailman/archive/cu-wireless-dev/attachments/20061029/77bab687/attachment.html