search

mistydemeo / tigerbrew

Experimental fork of homebrew for PPC Macs on Tiger
Other
537 stars 129 forks source link

New, strange warning after download/fetch #120

Closed chdiza closed 10 years ago

chdiza commented 11 years ago

brew fetch anything results in a dowload followed by a warning I've never seen before IIRC.

WARNING: can't open config file: /usr/local/etc/openssl/openssl.cnf

Well...huh. I do not now, nor have I ever in my life, had any openssl config files in /usr/local/etc. Yet, this warning is new.

I know the openssl formular was recently adjusted to force the config files to go in /usr/local/etc. Is Tigerbrew plumbing requiring that they be there?

BTW sorry for the typo action. TenFourFox on a G4 7450 does not play nicely with Github comment-boxes. 3 to 4second lagtime between hitting a key and seeing it in the box.

chdiza commented 11 years ago

I should add that I don't see the corresponding error in Hombrew over on Mountain Lion, even though I use the same custom openssl formula on each.

chdiza commented 11 years ago

Ack, I should also add that the strange error just reported is on Tiger PPC. I have not observed it on Leo PPC.

mistydemeo commented 11 years ago

Hmm. Did you upgrade git recently?

mistydemeo commented 11 years ago

Tigerbrew's git is built against tigerbrew's openssl on 10.4, and there may be an issue somewhere here.

chdiza commented 11 years ago

Hmm. Did you upgrade git recently?

Nope, not since shortly after whatever the current version is came out.

Tigerbrew's git is built against tigerbrew's openssl on 10.4, and there may be an issue somewhere here.

P'raps so. I comment out the depends_on 'openssl' in the git formula, because otherwise I am forced to brew openssl with the stock formula even if I already have brewed my custom one. But, I'm 90% sure that I also do this over on ML, Lion, and PPC Leo and the warnings don't appear there. I'll have to look into this.

chdiza commented 11 years ago

It appears this may have nothing to do with tigerbrew. Just a simple openssl version produces that warning.

OTOH this is just bizarre. I never saw that until recently, and I can see by looking at modification dates that I brewed openssl in April.

mistydemeo commented 10 years ago

Did you ever figure this one out?

chdiza commented 10 years ago

No, not really. I rebrewed openssl, but there was also a new git version shortly thereafter. Some combo of the two made it go away.