From: Brett F. <fo...@uo...> - 2007-03-08 22:35:00
|
I'm having trouble making colinux again -- anybody know why this is coming up? The kernel compiles fine, and so do the module. For some reason COLINUX_TARGET_KERNEL_PATH is not set. I even set it myself (via export) and it claims it's undefined. Check cross compiler: Skip i686-pc-mingw32-gcc, i686-pc-mingw32-ld - already installed on /home/fosterb/colinux-devel/mingw32/bin Check libs: Skip w32api.h, libfltk.a, libwin32k.a - already installed on /home/fosterb/colinux-devel/mingw32/i686-pc-mingw32/lib log: /home/fosterb/colinux-devel/log/build-colinux-11122.log Making Kernel 2.6.17 Making Modules 2.6.17 Create md5sum make[1]: Entering directory `/home/fosterb/colinux-devel/colinux/src' python ../bin/make.py colinux Analyzing target tree... Target architecture not specified, defaulting to i386 COLINUX_TARGET_KERNEL_PATH not set. Please set this environment variable to the pathname of a coLinux-enabled kernel source tree, i.e, a Linux kernel tree that is patched with the patch file which is under the patch/ directory. make[1]: *** [colinux] Error 3 make[1]: Leaving directory `/home/fosterb/colinux-devel/colinux/src' make: *** [colinux] Error 2 fosterb@mirabella-laptop:~/colinux-devel/colinux$ |
From: Stefan F. \(BebboSoft\) <s.f...@be...> - 2007-03-09 07:56:45
|
Maybe you forgot to run ./configure ??=20 > -----Urspr=FCngliche Nachricht----- > Von: col...@li...=20 > [mailto:col...@li...] Im=20 > Auftrag von Brett Foster > Gesendet: Donnerstag, 8. M=E4rz 2007 23:35 > An: col...@li... > Betreff: [coLinux-devel] COLINUX_TARGET_KERNEL_PATH not set >=20 > I'm having trouble making colinux again -- anybody know why this is > coming up? The kernel compiles fine, and so do the module. For some > reason COLINUX_TARGET_KERNEL_PATH is not set. I even set it myself > (via export) and it claims it's undefined. >=20 > Check cross compiler: Skip i686-pc-mingw32-gcc, i686-pc-mingw32-ld > - already installed on /home/fosterb/colinux-devel/mingw32/bin > Check libs: Skip w32api.h, libfltk.a, libwin32k.a > - already installed on=20 > /home/fosterb/colinux-devel/mingw32/i686-pc-mingw32/lib > log: /home/fosterb/colinux-devel/log/build-colinux-11122.log > Making Kernel 2.6.17 > Making Modules 2.6.17 > Create md5sum > make[1]: Entering directory `/home/fosterb/colinux-devel/colinux/src' > python ../bin/make.py colinux > Analyzing target tree... > Target architecture not specified, defaulting to i386 >=20 > COLINUX_TARGET_KERNEL_PATH not set. Please set this=20 > environment variable to the > pathname of a coLinux-enabled kernel source tree, i.e, a=20 > Linux kernel tree that > is patched with the patch file which is under the patch/ directory. > make[1]: *** [colinux] Error 3 > make[1]: Leaving directory `/home/fosterb/colinux-devel/colinux/src' > make: *** [colinux] Error 2 > fosterb@mirabella-laptop:~/colinux-devel/colinux$ >=20 > -------------------------------------------------------------- > ----------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the=20 > chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge &CID=3DDEVDEV > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel >=20 |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-03-09 09:05:58
|
Brett Foster wrote: > I'm having trouble making colinux again -- anybody know why this is > coming up? The kernel compiles fine, and so do the module. For some > reason COLINUX_TARGET_KERNEL_PATH is not set. I even set it myself > (via export) and it claims it's undefined. > > Check cross compiler: Skip i686-pc-mingw32-gcc, i686-pc-mingw32-ld > - already installed on /home/fosterb/colinux-devel/mingw32/bin > Check libs: Skip w32api.h, libfltk.a, libwin32k.a > - already installed on /home/fosterb/colinux-devel/mingw32/i686-pc-mingw32/lib > log: /home/fosterb/colinux-devel/log/build-colinux-11122.log > Making Kernel 2.6.17 > Making Modules 2.6.17 > Create md5sum > make[1]: Entering directory `/home/fosterb/colinux-devel/colinux/src' > python ../bin/make.py colinux > Analyzing target tree... > Target architecture not specified, defaulting to i386 > > COLINUX_TARGET_KERNEL_PATH not set. Please set this environment variable to the > pathname of a coLinux-enabled kernel source tree, i.e, a Linux kernel tree that > is patched with the patch file which is under the patch/ directory. > make[1]: *** [colinux] Error 3 > make[1]: Leaving directory `/home/fosterb/colinux-devel/colinux/src' > make: *** [colinux] Error 2 > fosterb@mirabella-laptop:~/colinux-devel/colinux$ Please check the entries in bin/user-build.cfg Newer kernels (2.6.17) use not COLINUX_TARGET_KERNEL_PATH. Please don't set it external. This would irretate some scripts and force they to a wrong fallback. Kernel Build and source are splitted into COLINUX_TARGET_KERNEL_BUILD and COLINUX_TARGET_KERNEL_SOURCE. -- Henry |
From: Brett F. <fo...@uo...> - 2007-03-09 21:51:04
Attachments:
user-build.cfg
|
I tried to grab the latest from monotone, but there weren't any major recent changes. I reconfigured, and the problem still exists. My config file is attached. Configuring with: ./configure --gcc-guest-build On 3/9/07, Henry Nestler <Hen...@ar...> wrote: > Brett Foster wrote: > > I'm having trouble making colinux again -- anybody know why this is > > coming up? The kernel compiles fine, and so do the module. For some > > reason COLINUX_TARGET_KERNEL_PATH is not set. I even set it myself > > (via export) and it claims it's undefined. > > > > Check cross compiler: Skip i686-pc-mingw32-gcc, i686-pc-mingw32-ld > > - already installed on /home/fosterb/colinux-devel/mingw32/bin > > Check libs: Skip w32api.h, libfltk.a, libwin32k.a > > - already installed on /home/fosterb/colinux-devel/mingw32/i686-pc-mingw32/lib > > log: /home/fosterb/colinux-devel/log/build-colinux-11122.log > > Making Kernel 2.6.17 > > Making Modules 2.6.17 > > Create md5sum > > make[1]: Entering directory `/home/fosterb/colinux-devel/colinux/src' > > python ../bin/make.py colinux > > Analyzing target tree... > > Target architecture not specified, defaulting to i386 > > > > COLINUX_TARGET_KERNEL_PATH not set. Please set this environment variable to the > > pathname of a coLinux-enabled kernel source tree, i.e, a Linux kernel tree that > > is patched with the patch file which is under the patch/ directory. > > make[1]: *** [colinux] Error 3 > > make[1]: Leaving directory `/home/fosterb/colinux-devel/colinux/src' > > make: *** [colinux] Error 2 > > fosterb@mirabella-laptop:~/colinux-devel/colinux$ > > Please check the entries in bin/user-build.cfg > Newer kernels (2.6.17) use not COLINUX_TARGET_KERNEL_PATH. Please don't > set it external. This would irretate some scripts and force they to a > wrong fallback. > > Kernel Build and source are splitted into > COLINUX_TARGET_KERNEL_BUILD and COLINUX_TARGET_KERNEL_SOURCE. > > -- > Henry > |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-03-09 23:13:03
|
Brett Foster wrote: > I tried to grab the latest from monotone, but there weren't any major > recent changes. I reconfigured, and the problem still exists. My > config file is attached. > > Configuring with: > ./configure --gcc-guest-build What shell you are using? Please try /bin/bash or /bin/ash -- Henry |
From: Brett F. <fo...@uo...> - 2007-03-09 23:16:22
|
On 3/9/07, Henry Nestler <Hen...@ar...> wrote: > > What shell you are using? > Please try /bin/bash or /bin/ash Already using bash. > > -- > Henry > |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-03-10 00:00:08
|
Brett Foster wrote: > On 3/9/07, Henry Nestler <Hen...@ar...> wrote: >> >> What shell you are using? >> Please try /bin/bash or /bin/ash > > Already using bash. Ok. Next idea. Change into the directory .../colinux-devel/colinux/bin and run ./build-colinux.sh If that not does work: Please change title line of this script into "#!/bin/sh -v" or "#!/bin/sh -x" to see what is loosing the paths. Is /bin/sh a link to your bash? What version have Python? -- Henry |
From: Brett F. <fo...@uo...> - 2007-03-10 00:05:43
|
On 3/9/07, Henry Nestler <Hen...@ar...> wrote: > Brett Foster wrote: > > On 3/9/07, Henry Nestler <Hen...@ar...> wrote: > >> > >> What shell you are using? > >> Please try /bin/bash or /bin/ash > > > > Already using bash. > > Ok. Next idea. > > Change into the directory .../colinux-devel/colinux/bin > and run > ./build-colinux.sh Bingo. > > If that not does work: Please change title line of this script into > "#!/bin/sh -v" or "#!/bin/sh -x" > to see what is loosing the paths. > > Is /bin/sh a link to your bash? Interesting -- It links to dash rather than bash. > What version have Python? > > -- > Henry > |
From: Brett F. <fo...@uo...> - 2007-03-10 00:12:21
|
Ok! Just to conclude this thread (with some well placed keywords). If building colinux on Ubuntu (Edgy) one must have /bin/sh point to /bin/bash instead of /bin/dash. This made the running Make work as well. sudo mv /bin/sh /bin/sh.old sudo ln -s /bin/bash /bin/sh There we go! Thanks! Now it's time to get my hands dirty. Which documents would help me implement new device drivers under coLinux? I've done Linux device driver development a while back, but I'm interested in the boundary between linux and WinNT. On 3/9/07, Brett Foster <fo...@uo...> wrote: > On 3/9/07, Henry Nestler <Hen...@ar...> wrote: > > Brett Foster wrote: > > > On 3/9/07, Henry Nestler <Hen...@ar...> wrote: > > >> > > >> What shell you are using? > > >> Please try /bin/bash or /bin/ash > > > > > > Already using bash. > > > > Ok. Next idea. > > > > Change into the directory .../colinux-devel/colinux/bin > > and run > > ./build-colinux.sh > > Bingo. > > > > > If that not does work: Please change title line of this script into > > "#!/bin/sh -v" or "#!/bin/sh -x" > > to see what is loosing the paths. > > > > Is /bin/sh a link to your bash? > > Interesting -- It links to dash rather than bash. > > > What version have Python? > > > > -- > > Henry > > > |
From: Robert B. <ro...@ro...> - 2007-03-10 00:21:16
|
Brett Foster wrote: > If building colinux on Ubuntu (Edgy) one must have /bin/sh point to > /bin/bash instead of /bin/dash. This made the running Make work as > well. > > sudo mv /bin/sh /bin/sh.old > sudo ln -s /bin/bash /bin/sh Alternatively, change the make #! link to point to /bin/bash if you must use bash. I would be wary of changing system links for a single app, which is misbehaving by the sound of it. If it needs a bash shell instead of any sh compatible shell, it should ask for it, and not assume that the sh is bash. > There we go! Thanks! Now it's time to get my hands dirty. Which > documents would help me implement new device drivers under coLinux? > I've done Linux device driver development a while back, but I'm > interested in the boundary between linux and WinNT. > > On 3/9/07, Brett Foster <fo...@uo...> wrote: >> On 3/9/07, Henry Nestler <Hen...@ar...> wrote: >>> Brett Foster wrote: >>>> On 3/9/07, Henry Nestler <Hen...@ar...> wrote: >>>>> What shell you are using? >>>>> Please try /bin/bash or /bin/ash >>>> Already using bash. >>> Ok. Next idea. >>> >>> Change into the directory .../colinux-devel/colinux/bin >>> and run >>> ./build-colinux.sh >> Bingo. >> >>> If that not does work: Please change title line of this script into >>> "#!/bin/sh -v" or "#!/bin/sh -x" >>> to see what is loosing the paths. >>> >>> Is /bin/sh a link to your bash? >> Interesting -- It links to dash rather than bash. >> >>> What version have Python? >>> >>> -- >>> Henry >>> |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-03-12 21:46:58
Attachments:
dash-complicant.patch
|
Robert Bridge wrote: > Brett Foster wrote: >> If building colinux on Ubuntu (Edgy) one must have /bin/sh point to >> /bin/bash instead of /bin/dash. This made the running Make work as >> well. >> >> sudo mv /bin/sh /bin/sh.old >> sudo ln -s /bin/bash /bin/sh > > Alternatively, change the make #! link to point to /bin/bash if you must The #! is ignored for sourced scripts. > use bash. I would be wary of changing system links for a single app, > which is misbehaving by the sound of it. If it needs a bash shell > instead of any sh compatible shell, it should ask for it, and not assume > that the sh is bash. Mostly of bash specials I found and changed in the patch. But why dash don't accept parameters for a sourced script? Have a sript "foo.sh": #!/bin/bash echo "first arg is $1" Than run: dash -c ". ./foo.sh hello" This shows an empty $1. Shure, I can make foo.sh executable and run ./foo.sh hello But this is not, what I need. I can not use subshell to set environment variables for current shell. Currently the ". bin/build-common.sh --package" is not working with dash. The other problem: I can not build gcc from source with dash as /bin/sh. The configure from gcc creates a wrong Makefile with "@foo_bar@" and "@if..." in the Makefile. How can set MAKE to use /bin/bash and not /bin/sh for such example? PREFIX := $(shell . bin/user-build.cfg; echo $$PREFIX) -- Henry ... dash is ugly :-( |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-03-10 00:29:43
|
Brett Foster wrote: > Which > documents would help me implement new device drivers under coLinux? > I've done Linux device driver development a while back, but I'm > interested in the boundary between linux and WinNT. Look into the serial device. It starts in the kernel as linux-2.6.17-source/drivers/char/cocd.c The NT side is src/colinux/os/winnt/user/coserial-daemon/main.c The Linux-as-host is src/colinux/os/linux/user/coserial-daemon/main.c This is the shortest and closest device with only one source file per OS. -- Henry |
From: Stefan F. \(BebboSoft\) <s.f...@be...> - 2007-03-10 08:55:27
|
Fyi: I just started to play around with snd-colinux =3D a sound driver = for linux, but I am not a registered coLinux developer. I defined the new device in the header and made a skeleton sound driver = (based on snd-dummy) wich compiles, loads, unloads. Now I am trying to use co_send_message to pipe the data to windows. Next step is to create the = dameon which recieves the data and plays it via directX. Bebbo =20 > -----Urspr=FCngliche Nachricht----- > Von: col...@li...=20 > [mailto:col...@li...] Im=20 > Auftrag von Henry Nestler > Gesendet: Samstag, 10. M=E4rz 2007 01:30 > An: Brett Foster > Cc: col...@li... > Betreff: Re: [coLinux-devel] COLINUX_TARGET_KERNEL_PATH not set >=20 > Brett Foster wrote: > > Which > > documents would help me implement new device drivers under coLinux? > > I've done Linux device driver development a while back, but I'm > > interested in the boundary between linux and WinNT. >=20 > Look into the serial device. >=20 > It starts in the kernel as linux-2.6.17-source/drivers/char/cocd.c > The NT side is src/colinux/os/winnt/user/coserial-daemon/main.c > The Linux-as-host is src/colinux/os/linux/user/coserial-daemon/main.c >=20 > This is the shortest and closest device with only one source=20 > file per OS. >=20 > --=20 > Henry >=20 > -------------------------------------------------------------- > ----------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the=20 > chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge > &CID=3DDEVDEV > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel >=20 |
From: George P B. <geo...@gm...> - 2007-03-10 21:24:03
|
Stefan Franke (BebboSoft) wrote: > Fyi: I just started to play around with snd-colinux = a sound driver for linux, > but I am not a registered coLinux developer. > > I defined the new device in the header and made a skeleton sound driver (based > on snd-dummy) wich compiles, loads, unloads. Now I am trying to use > co_send_message to pipe the data to windows. Next step is to create the dameon > which recieves the data and plays it via directX. > Sounds interesting. We'd be very interested in the patches to the kernel. Alternatively, it would be nice to not require coLinux on Windows to depend on DirectX, if there is another way to do sounds, that would be preferred. Probably except the solution anyways, as sound would be optional, and as long as the sound-daemon is the only thing dependent on DirectX George |