Re: Identifying possible situations for interactivity
On 2018-09-03, at 3:54 AM, Jan Stary wrote: >> - after running `selfupdate`, MacPorts could ask the user if they >> next want to upgradeall their outdated ports. > > No. This insistence on the latest bugs is a disease. > I want the version I have, which I know to work, unless I have > a reason to update (such as a security problem or a feature I wanted). Heck yes. Even more: if I find that I've installed something that doesn't work, I want to go back to the older working version. I am looking at you, ffmpeg, reported multiple times. --- Entertaining minecraft videos http://YouTube.com/keybounce
re:ranlib: malformed objects on 10.6
> After upgrading ports on 10.6 (I probably didn't touch the machine since > about May this year) I ran into issue compiling software with clang-5.0 > against libc++: /usr/bin/ranlib: object: .libs/libfoo.a(libfoo_la-bar-file.o) malformed object (unknown load command 2) ar: internal ranlib command failed Starting with clang-3.9, I found the objects could no longer be handled by the default /usr/bin/* tools, and you had to force them to use the cctools versions in /opt/local/bin/* sometimes that was as easy as having cctools installed. sometimes you had to send in the correct AR or RANLIB in the environment. clang-3.7 generates objects that the default /usr/bin/* tools can handle, as did clang-3.8 I recall. Best, Ken
Re: ranlib: malformed objects on 10.6
Hi, I’ve seen similar in the past, and it normal results when the compiler used is too new for the toolkit you are using (for ar etc.) and is generating code the assembler cannot understand. Do you have cctools installed ? Try updating your build to use the toolkit that provides instead. Chris > On 3 Sep 2018, at 8:40 pm, Mojca Miklavec wrote: > > Hi, > > After upgrading ports on 10.6 (I probably didn't touch the machine > since about May this year) I ran into issue compiling software with > clang-5.0 against libc++: > > /usr/bin/ranlib: object: .libs/libfoo.a(libfoo_la-bar-file.o) > malformed object (unknown load command 2) > ar: internal ranlib command failed > > Does anyone have any ideas what to check for? > > Thank you, >Mojca smime.p7s Description: S/MIME cryptographic signature
ranlib: malformed objects on 10.6
Hi, After upgrading ports on 10.6 (I probably didn't touch the machine since about May this year) I ran into issue compiling software with clang-5.0 against libc++: /usr/bin/ranlib: object: .libs/libfoo.a(libfoo_la-bar-file.o) malformed object (unknown load command 2) ar: internal ranlib command failed Does anyone have any ideas what to check for? Thank you, Mojca
Re: Identifying possible situations for interactivity
On Sep 01 12:12:11, eg...@gwmail.gwu.edu wrote:
> So I was going thru my drafts folder and found this unsent message in
> it from a few years ago; much of it may no longer be relevant now that
> MacPorts has already added interactivity, but I figured I might as
> well send this anyways for the archives so what I wrote doesn't die
> stuck in my drafts.
The port system should be as NON-interactive as possible.
A user starts a bulk build of, say, all audio ports and walks away.
It would be quite unfortunate if he had to be there the whole time.
The exeptions should only be exceptional: when a port is removed,
everything that depends on it should also be removed, but that
probably requires the user's Yes.
> - after running `selfupdate`, MacPorts could ask the user if they
> next want to upgradeall their outdated ports.
No. This insistence on the latest bugs is a disease.
I want the version I have, which I know to work, unless I have
a reason to update (such as a security problem or a feature I wanted).
> - modifications to configuration files:
> {{{
> Configuration file `/sw64/etc/shells'
> ==> File on system created by you or by a script.
> ==> File also in package provided by package maintainer.
>What would you like to do about it ? Your options are:
> Y or I : install the package maintainer's version
> N or O : keep your currently-installed version
> D : show the differences between the versions
> Z : background this process to examine the situation
> The default action is to keep your current version.
> *** shells (Y/I/N/O/D/Z) [default=N]
> }}}
An install should never touch configs in /etc (let alone in $HOME),
except if creating a brand new one. Notify the user that a port contains
a config different from one that aready exists, or has installed a new one,
and leave it to the user to do the editing.
