Status for Andrew DeFaria

• Portgd still not working well
• Build 3.0.0 TOT again
• Added package of pdn to 2.1.0. Somehow I missed it
• Repackaged cdklinux

Portgd's continuing woes

Turns out the problem is that we are attempting to do a cvs add from outside of the repository. Portgd works from one directory and checks out an los178.from and an los178.to. Then from that directory it attempts to cvs add los178.to/<path>/<dir>. This will not work. We need, instead, to cd los178.to then do cvs add <path>/<dir>.

But portgd was also having a problem trying to recursively add the directories above new files. How to debug/test this is the question...

Posted by at 5:00 PM | Permalink

• Changed portgd script to attempt to handle new CVS files/li>
• Changed package.sh for 3.0.0 to package NetSNMP
• Release LOS178 2.1.0. Still working on building GDB on Windows
• Built and released LOS178 3.0.0 20050825. Turns out the toolchain I was using does indeed have the latest!
• Port of GD from LOS178 has some missing CRs. Will work on this tomorrow

Posted by at 12:43 PM | Permalink

• Performed a TOT 3.0.0 build. More stuff coming in...
• Struggling with 2.0 GD build. Turns out I was missing some CRs. Finally building!
• GDB Server build on Solaris is OK now but it fails on Linux. I suspect a packaging problem
• The portgd script has issues

Portgd Challenges

One of the problems with portgd is that the from CVS repository really needs to be set to HEAD because you want the latest but you're gonna pull the CRs by number and individual file revisions. This may cause problems sometimes (think ordering of CR numbers where pulling one CR overwrites a previous one in the wrong way. BTW This is why branching is good!)

Additionally portgd has a problem where the CR introduces new elements (Clearcase term - think new files and/or directories). When portgd attempts to cp the file to the to CVS repository it may fail because the parent directory did not previously exist and is not in the to CVS repository.

The portgd script can be updated to check to insure that each directory in the path of the file revision to be "ported" exists and if not then to create it and add it to CVS. It should also check to see if the file is new and again copy it but also add it to CVS.

Posted by at 11:32 AM | Permalink

• Linux ABI build fails. Reported to vlad
• GDB build failed. Rebuilding...

Linux ABI build failure

The Linux ABI fails to build on yellowdog Linux.

    + DebugFlags=
    + export GLIBC_LOCATION LYNX_PREFIX LIBLYNXPTHREAD_PREFIX
    + export LYNXOS_VERSION_MAJOR LYNXOS178_VERSION_MAJOR
    + '[' 1 '!=' 0 ']'
    + '[' '!' -r /home/int/LOS178-300/20050822/linuxabi/glibc-2.3.3/../liblynxpthrea
    d/Makefile ']'
    + echo ======================= BUILD - LIBLYNXPTHREAD ==========================
    ===========
    ======================= BUILD - LIBLYNXPTHREAD =================================
    ====
    + cd /home/int/LOS178-300/20050822/linuxabi/glibc-2.3.3/../liblynxpthread
    + make PLATFORM=ppc
    make: *** No rule to make target `include/itimer.h', needed by `all'.  Stop.
    + exit 1

itimer.h has been removed. There are other problems too.

GDB Build Failure

For some reason it turns out that several libraries such as libc.a appear in the dev area as if they were built as production. IOW the size of libc.a(dev) == libc.a(pdn). Don't know why this happened because the install.log for dev seems to indicate that it was built in dev mode. May be a problem in the build_los178 script. Rebuilding...

Also, due to hardcoding of bison's location we must build in /usr/los178/2.1.0/ppc_dev.

Posted by at 6:10 PM | Permalink