Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!spool.mu.edu!uunet!mcsun!ukc!icdoc!njw From: njw@doc.ic.ac.uk (N J Williams) Newsgroups: comp.sys.hp Subject: Problems with Motif/gcc/R4 Keywords: Motif, X11r4, gcc1.39 Message-ID: Date: 24 Jun 91 15:20:09 GMT Article-I.D.: swan.NJW.91Jun24162009 Distribution: comp Organization: Imperial College Mafia, Computing Division. Lines: 29 Nntp-Posting-Host: swan.doc.ic.ac.uk Since we've had our hp's, one of the first things we did was ditch all of the R3 stuff and install an r4 distribution of X. This all worked fine, but we've had difficulties with Motif - the applications give strange error messages about undefined keys, the system is slow (okay, slower than usual for motif :-) and often glitches on the display. Fed up with this, I pulled across the binaries from me10 of motif1.1 built against r4. Now every motif application I compile dies in the Initialize functions: when built 'normally', the application just blocks within malloc, and when built -lmalloc, it gives "Error: cannot perform calloc". This all happens during the first call. E.g. > app_shell = XtInitialize(NULL, "Flawed", NULL, 0, &argc, argv); wanders off through the X libraries until it hits ?alloc. I don't know where the bad interaction is occuring... we have R4 libs and client built from standard src. R4 server is the entity from me10. The application in the above example is built using gcc-1.39 (It's in ansi code so it needs gcc). I tried building a simpler application using cc, but that barfed for some reason I forget on the motif header files [sigh]. This is all on a hp9000/350 running hpux7.0 -- Nick Williams, Dept of Computing, Imperial College, London, UK.