Thread View: gnu.gcc.help
3 messages
3 total messages
Started by Rick Boarman
Thu, 17 Dec 1992 06:32
Help!
Author: Rick Boarman
Date: Thu, 17 Dec 1992 06:32
Date: Thu, 17 Dec 1992 06:32
40 lines
1900 bytes
1900 bytes
Help! I'm trying to install gcc on our machine (vax) here at work. The first make process went smoothly. I did get some operator overloading warnings but no errors. When I ran make stage1 it errored out: apple.com: make stage1 if [ -d stage1 ] ; then true ; else mkdir stage1 ; fi mv *.o insn-flags.h insn-config.h insn-codes.h insn-output.c insn-recog.c insn1 mv: insn-attrtab.c: Cannot access: No such file or directory mv: stamp-attrtab: Cannot access: No such file or directory mv: stamp-proto: Cannot access: No such file or directory mv: xgcc: Cannot access: No such file or directory mv: cc1: Cannot access: No such file or directory mv: gcc-cross: Cannot access: No such file or directory mv: cc1plus: Cannot access: No such file or directory mv: cc1obj: Cannot access: No such file or directory mv: enquire: Cannot access: No such file or directory mv: protoize: Cannot access: No such file or directory mv: unprotoize: Cannot access: No such file or directory mv: specs: Cannot access: No such file or directory mv: collect2: Cannot access: No such file or directory mv: ld: Cannot access: No such file or directory *** Exit 1 (ignored) rm -f stage1/libgcc.a cp libgcc.a stage1 cp: libgcc.a: No such file or directory *** Exit 1 (ignored) if [ -f /usr/bin/ranlib -o -f /bin/ranlib ] ; then ranlib stage1/libgcc.a; elsei ranlib: cannot open stage1/libgcc.a What went wrong or who should I talk to get some help? Anything you can suggest would be appriceated. Rick rickb@apple.com
Help!
Author: Richard Stallman
Date: Fri, 18 Dec 1992 20:09
Date: Fri, 18 Dec 1992 20:09
37 lines
2302 bytes
2302 bytes
Apple's look and feel lawsuit attacks the freedom of programmers generally. Today's suit has just two defendants, but indirectly it attacks all of us. You appear to work at Apple. Whether or not you personally support the lawsuit, to help you install GCC on a machine at your office (at Apple, it would seem) would be directly helping Apple business. I sometimes do favors for strangers, but not for strangers like Apple that are trying to hurt me. I hope other readers feel the same. I am sending this message because (1) perhaps you personally don't realize what a bad thing your employer is doing, and (2) perhaps some of the other readers don't realize either. Perhaps you personally don't approve of Apple's lawsuit. If so, you can show you really mean it by starting a political discussion of whether it is unethical and whether Apple is morally obligated to stop it. This requires some courage--management will order you to stop, and you will have to refuse on the grounds that everyone has a duty to consider an issue of conscience--but showing courage is what can demonstrate that people should not blame you for what Apple does. Those readers who think they are allowed to write programs and won't get sued for doing so, should read the information published by the LPF about the danger of monopolies in software. Then, if they'd like something to be done about the problem, they can join the LPF. The League for Programming Freedom is an organization that works to protect programmers' freedom to write software, opposing enforced monopolies such as Apple wants to create. The LPF is not a free software organization and is not related to the GNU project. More information about the LPF is available in the directory doc/lpf on ftp.uu.net. To contact the LPF, send mail to lpf@uunet.uu.net. You too can join the LPF; some Apple employees are already members.
Re: Help!
Author: Jim Lynch
Date: Sun, 20 Dec 1992 20:30
Date: Sun, 20 Dec 1992 20:30
40 lines
2611 bytes
2611 bytes
In article <9212190609.AA14495@mole.gnu.ai.mit.edu> rms@gnu.ai.mit.edu (Richard Stallman) writes: >Apple's look and feel lawsuit attacks the freedom of programmers >generally. Today's suit has just two defendants, but indirectly it >attacks all of us. > >You appear to work at Apple. Whether or not you personally support >the lawsuit, to help you install GCC on a machine at your office (at >Apple, it would seem) would be directly helping Apple business. I >sometimes do favors for strangers, but not for strangers like Apple >that are trying to hurt me. I hope other readers feel the same. > >I am sending this message because (1) perhaps you personally don't >realize what a bad thing your employer is doing, and (2) perhaps some >of the other readers don't realize either. > >Perhaps you personally don't approve of Apple's lawsuit. If so, you >can show you really mean it by starting a political discussion of >whether it is unethical and whether Apple is morally obligated to stop >it. This requires some courage--management will order you to stop, >and you will have to refuse on the grounds that everyone has a duty to >consider an issue of conscience--but showing courage is what can >demonstrate that people should not blame you for what Apple does. > > >Those readers who think they are allowed to write programs and won't >get sued for doing so, should read the information published by the >LPF about the danger of monopolies in software. Then, if they'd like >something to be done about the problem, they can join the LPF. > >The League for Programming Freedom is an organization that works to >protect programmers' freedom to write software, opposing enforced >monopolies such as Apple wants to create. The LPF is not a free >software organization and is not related to the GNU project. > >More information about the LPF is available in the directory doc/lpf >on ftp.uu.net. To contact the LPF, send mail to lpf@uunet.uu.net. > >You too can join the LPF; some Apple employees are already members. RMS should know that there IS renewed interest in gcc at Apple.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads