1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
6 <meta name="generator" content="Movable Type 5.2.3" />
8 <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
9 <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
10 <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml"$>" />
12 <title>Status for Andrew DeFaria: December 2004 Archives</title>
14 <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
15 <link rel="prev" href="http://defaria.com/blogs/Status/archives/2004_09.html" title="September 2004" />
16 <link rel="next" href="http://defaria.com/blogs/Status/archives/2005_01.html" title="January 2005" />
18 <body class="layout-one-column">
20 <div id="container-inner" class="pkg">
23 <div id="banner-inner" class="pkg">
24 <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
25 <h2 id="banner-description">Searchable status reports and work log</h2>
30 <div id="pagebody-inner" class="pkg">
32 <div id="alpha-inner" class="pkg">
34 <p class="content-nav">
35 <a href="http://defaria.com/blogs/Status/archives/2004_09.html">« September 2004</a> |
36 <a href="http://defaria.com/blogs/Status/">Main</a>
37 | <a href="http://defaria.com/blogs/Status/archives/2005_01.html">January 2005 »</a>
43 <h2 class="date-header">December 30, 2004</h2>
45 <div class="entry" id="entry-267">
46 <h3 class="entry-header">More documentation</h3>
47 <div class="entry-content">
48 <div class="entry-body">
51 <p><li>Yet more documenting of Build, Test, Release processes</li></p>
55 <p class="entry-footer">
56 <span class="post-footers">Posted by at 5:27 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000267.html">Permalink</a>
66 <h2 class="date-header">December 29, 2004</h2>
68 <div class="entry" id="entry-266">
69 <h3 class="entry-header">Documentation</h3>
70 <div class="entry-content">
71 <div class="entry-body">
74 <li>Spent most of the day documenting <a href="http://saturn.lynx.com/build/">Build/Test/Release</a> processes</li>
78 <p class="entry-footer">
79 <span class="post-footers">Posted by at 10:09 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000266.html">Permalink</a>
89 <h2 class="date-header">December 28, 2004</h2>
91 <div class="entry" id="entry-265">
92 <h3 class="entry-header">Releasing 5.0.0</h3>
93 <div class="entry-content">
94 <div class="entry-body">
97 <li>Attempting to archive this 5.0.0 build both toolchain and lynxos. Not really sure where everything comes from or goes to</li>
99 <li>More work on cmptags.pl</li>
103 <p>Directories, builds, dated directories, etc are all over, spead out between t3, dopey, t-k1g-1, etc.. It's hard to know where things are and where they need to end up. Will look into this tomorrow with Thu</p>
105 <p>Regarding cmptags.pl, rearranged this to attempt to produce a simple list like:</p>
110 path/to/bar.c 1.2.3.1
113 <p>Unfortunately this appears to be very slow to process. cmptags.pl does not attempt to optimise things only working on files recently updated, rather it goes though all of the files in CVS and generates, parsed and creates data structures for all the CVS info, even that which it's not particularly interested in at the momment so that it can be more generally used. This takes forever with CVS as each file must be found and a cvs log issued and output parsed. Unlike Clearcase there doesn't seemto be a cvs command line prompt so cvs is constantly being invoked (process overhead) and it's always talking to the server (network overhead) and there's a lot of data (tags, revisions, comments, etc) to be processed. Clearly CVS has not been optimized for this sort of access.</p>
115 <p>Not sure how or if this can be optimized any further. It's a shame because I'm almost at the point where I can ask "Show me the files and version numbers for the following ECR's" which is something I know I'm gonna need quickly here for the impending build note that needs to be created.</p>
117 <p class="entry-footer">
118 <span class="post-footers">Posted by at 7:05 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000265.html">Permalink</a>
128 <h2 class="date-header">December 27, 2004</h2>
130 <div class="entry" id="entry-264">
131 <h3 class="entry-header">Fix Copyright, native 3.2.2/5.0.0 build</h3>
132 <div class="entry-content">
133 <div class="entry-body">
136 <li>Modified fix_copyright.pl to take into account the situation where the LynuxWork copyright is contained inside a comment block with another company's copyright.</li>
138 <li>Was able to build 3.2.2/5.0.0 toolchain natively by booking to the ide.0c partition</li>
140 <li>Build of non-development los178 is successful with expected errors</li>
144 <p class="entry-footer">
145 <span class="post-footers">Posted by at 9:36 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000264.html">Permalink</a>
155 <h2 class="date-header">December 22, 2004</h2>
157 <div class="entry" id="entry-263">
158 <h3 class="entry-header">los178 build</h3>
159 <div class="entry-content">
160 <div class="entry-body">
163 <li>Finished los178 build of sources with fixed copyrights!</li>
165 <li>Still an error with the non development build of los178 :-(</li>
167 <li>Made more progress on cmptags.pl (a Perl script to compare and report on the difference in terms of revisions and associated ECRs, authors and dates between two tags in CVS)</li>
171 <p>First I obtained the latest TOT for los178 - apparently they are still fixing things. This makes it imperative that fix_copyright.pl work flawlessly. Was able to build los178 from old, unmodified sources thus I know I'm starting from a good set of sources.</p>
173 <p>Next was to run fix_copyright.pl and attempt a compile. This time, instead of just hand editing the files I examined the file in question and why fix_copyright.pl failed in this case. Then fix fix_copyright.pl and repeat.</p>
175 <p>One problem was that some files have MS-DOS line endings. Fixed this by removing such line endings and making them standard Unix line endings.</p>
177 <p>Next some files ended the comment block with */ and then some additional spaces. This was fixed by not attempting to anchor the end comment block match with the end of the line (i.e. $).</p>
179 <p>Injected these actual two or three files back into the build process until it built.</p>
181 <p>For safety's sake I then destroyed my build area and recreated from scratch with cvs update -C then running fix_copyright.pl again and bringing that over to grumpy.</p>
183 <p>WRT cmptags.pl, made some more progress parsing cvs log info...</p>
185 <p class="entry-footer">
186 <span class="post-footers">Posted by at 3:28 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000263.html">Permalink</a>
196 <h2 class="date-header">December 21, 2004</h2>
198 <div class="entry" id="entry-262">
199 <h3 class="entry-header">Fixing fix_copyright.pl</h3>
200 <div class="entry-content">
201 <div class="entry-body">
204 <li>Decided to improve fix_copyright.pl. If two copyrights appear in a single copyright block it now just leaves that copyright intact.</li>
206 <li>Attempted rebuild of los178 and working out problems</li>
208 <li>Developing a better CVS report Perl script</li>
212 <p>Generally these copyright blocks with two copyrights are of the form described yesterday, with a single copyright line added for LynuxWorks. Such files will not be modified</p>
214 <p>Need to work out remaing los178 build problem and make fix_copyright handle them too.</p>
216 <p>Tried to get a Perl CVS module instead of coding it myself - seems there are no complete Perl CVS modules on CPAN!</p>
218 <p class="entry-footer">
219 <span class="post-footers">Posted by at 3:18 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000262.html">Permalink</a>
229 <h2 class="date-header">December 20, 2004</h2>
231 <div class="entry" id="entry-261">
232 <h3 class="entry-header">Improving fix_copyright.pl</h3>
233 <div class="entry-content">
234 <div class="entry-body">
237 <li>Still unable to build 3.2.2/5.0.0 natively</li>
239 <li>Worked on improving algorithm for copyright replacement</li>
243 <p>I'm finding it very difficult to develop a hueristic algorithm to find what I call "LynuxWorks copyright blocks" in existing source files. The problem is that the input data is not necessarily consistant. Sure we can go for the 80% fix and hand fix the rest (in fact, that's what I did before) however those 20% often cause compiler errors during the build. What's potential worse is that it is possible that some files will be altered in such a way as to not produce a compiler error but rather to change behavior of the resulting code.</p>
245 <p>My current algorithm attempts to do the following:</p>
248 <li>Locate the start of a C comment (i.e. "/*"). This comment must be at the beginning of the line (for now I am not considering inline comments as the chances of these containing a bona fide copyright statement is unlikely).</il>
250 <li>Scan until the enclosing end comment (i.e. "*/"). Again this must appear at the end of a line ($).</li>
252 <li>Take those lines and examine them for the works "(C) Copyright" and "LynuxWorks" (additionally I found some files that had "LynuxWork,").</li>
254 <li>If found then the comment block it throw out (to be replaced by the new, more consistent copyright block.</li>
258 <p>Currently the "official" copyright block is of the form:</p>
263 *************************************************************
270 $Revision: $Revision$
272 ************************************************************/
276 <p>The "$copy" is replaced by the copyright date found in the file. Dates of the form <year> are changed to <year>-<current year> (unless <year> == <current year>. Dates of the form <year1>, <year2>, <year3> are changed to <year1>-<curernt year>. In order to make finding such copyright information eaiser in the future I would suggest changing the above format to:</p>
280 /* Start Copyright ******************************************
282 (C) Copyright $copy LynuxWorks, Inc.
287 $Revision: $Revision$
289 * End Copyright *********************************************/
293 <p>This would 1) retain the "vi: ts=4 sw=4" annotation that I assume is for vi users, 2) group both the copyright string ("(C) Copyright") along with the company name of LynuxWorks on the same line. This makes it easier to grep for in the future considering some files have Rockwell copyrights. 3) Clearly delineates the start and stop of the copyright block.</p>
295 <p>The problems that I'm having is that I'm seeing copyright blocks of the following forms:</p>
298 <pre> /************************************************************
299 (C) Copyright 1987-2000
300 Lynx Real-Time Systems, Inc.
304 $Date: 2003/11/14 22:44:44 $
306 ************************************************************/
310 <p>(Does not contain LynuxWorks, rather Lynx Real-Time Systems)</p>
316 ***********************************************************************
320 ***********************************************************************
324 * INFORMATION SUBJECT TO EXPORT CONTROL LAWS
326 * Subject to local country rules and laws when applicable, you
327 * must comply with the following:
329 * These commodities, technology, or software were exported from
330 * the United States in accordance with the Export Administration
331 * Regulations. Diversion contrary to U. S. law and other relevant
332 * export controls is prohibited. They may not be re-exported to
333 * any of the following destinations without authorization; Cuba,
334 * Iran, Iraq, Libya, North Korea, Sudan or any other country to
335 * which shipment is prohibited; nor to end-use(r)s involved in
336 * chemical, biological, nuclear, or missile weapons activity.
339 * (C) Copyright 2001 Rockwell Collins, Inc. All rights reserved.
345 * utility to display disk usage
349 * ABBREVIATIONS/ACRONYMS:
351 *****************************************************************
354 /************************************************************
355 (C) Copyright 1987-1996
356 Lynx Real-Time Systems, Inc.
360 $Date: 2003/09/10 15:24:57 $
362 ************************************************************/
366 <p>Contains multiple "(C) Copyright" strings, one being ours and the other being Rockwell's. Should both exist in the resultant file?</p>
372 **********************************************************************
378 * Performs the integrity check of the program and data files
379 * in the CPR read only file system.
381 * ABBREVIATIONS/ACRONYMS: (optional)
386 * (C) Copyright 2001-2002 Rockwell Collins, Inc. All rights reserved.
387 * Proprietary and confidential material. Distribution,
388 * use, and disclosure restricted by Rockwell Collins, Inc.
389 * Copyright (c) 2003-2004, LynuxWorks, Inc. All Rights Reserved.
391 ***********************************************************************
397 <p>Contains multiple "(C) Copyright" strings, one being ours and the other being Rockwells, in the same comment block! Also notice the inconsistant form of one bying "(C) Copyright" while the other being "Copyright (C)". How should this case be handled?</p>
399 <p class="entry-footer">
400 <span class="post-footers">Posted by at 5:55 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000261.html">Permalink</a>
410 <h2 class="date-header">December 17, 2004</h2>
412 <div class="entry" id="entry-260">
413 <h3 class="entry-header">LOS178 Build/5.0.0 native toolchain build</h3>
414 <div class="entry-content">
415 <div class="entry-body">
418 <li>LOS178 build after copyright fix builds with 12 errors. Test build of LOS178 without copyright fix also builds with 12 errors!</li>
420 <li>Building of 5.0.0 toolchain natively is failing</li>
424 <h3>LOS178 copyright fix</h3>
426 <p>The Perl script to fix the copyrights in LOS178 sources needs detect if there was a prior copyright block and replace it if necessary. Finding old copyright blocks is hueristic in nature and thus fallable. The problem is there are no sentenals clearly marking our copyright. The best the script can do is attempt to find a comment block that starts and ends with a particular comment line based on the "/" and a number of "*"'s for the start and a number of "*"'s and a "/" for the end. Problem is we do not know if what's inbetween is really our copyright. The hueristic can be tuned finer with some difficulty but currently it does not.</p>
428 <p>The real difficulty is that there is no real standard in our copyright blocks thus it is hard to get this right</p>
430 <p>As it stands the script occasionally misinterprets a comment block, sometimes just the ending comment block, and alters the file in such a way that it introduces compile errors.</p>
432 <p>There were a number of files that this occurred in and they were hand edited</p>
434 <h3>5.0.0 Native Toolchain Build</h3>
436 <p>In picking up ECR 23084 I was able to build the toolchain for both cross x86 and ppc. In building the native toolchain there is an error:</p>
439 Configuring texinfo...
440 configure: error: invalid package name: gcc-version-trigger
441 Configure in /mnt/toolchain/build-i386/texinfo failed, exiting.
442 make: *** [stamp-configure-i386] Error 1
445 <p>Thu says that I didn't run fixup.sh but I did. The toolchain does not package up fixup.sh so I grabbed one from somewhere. Thu suggests that we file an ECR for this and fix the Makefile.</p>
447 <p class="entry-footer">
448 <span class="post-footers">Posted by at 10:38 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000260.html">Permalink</a>
458 <h2 class="date-header">December 16, 2004</h2>
460 <div class="entry" id="entry-259">
461 <h3 class="entry-header">LOS178 & ECR 23084</h3>
462 <div class="entry-content">
463 <div class="entry-body">
466 <li>Wrote a Perl script to fix up copyrights on LynxOS (178). Working on running that and getting the build to work</li>
468 <li>Pulled ECR 23084 and built toolchain for x86 & ppc. Need to build native</li>
472 <p class="entry-footer">
473 <span class="post-footers">Posted by at 9:24 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000259.html">Permalink</a>
483 <h2 class="date-header">December 14, 2004</h2>
485 <div class="entry" id="entry-258">
486 <h3 class="entry-header">ECRs 23079 & 23080</h3>
487 <div class="entry-content">
488 <div class="entry-body">
491 <li>Submitted ECR: 23079: PPC: target elf32-powerpc-lynx not found</li>
493 <li>Submitted ECR: 23080: OUTPUT_FORMAT directive should be adjusted to elf32-powerpc-lynx</li>
497 <p>Thu determined that we have a toolchain problem here so she had me submit ECR 23079. Adam debugged the problem which produced 23080</p>
499 <p class="entry-footer">
500 <span class="post-footers">Posted by at 4:55 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000258.html">Permalink</a>
510 <h2 class="date-header">December 13, 2004</h2>
512 <div class="entry" id="entry-257">
513 <h3 class="entry-header">Rebuilding PPC</h3>
514 <div class="entry-content">
515 <div class="entry-body">
518 <li>Rebuilding for the PPC. I messed up a step or two</li>
522 <h2>Building cross lynxos for PPC</h2>
526 <li>Cleaned up by removing the ppc directories (i.e. starting from scratch WRT the ppc)</li>
528 <li>Linked /usr/lynx/5.0.0 -> /export/build1/LYNXOS_500/build/lynxos/120604-A</li>
530 <li>In /export/build1/LYNXOS_500/build/lynxos/120604-A/int_tools modified START to change steps_ppc to just 1 and 2. We're gonna take this slowly.</li>
532 <li>Made sure that __profile.exp points to 120604-A. It still does, from before. There are a lot of settings in here that sometimes need to change depending on the situation. For example, right now the TOP_OF_TRUNK variable is set to no but it is usually set to yes.</li>
534 <li>Execute START and then tail -f LOGS/ppc.log.</li>
536 <li>Checked out with "check ppc". Seems OK.</li>
538 <li>Changed START to do steps 3 and 4. I think I could have done 1, 2, 3 and 4 together but Thu only wrote down 1 and 2</li>
540 <li>Checked again with check ppc. Still seems fine</li>
542 <li>Changed START to do steps 5en 5el 7 9 14 15 16 (17 doesn't work yet so why do it?) <font color="red"><b>Failure:</b></font> got:<br>
545 Failure reason : Compiler does not exist: /export/dev_archive/lynxos/tools-5.0.0/3.2.2-072304/toolchain-powerpc-lynx-lynxos-ppc.tar.gz
548 Ah ha! See this is one of those things that just confuses me. Contained in __profile.exp there's:
552 #set DIR_PATH(compilers) "/usr/lynx/t3/dev_archive/lynxos/tools-5.0.0/3.2.2-072304"
553 set DIR_PATH(compilers) "/export/dev_archive/lynxos/tools-5.0.0/3.2.2-072304"
556 need to uncomment the first line and comment out the second line.</li>
558 <li>After making the above change I reran START. Errors in makeall.log</li>
562 <h2>Build ppc toolchain</h2>
564 <p>Thu said that the error sin makeall.log were acceptable. Continuing on to build the ppc toolchain...</p>
568 <li>cd /usr/lynx/5.0.0/ppc (note that /usr/lynx/5.0.0 still points to 120604-A)</li>
570 <li>Ran . SETUP.bash setting ENV_PREFIX to cwd, target = ppc. which gcc yeilds /usr/lynx/5.0.0/ppc/cdk/linux-elf-ppc/bin/gcc</li>
572 <li>Toolchain is in /export/build1/LYNXOS_500/build/toolchain/3.2.2/120804 so cd'ed there</li>
574 <li>make install > install-ppc.log 2>&1 &</li>
576 <li>Toolchain seemed to build OK this time. Archived toolchain by doing make package then moving toolchain-i686-pc-linux-gnu-powerpc.tar.gz to /usr/lynx/t3/dev_archive/lynxos/tools-5.0.0/3.2.2-120604. This is a little tricky because this path is a link to a mount on t3 and as such is considered a read only file system. The following worked for me, in /export/build1/LYNXOS_500/build/toolchain/3.2.2/120804:</li>
579 $ rcp toolchain-i686-pc-linux-gnu-powerpc.tar.gz int@t3:/export/dev_archive/lynxos/tools-5.0.0/3.2.2-120604
584 <h2>Building cross lynxos for PPC (again)</h2>
588 <li>Linked /usr/lynx/5.0.0 -> /export/build1/LYNXOS_500/build/lynxos/120604-B</li>
590 <li>In /export/build1/LYNXOS_500/build/lynxos/120604-B/int_tools modified START to change steps_ppc to for 1, 2, 3 and 4.</li>
592 <li>Execute START and then tail -f LOGS/ppc.log. Steps 1-4 seemed to have worked OK</li>
594 <li>Looked at __profile.exp and found
596 <tt><pre>set DIR_PATH(compilers) "/usr/lynx/t3/dev_archive/lynxos/tools-5.0.0/3.2.2-120604"
599 The compiler exists there (because of the archiving step above). Note there was no t3 style reference here.</li>
601 <li>Ran START again and monitored logs... Errors stating "gcc: installation problem, cannot exec `cc1': No such file or directory"</li>
606 <p class="entry-footer">
607 <span class="post-footers">Posted by at 2:40 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000257.html">Permalink</a>
617 <h2 class="date-header">December 10, 2004</h2>
619 <div class="entry" id="entry-256">
620 <h3 class="entry-header">Building 5.0.0 ppc cross toolchain</h3>
621 <div class="entry-content">
622 <div class="entry-body">
625 <li>Built 5.0.0 ppc cross toolchain - looking for ppc to build native</li>
627 <li>Rebuilding 5.0.0 ppc using previous toolchain (having problems)</li>
631 <p class="entry-footer">
632 <span class="post-footers">Posted by at 3:06 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000256.html">Permalink</a>
642 <h2 class="date-header">December 9, 2004</h2>
644 <div class="entry" id="entry-255">
645 <h3 class="entry-header">Building 5.0.0 for ppc</h3>
646 <div class="entry-content">
647 <div class="entry-body">
650 <li>Built 5.0.0 for ppc</li>
652 <li>Studying CVS</li>
656 <p>I was under a mistaken assumption that I needed to have a PPC machine in order to do this and was waiting for one. Thu informed me that I could build 5.0.0 for cross and even rebuild the toolchain cross - that I wouldn't need a ppc machine until I needed to build a native gcc.</p>
658 <p>Building for ppc takes a long time as our ppc machines are slow and there's a lot more to build for ppc.</p>
660 <p class="entry-footer">
661 <span class="post-footers">Posted by at 3:04 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000255.html">Permalink</a>
671 <h2 class="date-header">December 8, 2004</h2>
673 <div class="entry" id="entry-254">
674 <h3 class="entry-header">Booting 5.0.0 LynxOS</h3>
675 <div class="entry-content">
676 <div class="entry-body">
679 <li>Used loadit.exp to run ATS of for this new 5.0.0 LynxOS
683 <p>Failed to get loadit.exp to work. Seems that it is oriented to getting the images off of t3. But I didn't put this new images on T3 yet. Seems there's some rync process that Thu flew by me and I missed.</p>
685 <p><b>Note:</b> loadit.exp <b>requires</b> a working network connection to the System Under Test! When last we left t-k1g-1 it was booted to lynxos with non-working networking. loadit.exp sits and waits at an rcp command and the SUT never responds!</p>
687 <p class="entry-footer">
688 <span class="post-footers">Posted by at 11:37 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000254.html">Permalink</a>
698 <h2 class="date-header">December 7, 2004</h2>
700 <div class="entry" id="entry-253">
701 <h3 class="entry-header">Building 5.0.0 TOT toolchain</h3>
702 <div class="entry-content">
703 <div class="entry-body">
706 <li>Built 3.2.2 toolchain natively on Lynxos 5.0.0</li>
710 <p>Came in to find that the native build of the 5.0 toolchain went nowhere. Seems, as I expected, that I need to unpack 18010.x11r6.tar.gz and 18011.pd.tar.gz too. Unpacked that and restarted build.<p>
712 <p>Build failed again, this time <i>Memory Exhausted</i>. I had to do <tt>ulimit -s -d 1000000</tt> and restart build</p>
714 <p>Build finally succeeded. Did make package then copied to t3 area (to be precise <tt>t3:/export/dev_archive/lynxos/tools-5.0.0/3.2.2-120604</tt>). Only needed to copy over the <tt>toolchain-i386-lynx-lynxos-i386.tar.gz</tt> as this package is the 5.0.0 toolchain built natively</p>
716 <p>Created a new build area on dopey @ <tt>/export/build1/LYNXOS_500/build/lynxos/120604-C</tt>. Needed to copy over int_tools and modify <tt>int_tools/__profile.exp</tt> to:
720 <li>Change <tt>DIR_PATH(archive)</tt> back to dopey (it was at t3 for 120604-B) </li>
722 <li>Change <tt>int_tools/EXP_LIB/steps.exp</tt> to use gnuaout instead of gnu in the name of the package. There is a little debate of which way this should go</li>
726 <p><b>Note:</b> I find all of these different machines with different long pathnames confusing. For example, I would think using the principal of separation of code and data that the <i>int_tools</i> code should be globally accessible and that one should not be modifying variable contents before running scripts. That's data and should either have to be supplied or kept in a data file perhaps separate for each build run. IOW <i>int_tools</i> should be globally visable (perhaps in one's PATH) and execuable as code and not modified per run. Also, as such it should in CVS and perhaps grabbed from CVS with an official TAG.</p>
728 <p class="entry-footer">
729 <span class="post-footers">Posted by at 6:54 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000253.html">Permalink</a>
739 <h2 class="date-header">December 6, 2004</h2>
741 <div class="entry" id="entry-252">
742 <h3 class="entry-header">Building LynxOS with gcc 3.2.2</h3>
743 <div class="entry-content">
744 <div class="entry-body">
747 <p><li>Build 3.2.2 toolchain successfully</li></p>
752 <p>Managed to build the toolchain (gcc 3.2.2) successfully. We had to first build LynxOS then build the compiler then build LynxOS again. Confusing indeed. Lot's of paths and scripts. I'm still not totally comfortable with the environment, how to build, native vs. cross, toolchain vs. LynxOS, CVS top of trunk, etc.</p>
754 <p class="entry-footer">
755 <span class="post-footers">Posted by at 5:01 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000252.html">Permalink</a>