| |
| |
| |
|
Comments:
<0> if i've got some c source code, how do i compile it? gcc -o endprogram source.c ?
<1> yes
<0> ok, thank you
<2> in functions like void __lockfunc lock_kernel(void) { ... } what does __lockfunc do to the method? or __init in the functions called by start_kernel() ?
<2> or just __whatever in general.. how does gcc interpret them?
<3> hi all
<3> i am able to compile programs for 64 bits if they are made for i386?
<3> or i can see somewhere ifthey are made for i386?
<3> hi ..where i can see if a source is made for i386 or x64?
<4> use file on the object file
<3> how?
<3> file foo.cc?
<3> yes ..but i need to know if the sourceis for i386 or for 64
<3> if it can be compiled for 64 better said
<4> not really sure I understand your question. You can't really see if you can compile a file for a given arch
<3> i cant?
<3> this i want to see:)
<4> int main(int argc, char *argv[]) { return 0; }
<4> what arch is this for ?
<3> for 64 i want it to be
<3> i think is made for i386
<3> because gcc foo.cc gives me i386 errors
<4> I guess I don't understand what you are saying. the code I just pasted works on all arches. I was making the point that the code cannot tell you what arch it runs on.
<3> ok i fyou have the time to listen
<3> i tell you again
<3> i have some gcc program that worked on i386
<3> but now it doesnt work for x64
<3> becasue i upgraded to x64
<3> so when i compile gcc foo.cc ggives me this errors
<3> a will paste bin in a moment
<3> thomas_, if you can see this http://code.bulix.org/5ffp49-9347
<3> so thomas_ if i change the code waht you said then i could compile it for x64?
<4> ALVAN: were is the actual code ? the error clearly says you're using a deprecated header
<3> ah the codee one moment :P
<3> thomas_, sorry fro the delay here is the code http://code.bulix.org/9uql96-9348
<4> apparently fstream.h is deprecated. try changing it to just fstream (without .h) and recompile
<4> this is completely unrelated to the architecture you're building on btw
<3> ok
<3> becasue i know that some C files work on many arhitectures
<3> sorry still didnt work ..
<3> thomas_, ?
<4> ALVAN: what is the error now ?
<3> cant find file fstream.h
<3> newquote.cc:6:21: error: fstream.h: No such file or directory
<4> ALVAN: you seem to be new to compiling
<4> ALVAN: I don't know g++ well, but a few hints
<3> i sorry g++ almost new
<4> a) the compiler gave you a pretty clear error message before saying that fstream.h is deprecated, and that you should check that specific chapter in the spec
<4> b) the new error is quite different, because apparently it's not just a matter of dropping the .h like for iostream
<4> c) google is your friend - see resources like http://members.aon.at/hstraub/linux/newscache/porting-howto.html
<4> but you need to *read* the messages from the compiler to figure out what's going on
<3> i now some errors in compiling but for depracated i always upgrade the gcc
<3> i dont know so well to modify and where to modify the code
<3> i must put #include <fstream> ?
<4> you must find out what it is you were using from the old fstream.h, and check what it is replaced with
<3> ok thanks
<3> and i must change the code to be suitable for 64 bit
<3> i try with -Wno-deprecated and still doesnt work
<3> can you adjust it for me ?
<3> if you have the time ?
<3> thomas_, ?
<4> "doesnt work" -> doesn't say anything. *read* the *compiler* *message*
<4> ALVAN: I don't use c++
<3> if you rember my paste bin ...now i have the error newquote.cc: In function void WriteQuote(char*, int, char*):
<3> end was not declared in this sco
<3> end was not declared in this scope
<4> so fix the source code. it's c++, I don't know c++
<3> me neither :)
<3> i better search a source code on goole for 64 bit
<3> it's better then streching my brains to fix the code
<3> is there a g++ channel?
<5> lo all, can i use gcj to produce elf binarys instead of ***embler?
<1> variant: it does so by default
<1> on platforms where elf is the default that is
<5> ah
<5> thanks
<5> thanks:)
<5> i was just reading about htat actualy
<1> or rather it always produces ***embler and gives that to ld to produce the executable (by default)
<1> unless you tell it explicitly not to do so
<5> i created a simple helloworld file but the binary is 17k.. is there any way to make it smaller?
<1> you can try to strip it
<1> (with the "strip" command)
<1> and optimize for size with -Os
<6> hello is it safe to use gcc 4.1.1? or any 4.x ?
<1> "safe"?
<6> i mean : would i end up with broken programs / kernel ?
<6> i wonder if it makes a good code because i saw some comments that it doesnt
<7> i've had problems compiling libsh with gcc 4.1. no such with 4.0, though.
<8> hello there
<8> i'm trying to recompile my kernel and i get this error after i run the "make" command :
<8> LD init/mounts.o
<8> ld: more than one '-m' parameter
<8> make[1]: *** [init/mounts.o] Error 1
<8> make: *** [init] Error 2
<8> can someone tell ho can i fix this ?
<8> make -v
<8> GNU Make 3.81
<8> gcc version 3.4.6
<8> q
<9> hi everyone.
<9> i am in the process of building an openmosix patched 2.4.26 on an amd64 host. this version of openmosix requires gcc 2.95. with no deb packages for this arch available, i am building gcc 2.95 from source. i had to p*** target=i386-pc-linux-gnu to configure, as there is apparently no x86_64 support in this version of gcc.
<9> does anyone see potential problems with this strategy?
Return to
#gcc
or
Go to some related
logs:
#osdev
recording internet radio illegal
Solaris Nevada qemu
#kde
ubuntu couldn't find package libx11-dev
debian unstable netinstall iso
installing xaralx on ubuntu
uninstall proftpd ubuntu
ssh -X xclock can't open display
scroll-wheel-sensitivity xmodmap
|
|