search for: rs6000

Hi, i am trying to compile llvm in a 64 Bit PowerPC machine with Yellowdog Linux 6.1 operating system. I could compile llvm but when I was trying to compile the llvm-gcc4.2 front end the compilation aborted with following error message: ../../gcc/config/rs6000/rs6000.c: In function ‘rs6000_override_options’: ../../gcc/config/rs6000/rs6000.c:1510: error: ‘MASK_MACHO_DYNAMIC_NO_PIC’ undeclared (first use in this function) ../../gcc/config/rs6000/rs6000.c:1510: error: (Each undeclared identifier is reported only once ../../gcc/config/rs6000/rs6000.c:1510: e...

...lve my problem. In addition, configure is failing on aix325 and SunOS 4.1.4. Are they still supported? Here is the output from AIX 3.2.5 (SunOS gives the same): disrael@ilx395> setenv CC /bin/cc disrael@ilx395> ./configure configure: Configuring rsync 2.5.5 checking build system type... rs6000-ibm-aix3.2.5 checking host system type... rs6000-ibm-aix3.2.5 checking target system type... rs6000-ibm-aix3.2.5 checking for gcc... /bin/cc checking for C compiler default output... cat: cannot open conftest.c configure: error: C compiler cannot create executables Da...

Duncan, et al., I am interested in getting dragonegg to work on PowerPC. Obviously the stuff in src/x86 needs to be replaced/replicated for PowerPC, but if you have a few minutes, can you provide your thoughts on what has to be changed between x86 and PPC. Thanks in advance, Hal -- Hal Finkel Postdoctoral Appointee Leadership Computing Facility Argonne National Laboratory

...d in getting dragonegg to work on PowerPC. Obviously the > stuff in src/x86 needs to be replaced/replicated for PowerPC, but if you > have a few minutes, can you provide your thoughts on what has to be > changed between x86 and PPC. you should probably start by doing this: copy gcc/config/rs6000/llvm-rs6000.cpp to (in the dragonegg source) src/ppc/Target.cpp. Extract the LLVM bits of rs6000.h into include/ppc/dragonegg/Target.h. Be inspired by the corresponding x86 Target.cpp and Target.h. Try to compile. Ciao, Duncan.

Hello, I'm trying to configure samba on AIX / RS6000. I have the smbd part of it running well . The nmbd part is giving us problems. Nmbd daemon dies as soon as started ! When I issue a 'ps -ef ' to see the processes, smbd runs but nmbd never. When using 'smbclient -L JAWS ' to debug the problem, I have the following output : U...

...ag_exceptions) \ + argvec.push_back("--enable-eh") + /* Once GDB has been enhanced to deal with functions without frame pointers, we can change this to allow for elimination of the frame pointer in leaf functions. */ [bwendling:llvm-eh] svn diff gcc/config/rs6000/rs6000.h Index: gcc/config/rs6000/rs6000.h =================================================================== --- gcc/config/rs6000/rs6000.h (revision 41554) +++ gcc/config/rs6000/rs6000.h (working copy) @@ -26,6 +26,8 @@ /* Definitions for the object file format. These are set at compile-ti...

Hi all, I have an APCC Back-UPS XS 1000 (it's a USB device) that I'm using with nut 2.0.2 that came with Fedora Core 4. It reports itself like this: Back-UPS RS 1000 FW:7.g8 .D USB FW:g8 in the nut web status page, which seems a tad messy. It otherwise works fine, except I don't get any information on the input and output voltages. I'm using the hidups driver. My

Are there anybody at all that use R on IBM RS 6000 machines running AIX? I would be happy to talk to you in that case. I have successfully (I think) managed to install R, however I cannot figure out how to `dyn.load' external C functions. Any help will be appreciated. Fredrik =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--- r-help mailing list -- Read

: I have an XP client running office XP. This is sitting on an network along with an IBM RS6000. The RS6000 has SAMBA installed and configured so that the XP client can see the RS6000 as though it is a network device. The user opens a template in Word 2002 which creates a mailmerge document using VBA. The VBA code gets the name of the document and the location for both the document and the da...

Hi, I've been searching through the R help archives and came across only one AIX compilation question in March, which received no public responses. I'm currently having the same problems with the "Illegal instruction" and core dump of running R 1.0.1 on AIX 4.3. Firstly, the R distribution was missing some FORTRAN routines, which I found on the net and added, by modifying

Hi, I've been searching through the R help archives and came across only one AIX compilation question in March, which received no public responses. I'm currently having the same problems with the "Illegal instruction" and core dump of running R 1.0.1 on AIX 4.3. Firstly, the R distribution was missing some FORTRAN routines, which I found on the net and added, by modifying

Hi. I'm running on a Windows 98 client and an RS6000 with Samba 2.0.7 (latest). I've used "net time \\ibrissde /SET /YES" to sync the times between the two systems ... but if I save a file onto the RS6000 through Samba on a mapped drive the file in UNIX is 1 hour old. I haven't been able to find any help on this so I'm assumi...

...about PowerPC specific constraints, you'll want to look here: http://gcc.gnu.org/onlinedocs/gcc-4.7.0/gcc/Machine-Constraints.html I'll note that the "s" in the %s0 means to only print the low 5 bits of operand 0. I think that may only be documented in the src: gcc/config/rs6000/rs6000.c:print_operand() Peter

I have just installed Samba for the following configuration: AIX 4.2, with NT clients We are trying to print from clients to unix printers through a Progress (database) program. On unix, I would identify my destination as "lp -s -dprinter1". Now, I indicate "//rs6000/printer1". People in our systems department (and therefore, people with "root" privileges) can print without any problem. However, regular users cannot. They get a message that basically says they don't have access to the following file //rs6000/printer1 (where printe...

Hello, I am not sure whether this is a clang issue, an LLVM issue, or both; but clang chokes when parsing expanded macros from the glibc /usr/include/bits/fenvinline.h with an error like: ./boost/math/tools/config.hpp:279:10: error: invalid input constraint 'i#*X' in asm feclearexcept(FE_ALL_EXCEPT); ^ /usr/include/bits/fenvinline.h:56:11: note: expanded from macro

Full_Name: Paul Gutwin Version: R-1.0.0 OS: AIX 4.2.1 Submission from: (NULL) (198.133.22.67) R-1.0.0 fails to compile. I'm using the config.cache file from a successful compliation of R-0.65.0 (prob #290, fixed thanks to Thomas Vogels @ CMU). Compiling R-1.0.0 fails with the following error messages: make Target "R" is up to date. gcc -I. -I../include -I../../src/include

...> > cyrille > Okay, I took a closer look at your output. I was correct in that gccas is attempting to assemble a native PPC assembly language file. However, this appears to be happening because the assembly file is generated by the GCC Makefiles for libgcc2 (in llvm-gcc/gcc/config/rs6000/t-ppccomm, I think). The first thing I would try is Marco's suggestion: add --disable-multilib to the configure command line and rebuild. Hopefully this will disable the generation of this assembly code. If that doesn't work, then you will need to comment out stuff in llvm-gcc/gcc/con...

...nflicts with default .cpp.o build rule in same makefile at line #889. Two alternatives are : 1) FInd a way to avoid executing $(out_cxx_object_file) rule for your target in such situation. OR 2) Set out_cxx_file for your target in config.gcc. You may be able to use llvm-i386.cpp or llvm-rs6000.cpp directly if your target is either x86 or powerpc. - Devang

On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote: > Cyrille Mescam wrote: > >Hi, > > > > > >When compiling the cfrontend for Linux/PPC architecture on a powermac > >G5, i got > >the following error : > > I hate to ask a silly question, but are you using "make bootstrap" to > build the cfrontend? Your output looks like gccas

.../Users/mmccrack/Documents/hpcl/LLVM/ll vm-gcc-4-2/libdeps/include -I../../trunk/gcc/../libdecnumber -I../libdecnumber -I/Users/mmccrack/Documents/hpcl/LLVM/llvm-svn/include -I/User s/mmccrack/Documents/hpcl/LLVM/llvm-svn-obj//include -m64 -fvisibility=hidden -DHIDE_EXPORTS -c ../../trunk/gcc/config/rs6000/ppc64-fp.c -o l ibgcc/ppc64/ppc64-fp.o In file included from ../../trunk/gcc/config/rs6000/ppc64-fp.c:35: ../../trunk/gcc/config/fp-bit.h:100: error: unable to emulate 'TF' So I think, why am I building ppc64? Taking a cue from the way to build 32-bit only for x86, I add --disable-mulitli...