gcc compiler errors
 

Since upgrading to jaguar and installing the new developer cd gcc won't compile anything. I get the error:

Any ideas. I almost always run gcc from inside fink.

Thanks

...which is where you should compile gnome libs

Anyway if it is failing at the configure step you are going to have to post a little more information about what you are doing, what the error is, what it isn't finding, etc.

Fink installs some missing c headers in Jaguar too BTW.

But I don't think you got that far.

I had this issue a while back..

check the config.log file and you'll probly find that you need to ranlib on a few files..

just look in the log file for find the file names and the type:

ranlib <fullpath-to-file>/filename

Cheers,
---Zed :cool:

I just followed the update instructions on the fink site but the problem persists.

Zed: could you give me more detailed instructions on finding the config.log file and performing the ranlib.

thanks

Ed

The config.log file should be in the src dir of the package that you are installing..

you could just search for it using Finder..

once you've found it post the contents here and we should be able to help resolve it..

Cheers,

--Zed :cool:

OK heres and example for ncurses:



thanks

Ed

gsdali,

Several questions:

To update Fink to 10.2, did you followed this instructions? :

http://fink.sourceforge.net/news/jaguar.php

The version of gnome-libs you are trying to install is quite old, fink latest version is gnome-libs-1.4.2-1

Are you are trying to install it with Fink ?

If yes, can you post the last 15 lines of the compiling-log ? And, what's your 'fink -V' ?

July Developer Tools and August update installed?


Cheers...

have followed the fink 10.2 instructions. I've run selfupdate now

this is the last n lines of output:

fink -V

I've not installed those dev tools updates. Where on apple do they come from?

thanks

Ed

I seem to be having difficulties with my mac at the moment. It won't mount the dev tools images one gives a broken pipe error (32), the other claims the image is already mounted. I'm having other issues. with stuff at the moment. Wierd **** is happening and I'm not sure what to do.

thanks

Ed

gsdali,

1- Did you ran 'fink sefupdate' or 'fink selfupdate-cvs' ?

The July Developer Tools are the ones that came with OS X 10.2.

2- I think you missed the August Developer Tools update for 10.2.

"The August 2002 Mac OS X Developer Tools Update addresses issues with the July 2002 Mac OS X Developer Tools originally released with Mac OS X version 10.2"

Download them from ADC, after signing for free as a developer:

http://www.apple.com/developer/

Please, install the update and try again, 'fink selfupdate-cvs'

I just ran 'fink selfupdate-cvs' successfully and installing ncurses-5.2-9 got the following at the same place as yours:

Cheers...

I'm hoping that once I finally can install the dev tools updates it will all work fine. However I can't mount the disk images from apple. I keep getting this broken pipe error, -32.

any idea how to fix that, is it related to my inability to create a new keychain.

thanks

Ed

gsdali,

Maybe, make a 'google' search with the broken pipe error, -32 in MacOS X.

Are you on a modem connection?

Cheers...

no, ADSL.


thanks

Ed

I can't dig anything up on apple's knowledge base or on the web. I've filed a bug report with apple just it case.

gsdali,

Are you sure before you installed the Jaguar (July) Developer tools, the ones that came with 10.2?

Maybe they didn't install properly?

What says 'gcc -v' ?


Cheers...

gsdali,

I asked Martin Costabel, one of the Fink Developers about your problem. This is what he wrote back:

-----------------------
Sorry, I don't think I can help; I have never seen such a thing.
What I would check is the permissions for /tmp/ and for /var/tmp/, they should be writable for everybody. It could also be useful to run the "Verify privileges" program from Disk Utility.

-----------------------


Cheers...

hmm, anyone else getting these?

$ grep bad /var/log/*.log
/var/log/mail.log:Nov 11 15:15:28 gunther sendmail[448]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
/var/log/mail.log:Nov 11 15:15:28 gunther sendmail[459]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
/var/log/mail.log:Nov 11 16:29:27 gunther sendmail[452]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
/var/log/mail.log:Nov 11 16:29:27 gunther sendmail[455]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
/var/log/mail.log:Nov 11 19:21:42 gunther sendmail[448]: NOQUEUE: SYSERR(root): fill_fd: before main() initmaps: fd 0 not open: Bad file descriptor
/var/log/mail.log:Nov 11 19:21:42 gunther sendmail[448]: NOQUEUE: SYSERR(root): fill_fd: before main() initmaps: fd 1 not open: Bad file descriptor
/var/log/mail.log:Nov 11 19:21:42 gunther sendmail[448]: NOQUEUE: SYSERR(root): fill_fd: before main() initmaps: fd 2 not open: Bad file descriptor
/var/log/mail.log:Nov 11 19:21:42 gunther sendmail[456]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
/var/log/mail.log:Nov 12 04:03:12 gunther sendmail[442]: NOQUEUE: SYSERR(root): fill_fd: before readcf: fd 0 not open: Bad file descriptor
/var/log/mail.log:Nov 12 04:03:12 gunther sendmail[442]: NOQUEUE: SYSERR(root): fill_fd: before readcf: fd 1 not open: Bad file descriptor
/var/log/mail.log:Nov 12 04:03:13 gunther sendmail[442]: NOQUEUE: SYSERR(root): fill_fd: before readcf: fd 2 not open: Bad file descriptor
/var/log/mail.log:Nov 12 04:03:14 gunther sendmail[471]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
/var/log/mail.log:Nov 12 04:10:57 gunther sendmail[434]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
/var/log/mail.log:Nov 12 04:10:58 gunther sendmail[445]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
/var/log/mail.log:Nov 12 12:28:47 gunther sendmail[437]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
/var/log/mail.log:Nov 12 12:28:48 gunther sendmail[440]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
/var/log/mail.log:Nov 14 11:40:38 gunther sendmail[455]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
/var/log/mail.log:Nov 14 11:40:38 gunther sendmail[458]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor

and on in the same way as mT. Theres loads more of this for Nov 15 aswell.

gsdali,

IMHO it looks somethings is really wrong system-wide.

And, I don't know what it is...

When you installed 10.2, did you made a clean install or 'archive and install'?

I'm walking blind here, probably the best person to dig what's wrong in your system, would be MervTormel.


Cheers...

https://connect.apple.com/

October 2002 Developer Tools Patch

This patch fixes a bug in the August 2002 Developer Tools Update. This patch reverts the nibtool to the version supplied in Mac OS X 10.2 Developer Tools (released July 2002).


October 2002 Developer Tools Patch

28 Oct 2002 MacBinary 66 K

Glanz,

According to gsdali, he never installed the August Developer Tools Update, as he couldn't mount the image.

He was still using the July (Jaguar) Tools.

Maybe, his problem is due to a corrupt installation of the July Tools from the CD.


Cheers...

Speaking of the Dev tools. In the ADC there is the July tools, an august update, and an update to the august update. But for some reason the July tools are listed between these two updates.

How necessary are they to apply?


v

vonleigh,

1-The "July" Tools are the original Jaguar Tools released by Apple with 10.2.

2-The "August" update deals with issues with the July 2002 Mac OS X Developer Tools.

3-The "October" update patch "only" fixes a bug in the August 2002 Developer Tools Update which reverts the nibtool to the July Developer Tools installation.

I recommend the installation of all of them.


Cheers...

That could very well be! That happened to me once. I simply did a reinstall. BTW...., I know this is nearly off topic, but maybe not as much as we may believe. I once had many compiling problems caused by priv being botched during an install of 10.2. So what I did was to use the "Repair Disk Permissions" option under "First Aid"... I didn't even bother with a "Verify Disk Permissions" run beforehand. That solved 80% of my compilation probs. Permissions are a bit different in Jag.

Right now I'm using a GNAT compiler for 10.2 called WAVEFRONT available at http://www.adapower.net/macos/compiler.html

for many things.