You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(17) |
Feb
(9) |
Mar
(25) |
Apr
(40) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(3) |
2004 |
Jan
(5) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Ed C. <ed....@gs...> - 2004-06-04 13:44:15
|
As the member who tipped you off about the installer kernel being built for a PIII, I can tell you that this is not fixed in 1.2. The installer kernel in the generic i386 BSP remains precompiled for PIII. We also had some problems with certain network cards. It seemed that no amount of fiddling with the settings would cause it to actually compile the ne2000 driver. After a lot of digging in the scripts, this was finally traced to the state of a kernel config variable called "CONFIG_NET_ISA" which was set to "n". Attempting to change it to "y" did not work, as something reset it to "n' every time. The result is that certain drivers in an ISA architecture can never be built. More digging in the scripts finnaly traced the problem to the file "rules.cml" in "q+esto/bsp/i386/generic/cmls/kernel-tree". Towards the end, in a section commented with "Declare these to suppress some 'unknown symbol' messages...", change the line "derive NET_ISA from n" to "derive NET_ISA from y" This will fix the problem for any new projects created from now on. To fix it for an existing project, make the same change in the file "rules.out" in the root directory of the project, and remove the existing "config.kernel" in the same directory. It will then get rebuilt correctly. Now, all of the above applies to your project's kernel, but you also have be sure that the new installer kernel that you build also has the correct network driver, Further, the new installer kernel should have the driver built directly into the kernel instead of as a module. It is possible to do it as a module, but it is a lot more complicated, involving modifying the prebuilt installer's initial ramdisk (initrd). Hope this helps. @(^.^)@ Ed > Aron Reid wrote: > > Thanks to one of the members here, I found out that the install kernel > is designed for the PIII/Cele board, so I tried it, and it worked > fine, however as another member on this board had a problem where by > the boot kernel would contain a Tulip and 3C95x.o file however that > was all [This is during the Qplus Install Boot, where you press 1, the > IP and then install.conf]. I am having the same issue, and when I > look in the /net folder there is absolutely nothing. Also I tried > checking the rootfs.tar.gz file, and again, nothing, I tried copying > it in, and it didn't show up in the shell. I removed all files except > for qplus.etherboot and still it booted, so by process of elimination > the qplus.etherboot file contains the rootfs for the install kernel > too I assume? > > Anyhow, I have also put a "Y" on "Realtek 8139" the chipset that I am > using, recompiled the system, and same thing. > > Going to the FTP site for Qplus I noted version 1.2 (I am using 1.0) > would upgrading fix this? Would It fix my original issue where by the > install kernel is specifically designed for PIII/Cele regardless of > what I set in the Qplus builder? (I have it set to MMX, P1, PIII > anything and yet my Socket 7 P1MMX reboots when loading the kernel) > > Thank You Again All; > Aron R. |
From: Aron R. <Aro...@Ro...> - 2004-06-04 05:07:25
|
Thanks to one of the members here, I found out that the install kernel = is designed for the PIII/Cele board, so I tried it, and it worked fine, = however as another member on this board had a problem where by the boot = kernel would contain a Tulip and 3C95x.o file however that was all [This = is during the Qplus Install Boot, where you press 1, the IP and then = install.conf]. I am having the same issue, and when I look in the /net = folder there is absolutely nothing. Also I tried checking the = rootfs.tar.gz file, and again, nothing, I tried copying it in, and it = didn't show up in the shell. I removed all files except for = qplus.etherboot and still it booted, so by process of elimination the = qplus.etherboot file contains the rootfs for the install kernel too I = assume? Anyhow, I have also put a "Y" on "Realtek 8139" the chipset that I am = using, recompiled the system, and same thing. =20 Going to the FTP site for Qplus I noted version 1.2 (I am using 1.0) = would upgrading fix this? Would It fix my original issue where by the = install kernel is specifically designed for PIII/Cele regardless of what = I set in the Qplus builder? (I have it set to MMX, P1, PIII anything and = yet my Socket 7 P1MMX reboots when loading the kernel) Thank You Again All; Aron R. |
From: Aron R. <Aro...@Ro...> - 2004-06-02 17:33:21
|
I have given that a shot, changing the processor to Pentium and MMX both do the same thing after a Forced Kernel build, then deploying the images (Still just reboots) this board is a Socket 7 that I'm using with the Host machine right now so I don't see why it wouldn't work, the specs of the board are bellow if anyone can see any compliancy problems. http://www.lannerinc.com/products/ViewProduct.asp?view=86 I appreciate the help, also I am using a ROM file from rom-o-matic.org, since I did not know if there is anything specific I needed I just downloaded the newest *.iso rom and that was it, maybe its the ROM? I tried to use one of the pre-existing *.lzdsk files, but it just goes "Searching for DHCP" and keeps going, however the rom-o-matic rom at least downloads the qplusp.etherboot file. Thank You All; Aron Reid ----- Original Message ----- From: <je...@ch...> To: "Aron Reid" <Aro...@ro...>; <qpl...@li...> Sent: Wednesday, June 02, 2004 12:48 PM Subject: Re: [Qplus-devel] Target Builder; not deploying > This sounds like the infamous processor type problem. Change the CPU type to "Pentium" (I think PIII is the default) and do a "Build Force". > > Jerry > > > > > From: "Aron Reid" <Aro...@ro...> > > Date: 2004/06/01 Tue PM 07:00:54 GMT > > To: <qpl...@li...> > > Subject: [Qplus-devel] Target Builder; not deploying > > > > Hello all, I've seen this question posted a few times but no real resolution, so I figure maybe I can give it another shot. > > > > Alright, here is my issue, when I try to deploy the target image, it transfers the "qplusp.etherboot" file and then just stops at "Ok, booting Kernel" and nothing more. This happens on a Cyrix Media GX board (http://www.lannerinc.com/products/ViewProduct.asp?view=55). In the mailing list I saw a few suggestions to use a pure x86 processor, so I tried a Socket 7 P1-MMX at 233MHz (http://www.lannerinc.com/products/ViewProduct.asp?view=86) and the unit just reboots at the same stage. > > > > So having said this, is there a way to get this to work? Or perhaps is there a way I can deploy this right to the HDD? This is just for prototyping so anything that makes it work is good :) So does anyone know of a way I can just move the files to the hard drive, maybe by CD or make a bootable CD or something? > > > > Thank You; > > Aron R. > > > |
From: <je...@ch...> - 2004-06-02 17:12:14
|
This sounds like the infamous processor type problem. Change the CPU type to "Pentium" (I think PIII is the default) and do a "Build Force". Jerry > > From: "Aron Reid" <Aro...@ro...> > Date: 2004/06/01 Tue PM 07:00:54 GMT > To: <qpl...@li...> > Subject: [Qplus-devel] Target Builder; not deploying > > Hello all, I've seen this question posted a few times but no real resolution, so I figure maybe I can give it another shot. > > Alright, here is my issue, when I try to deploy the target image, it transfers the "qplusp.etherboot" file and then just stops at "Ok, booting Kernel" and nothing more. This happens on a Cyrix Media GX board (http://www.lannerinc.com/products/ViewProduct.asp?view=55). In the mailing list I saw a few suggestions to use a pure x86 processor, so I tried a Socket 7 P1-MMX at 233MHz (http://www.lannerinc.com/products/ViewProduct.asp?view=86) and the unit just reboots at the same stage. > > So having said this, is there a way to get this to work? Or perhaps is there a way I can deploy this right to the HDD? This is just for prototyping so anything that makes it work is good :) So does anyone know of a way I can just move the files to the hard drive, maybe by CD or make a bootable CD or something? > > Thank You; > Aron R. > |
From: Aron R. <Aro...@Ro...> - 2004-06-01 19:01:02
|
Hello all, I've seen this question posted a few times but no real = resolution, so I figure maybe I can give it another shot. Alright, here is my issue, when I try to deploy the target image, it = transfers the "qplusp.etherboot" file and then just stops at "Ok, = booting Kernel" and nothing more. This happens on a Cyrix Media GX = board (http://www.lannerinc.com/products/ViewProduct.asp?view=3D55). In = the mailing list I saw a few suggestions to use a pure x86 processor, so = I tried a Socket 7 P1-MMX at 233MHz = (http://www.lannerinc.com/products/ViewProduct.asp?view=3D86) and the = unit just reboots at the same stage. =20 So having said this, is there a way to get this to work? Or perhaps is = there a way I can deploy this right to the HDD? This is just for = prototyping so anything that makes it work is good :) So does anyone = know of a way I can just move the files to the hard drive, maybe by CD = or make a bootable CD or something? Thank You; Aron R. |
From: Ron P. <ron...@gs...> - 2004-03-12 15:52:29
|
Has anyone incorporated the M-Systems Disk-On-Chip driver module into the QPlus system? I would like to be able to build and deploy DOC images directly to the Disk-On-Chip. This would require not only building the driver module for a target initrd but also incorporating it into the initrd for the installer kernel so that it can talk to the DOC to install the image. Seems like it may be a tedious process so I wanted to see if anyone had already done it. Ron Parise |
From: <gra...@bt...> - 2004-02-13 10:11:58
|
Hi=20 I have recently been trying out your very interesting Embedded Linux = Config Management/Build Tool Qplus-P. I would like to know what is the most uptodate version of the Software = which is available for=20 download ? My target systems is i386 generic.=20 I began by downloading all files from = <http://qplus.etri.re.kr/qplus-p/ftp/1.2/qplus_rpm/>=20 into a directory and I installed by running install.sh. Is this version = 1.2 of Qplus-P (as the=20 URL path suggests) ? I notice that the Sourceforge site for Qplus-P = seems to have version=20 1.0 of Qplus, which would seem to be older than what I have installed.=20 I am confused as to how to obtain the most uptodate version of the = software after looking=20 at your Download page with links to=20 <http://qplus.etri.re.kr/qplus-p/ftp/updates/1.0/qp-tb-2.0-032703.tar.gz>= =20 <http://qplus.etri.re.kr/qplus-p/ftp/updates/1.0/qp-rpm-4.0.3-7x-032703.t= ar.gz>=20 <http://qplus.etri.re.kr/qplus-p/ftp/updates/1.0/qp-tb-2.0-032703.tar.gz>= =20 <http://qplus.etri.re.kr/qplus-p/ftp/updates/1.0/qp-bsp-i386-generic-lkc-= 1.0-021003.tar.gz>=20 Which of the above files do I need to download and install to have the = most uptodate Qplus-P ?=20 Or is the version based in the directory = <http://qplus.etri.re.kr/qplus-p/ftp/1.2/qplus_rpm/>=20 the most uptodate one ?=20 Please feel to copy this email and any replies to qplus-developers email = list at Sourceforge.=20 Thanks for your help.=20 Graeme N Brown=20 emailto:gra...@bt... |
From: Jerry E. <je...@ep...> - 2004-01-20 19:58:36
|
Perhaps the most direct way to accomplish this is simply to: 1. Use the 'Install to target system' deployment method to generate the kernel and root filesystem (see section 3.7 of the manual). 2. Mount the CF card on the cross-development host. 3. Transfer the kernel and root fs images to the CF card. 4. Set up lilo on the CF card. 5. Move it over to the target and boot. Alternatively, using the rsync-based 'Install to target system' functionalilty directly, keeping the CF card installed on the target, might work for you, since you do have an Ethernet interface on the target. Jerry Terje Utheim wrote: > >> Hello, my name is Terje Utheim, I work with the University of Bergen in >> Norway at the Institute og Geoscience. >> My project is designing field recorders for recording earthquakes. We >> are >> now looking for posibillities lowpower embedded Linux systems. >> I read through your documentation for Qplus and found it intresting. >> However I have a question before actually trying out your software: >> >> Our development configuration is: >> >> Host: >> Standard desktop PC with Redhat 9.0 >> PCMCIA interface with Compac Flash adapter, (this is where I want to >> deploy >> the bootable Linux os) >> >> Target: >> Lippert PC104 CPU with CompacFlash socket integrated on board. The PC >> can >> boot from the compacflash. >> No floppy, no CD, but Ethernet interface >> >> If the image can be made bootable as hda on the compacflash, I am in >> business. >> >> Is there any way I can do this in Qplus ? >> >> Again, the idea is to generate the bootable compacflash as hda on the >> host >> system, then insert it in the PC104 system and boot it. >> >> I would appreciate your advice and suggestions and be happy to use your >> software if possible. > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Qplus-devel mailing list > Qpl...@li... > https://lists.sourceforge.net/lists/listinfo/qplus-devel > |
From: Terje U. <ter...@ge...> - 2004-01-19 16:22:34
|
>Hello, my name is Terje Utheim, I work with the University of Bergen in >Norway at the Institute og Geoscience. >My project is designing field recorders for recording earthquakes. We are >now looking for posibillities lowpower embedded Linux systems. >I read through your documentation for Qplus and found it intresting. >However I have a question before actually trying out your software: > >Our development configuration is: > >Host: >Standard desktop PC with Redhat 9.0 >PCMCIA interface with Compac Flash adapter, (this is where I want to deploy >the bootable Linux os) > >Target: >Lippert PC104 CPU with CompacFlash socket integrated on board. The PC can >boot from the compacflash. >No floppy, no CD, but Ethernet interface > >If the image can be made bootable as hda on the compacflash, I am in >business. > >Is there any way I can do this in Qplus ? > >Again, the idea is to generate the bootable compacflash as hda on the host >system, then insert it in the PC104 system and boot it. > >I would appreciate your advice and suggestions and be happy to use your >software if possible. |
From: Ron P. <ron...@gs...> - 2004-01-06 17:52:18
|
Jerry, That was it! I don't know how I missed that after going through the menus a thousand times but I did. My first attempt failed and the I realized that make probably didn't know anything had changed and didn't recompile. But when I did a build kernel -force that fixed everything. Thanks again! Ron At 08:58 1/5/2004 -0600, Jerry Epplin wrote: >Be sure to build the kernel with the correct processor type ("Pentium"). >As I recall, the default is PII or PIII. > >Jerry > >Ron Parise wrote: > >> >>I am trying to learn how to use qplus but have not had any success >>booting my target system. The devel system is a RedHat 8.0 system. >>The target is a generic 100MHz Pentium with 48MB memory, a video >>card, 3c509 network card, and floppy. >>The build seems to proceed cleanly. I am trying to deploy using an initrd >>as the root file system. Etherboot (5.2.2) boots (from a floppy), >>gets an ip address, and >>the qplusp.etherboot filename. It then transfers the file (or seems to). >> >>I get the following output on the video console and then the target system >>just dies. >> >><millions of dots deleted>.............................. >>........................................done >>mknbi-1.4.3/first32.c (GPL) >>Top of ramdisk is 0x03000000 >>Ramdisk at 0x02D4F000, size 0x002B1000 >> >>At this point it just stops forever. It doesn't execute the boot file and >>is just >>dead. >> >>Anyone have any ideas? I'm stumped. >> >>Ron >> >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: IBM Linux Tutorials. >>Become an expert in LINUX or just sharpen your skills. Sign up for IBM's >>Free Linux Tutorials. Learn everything from the bash shell to sys admin. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>_______________________________________________ >>Qplus-devel mailing list >>Qpl...@li... >>https://lists.sourceforge.net/lists/listinfo/qplus-devel > |
From: Jerry E. <je...@ep...> - 2004-01-05 14:58:38
|
Be sure to build the kernel with the correct processor type ("Pentium"). As I recall, the default is PII or PIII. Jerry Ron Parise wrote: > > I am trying to learn how to use qplus but have not had any success > booting my target system. The devel system is a RedHat 8.0 system. > The target is a generic 100MHz Pentium with 48MB memory, a video > card, 3c509 network card, and floppy. > The build seems to proceed cleanly. I am trying to deploy using an initrd > as the root file system. Etherboot (5.2.2) boots (from a floppy), > gets an ip address, and > the qplusp.etherboot filename. It then transfers the file (or seems to). > > I get the following output on the video console and then the target > system > just dies. > > <millions of dots deleted>.............................. > ........................................done > mknbi-1.4.3/first32.c (GPL) > Top of ramdisk is 0x03000000 > Ramdisk at 0x02D4F000, size 0x002B1000 > > At this point it just stops forever. It doesn't execute the boot file > and is just > dead. > > Anyone have any ideas? I'm stumped. > > Ron > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Qplus-devel mailing list > Qpl...@li... > https://lists.sourceforge.net/lists/listinfo/qplus-devel > |
From: Ron P. <ron...@gs...> - 2004-01-05 03:50:10
|
I am trying to learn how to use qplus but have not had any success booting my target system. The devel system is a RedHat 8.0 system. The target is a generic 100MHz Pentium with 48MB memory, a video card, 3c509 network card, and floppy. The build seems to proceed cleanly. I am trying to deploy using an initrd as the root file system. Etherboot (5.2.2) boots (from a floppy), gets an ip address, and the qplusp.etherboot filename. It then transfers the file (or seems to). I get the following output on the video console and then the target system just dies. <millions of dots deleted>.............................. ........................................done mknbi-1.4.3/first32.c (GPL) Top of ramdisk is 0x03000000 Ramdisk at 0x02D4F000, size 0x002B1000 At this point it just stops forever. It doesn't execute the boot file and is just dead. Anyone have any ideas? I'm stumped. Ron |
From: Ed C. <ed....@gs...> - 2003-12-22 21:24:50
|
I had the same problem with Red 8.0 too. Here's a partial solution: In the toolchain directory (/opt/q+esto/tc/bin) find and edit the file "tb". Search for the line beginning with "class DepViewWindow(". Just under that, change the line "<font size=1>" to "<font size=2>" This will allow the heading and the dependency text to show, but the links will still have little boxes instead of characters. You have to click on the link and see where it takes you to find out what it is. Not a great solution, but better than nothing... @(^.^)@ Ed Hanoi Santos Hung wrote: > > Hello : > I'm new using QPlus. I'm install qplus and upgrades over a RedHat 8.0 > system but I can't see the information that qplus shows in > 'Dependencies' tab , I think that is a problem with a font but I dont > know which font is. > |
From: Hanoi S. H. <ha...@ic...> - 2003-12-22 18:28:01
|
Hello : I'm new using QPlus. I'm install qplus and upgrades over a RedHat 8.0 system but I can't see the information that qplus shows in 'Dependencies' tab , I think that is a problem with a font but I dont know which font is. Best Regards Hanoi Santos Hung Linux User 296804 |
From: Ed C. <ed...@ch...> - 2003-12-04 05:38:49
|
When I was attempting to add the package wu-ftpd-2.6.2-8.src.rpm into QPlus, I received a startup error: "Unable to find package wu" Apparently something is parsing the package name up to the first dash only. No amount of renaming files or changing the %package line in the .qpd file would get past this. There was always some sort of mismatch between the package name and what QPlus thought the package name should be. I need to be able to incorporate this srpm into the embedded system I'm building. Can anybody help? @(^.^)@ Ed Criscuolo |
From: Trilok S. <tri...@ya...> - 2003-08-27 12:28:37
|
Test for Mailing List Please ignore this message. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |
From: Yun Hee-C. <gan...@sp...> - 2003-08-05 01:06:37
|
Forget about this.. -- Heechul. Yun HTTP://sparcs.kaist.ac.kr/~gangster Dorm: +82-042-879-2095 Pager: 015-435-9413 Addr: Dorm 1405(East), KAIST, Taejeon, Korea (ZIP:305-701) |
From: SourceForge.net P. <pos...@so...> - 2003-08-01 00:57:42
|
This is a test message being sent to you by the SourceForge.net Operations staff to test reported problems with email routing. There is no need to reply to this message, as we are able to extract all the information that we need from our logs. Thank you, Postmaster -- SourceForge.net Operations |
From: Trilok S. <tri...@ya...> - 2003-07-22 04:47:56
|
Qplus P Improvments. 1. GUI Part. - Provide shortcuts in Menu. e.g. Alt+F will opens drop-down File menu. - Provide icon in toolbar to open new project wizard. e.g. similar to opening new document in word-processor. - Provide HTML Help shortcut in Help Menu. - Provide Context Sensitive Help. e.g. We can drag question-mark icon to the place/object/control for which we want to see help. 2. Port to Windows. - After looking at configuration tool of eCos. I came to suggestion that why don't we try to port Target Builder to Windows NT/2K/XP. - As application developed with wxWindows can be ported to windows platform. Simlarly for python. - Would you like to start this? As I have approached to one developer about similar development. If you give us green signal, then it will have great experience for us. 3. Setup CVS Tree. So that other can check-out code easily. Regards, Trilok Soni Sr. Software Engg. tri...@te... Tectona SoftSolutions(p) Ltd. http://www.tectonas.com __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |
From: ??? <hc...@et...> - 2003-05-09 02:13:54
|
Documents are written in english. However due to some font mismatching problem, some people can't see characters. Therefore there's html version of documents and you will have no problem with that. If you still want to see pdf version of document, you only need to install korean font pack for acrobat. As for python book I only read online python documentations. If you have any problems, please use mailling list, so people other than me can help you. Regard Heechul. ----- Original Message ----- From: "SERGIO_WAP" <SER...@te...> To: <hc...@et...> Sent: Friday, May 09, 2003 12:39 AM Subject: --- QPLUS --- > Dear Sirs, > > We are an Spanish company, FULTECH SYSTEMS SL. We are making a project > and we think using QPLUS would be very useful for us. But we can not > open the manuals as in the web page sais they are only in Corean. We > have downloaded the QPLUS software (more than 500MB). > Could you please send us the English manual? Where do we download it? > > Regards, > Sergio > > PS: Is there any Phyton or Qplus book to help us to introduce to them? > Which one you recommend? > > > |
From: <lhr...@et...> - 2003-04-28 01:49:13
|
Hi, You can build 'spruce' package by attached files(qpd,srpm). I think that it has some bugs about Korean. So I modified repeat message definition in 'ko.po' file and mktemp funtion in print.c, main.c files Overwrite attached files to next directories. /opt/q+esto/packages/QPDS/arm/spruce.qpd /opt/q+esto/packages/SRPMS/spruce-0.6.0-0.src.rpm P.S I coudn't attach files in this mail because message body was too big: 558205 bytes but mailing list of qplus is a limit of 60 KB. I only sent to Jeffery. I'll add on next version of TB. Regards, Hongro Lee |
From: <lhr...@et...> - 2003-04-25 08:04:47
|
Hi, You can build 'spruce' package by attached files(qpd,srpm). I think that it has some bugs about Korean. So I modified repeat message definition in 'ko.po' file and mktemp funtion in print.c, main.c files Overwrite attached files to next directories. /opt/q+esto/packages/QPDS/arm/spruce.qpd /opt/q+esto/packages/SRPMS/spruce-0.6.0-0.src.rpm P.S I didn't attach files in this mail because message body was too big: 558205 bytes but mailing list of qplus is a limit of 60 KB I only sent to Jeffery. I'll add on next version of TB. Regards, Hongro Lee ---------------------------------------------------------------------------- ---- Dear all When I compiling the spruce (BSP template is S3C2400), my building platform is RedHat 8.0 , I got the error message file=./`echo ko | sed 's,.*/,,'`.gmo \ && rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file ko.po ko.po:666: repeat message definition ko.po:162: ...this is first location of definition /usr/bin/msgfmt: found a 1 serious error make[2]: *** [ko.gmo] Error 1 make[2]: Leaving directory `/root/S3c2400/build/BUILD/spruce-0.6.0/po' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/S3c2400/build/BUILD/spruce-0.6.0' make: *** [all-recursive-am] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.16540 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.16540 (%build) exceptions.SystemExit result arrived... (thread exited..) result arrived... (thread exited..) Jeffery ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Qplus-devel mailing list Qpl...@li... https://lists.sourceforge.net/lists/listinfo/qplus-devel |
From: <hc...@et...> - 2003-04-24 16:22:03
|
Ok. I'll prepare space for you. But I'll not be in my office this week, so I'll tell you about it next week. Heechul |
From: Trilok S. <tri...@ya...> - 2003-04-24 10:58:15
|
Hi, I am unable to manage ftp server at my place. Can you give other links where I can upload my 50 MB stuff for QP-BSP-ARM-CDB89712. Otherwise give me sites where I can upload this open source bsp. Regards, Trilok Soni. __________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com |
From: <lhr...@et...> - 2003-04-17 10:55:58
|
Hi, I can see many bug reports about the package. So I have compiled those here. I also have those errors and think I have to analyze these. And I hope others who is capable of this I suggest get rid those bugs. Don't you want to be a packager of theTarger Builder? And please notify me. Regards Hongro Lee |