I cant print to screen :'(
Re:I cant print to screen :'(
Ok it looks good yet , but its normal if its making some time and configuring some time after executing make all install ???
Re:I cant print to screen :'(
binutils and GCC consist of several submodules, each with its own Makefile in its own subdirectory. The initial ./configure just does a couple of global settings, the final "make" then recursively calls the Makefiles in the subdirectories (which, in turn, run their own ./configure).
It's stupid, it's wasteful, it's potentially broken, but it's the way virtually all GNU tools do their build.
It's stupid, it's wasteful, it's potentially broken, but it's the way virtually all GNU tools do their build.
Every good solution is obvious once you've found it.
Re:I cant print to screen :'(
Thanks for your reply , but i have a problem when triying to do a make all-gcc install-gcc , here's the error message :
The GCC source package version i downloaded is 3.4.4 , my host compiler's version is also 3.4.4 , my binutils source package version is 2.16.1 and my host bintutils version is 2.16.91 .
So what's wrong ? should i choose versions inferior than my host versions ???
Thank you for any answer .
PS : why i am'nt getting notified ?
Code: Select all
make[2]: Entering directory `/usr/src/build-gcc/gcc/fixinc'
/bin/sh ../../../gcc-3.4.4/gcc/fixinc/genfixes machname.h
-uLe fichier sp?cifi? est introuvable.
make[2]: *** [machname.h] Error 1
make[2]: Leaving directory `/usr/src/build-gcc/gcc/fixinc'
make[1]: *** [fixinc.sh] Error 2
make[1]: Leaving directory `/usr/src/build-gcc/gcc'
make: *** [all-gcc] Error 2
So what's wrong ? should i choose versions inferior than my host versions ???
Thank you for any answer .
PS : why i am'nt getting notified ?
Re:I cant print to screen :'(
PS :
"Le fichier sp?cifi? est introuvable" means The specified file could not be found .
"Le fichier sp?cifi? est introuvable" means The specified file could not be found .
Re:I cant print to screen :'(
Ok i give up , i ill try to find a minimalist linux distribution with gcc , binutils , and bash ( or csh ... ) without other things that takes space and memory like openoffice , xfree ... .
I thinks now programming under windows is very hard , and on linux its very easy !
I thinks now programming under windows is very hard , and on linux its very easy !
Re:I cant print to screen :'(
It may be tempting to give up, but allowing some time for an answer to a question like this one usually yields a simple solution. Bear in mind that your last question was only posted just over 3 hours ago, repeat posting saying things such as "so can anyone help me?" achieves nothing. People have jobs and sleep and suchlike to attend to, and the chances of someone who can answer you being available within an hour or two is very low.
Patience is always a virtue
Patience is always a virtue
Re:I cant print to screen :'(
Well, to have any chance figuring out what went wrong, I'd have to run through a cross-compiler setup myself, writing all output to log, find out whether that file appears in my build too, and figuring out why your build runs differently from mine.
Right now I'm working under Linux, preparing v0.4.1 of PDCLib, answering a week's backlog of mail, and updating a Linux server which I administrate for a friend of mine.
Last time I tried the tutorial (less than a month ago), it worked flawlessly, like every time since I wrote it (some years ago). That's why I am not too eager to drop my current work and go hunting your problem. And if I would have stepped up and said, "just follow the tutorial closely and it will work", that wouldn't have motivated you very much, either, would it?
Desinstall your Cygwin, and try it all over again, sticking to the letter of the tutorial. It does work, trust me.
Right now I'm working under Linux, preparing v0.4.1 of PDCLib, answering a week's backlog of mail, and updating a Linux server which I administrate for a friend of mine.
Last time I tried the tutorial (less than a month ago), it worked flawlessly, like every time since I wrote it (some years ago). That's why I am not too eager to drop my current work and go hunting your problem. And if I would have stepped up and said, "just follow the tutorial closely and it will work", that wouldn't have motivated you very much, either, would it?
Desinstall your Cygwin, and try it all over again, sticking to the letter of the tutorial. It does work, trust me.
Every good solution is obvious once you've found it.
- Pype.Clicker
- Member
- Posts: 5964
- Joined: Wed Oct 18, 2006 2:31 am
- Location: In a galaxy, far, far away
- Contact:
Re:I cant print to screen :'(
any chance you forgot to tell the cross-compiler what machine it should support (which could explain the missing machstuff.h file).
Otherwise, i'd suspect something got wrong when you reinstalled X or Y. I'd try to get rid of any previous attempts, download fresh meat and redo things from start, step by step if i were you.
(well, actually not. If i were you, i'd grep makefiles for the missing files, run the build process again with make --debug or directly in strace to find out what's going on and where programs assumptions broke, but i guess you'll prefer a "redo-from-start" to that kind of mess )
Otherwise, i'd suspect something got wrong when you reinstalled X or Y. I'd try to get rid of any previous attempts, download fresh meat and redo things from start, step by step if i were you.
(well, actually not. If i were you, i'd grep makefiles for the missing files, run the build process again with make --debug or directly in strace to find out what's going on and where programs assumptions broke, but i guess you'll prefer a "redo-from-start" to that kind of mess )
Re:I cant print to screen :'(
Thanks all , and sorry for the UPs ( Can somebody help me? ) .
I did'nt know that all here dont have the same time offset ( mine is GMT 000 ) , probably the most are sleeping .
Ok , i ill try to uninstall cygwin and all its config files , then i let the setup.exe program choose the right versions .
I did'nt know that all here dont have the same time offset ( mine is GMT 000 ) , probably the most are sleeping .
Ok , i ill try to uninstall cygwin and all its config files , then i let the setup.exe program choose the right versions .
Re:I cant print to screen :'(
I have yet another error message :
Code: Select all
sed: -e expression #1, char 88: unterminated address regex
-uLe fichier sp?cifi? est introuvable.
make[1]: *** [s-macro_list] Error 1
make[1]: Leaving directory `/usr/src/build-gcc/gcc'
make: *** [all-gcc] Error 2
Re:I cant print to screen :'(
Here's the --debug error message :
Code: Select all
File `libgcc.a' does not exist.
File `stmp-int-hdrs' does not exist.
File `stmp-fixinc' does not exist.
File `macro_list' does not exist.
File `s-macro_list' does not exist.
Must remake target `s-macro_list'.
echo | /usr/src/build-gcc/gcc/xgcc -B/usr/src/build-gcc/gcc/ -B/usr/cross/i586-e
lf/bin/ -B/usr/cross/i586-elf/lib/ -isystem /usr/cross/i586-elf/include -isystem
/usr/cross/i586-elf/sys-include -E -dM - | \
sed -n 's/^#define \([^_][a-zA-Z0-9_]*\).*/\1/p ; \
s/^#define \(_[^_A-Z][a-zA-Z0-9_]*\).*/\1/p' | \
sort -u > tmp-macro_list
sed: -e expression #1, char 88: unterminated address regex
-uLe fichier sp?cifi? est introuvable.
make[1]: *** [s-macro_list] Error 1
make[1]: Leaving directory `/usr/src/build-gcc/gcc'
make: *** [all-gcc] Error 2
Re:I cant print to screen :'(
I've seen this problem! it happens when your windows paths occur before the cygwin ones.Lord_Coder wrote: ... | sort -u > tmp-macro_list
If you do a 'which sort', you'll probably see that the windows 'sort' is being used.
Reinstalling cygwin DOES fix this problem (this is why you listen to simple instructions), but the faster option is doing 'export PATH=/bin:/usr/bin' in the preparation section of the cross-compiler instructions.
Re:I cant print to screen :'(
Thanks very much .
My cygwin package is in english , and the only program that should produce a french message is one of window's programs .
My cygwin package is in english , and the only program that should produce a french message is one of window's programs .
Re:I cant print to screen :'(
Wow it works fine !
Thank you all !
I dont need a linker script with a rodata section , this command works fine :
Thank you all !
I dont need a linker script with a rodata section , this command works fine :
Code: Select all
ld --oformat binary -Ttext 1000 kernel.o -o kernel.bin