---> Building libgcc9
Error: Failed to build libgcc9: command execution failed
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc9/libgcc9/main.log
for details.
Error: Follow https://guide.macports.org/#project
Hi,
On 18/10/2019 7:00 am, Riccardo Mottola via macports-users wrote:
Hi,
when running upgrade of llvm 3.9, I get this message:
$ sudo port -v upgrade llvm-3.9
---> llvm-3.9 is replaced by llvm-8.0
is this correct? I think that for now the different clang versions would
"stay" and so corres
Hi,
Workaround is to either blacklist the compiler which has this option
turned on by default (which is what Chris replied) or in fact use a flag
to disable this. But disabling this flag is not needed for non-broken
compilers, so it's probably better to just blacklist the compiler, and
the la
> On 18 Oct 2019, at 11:30 pm, Michael Newman via macports-users
> wrote:
>
> I’m sorry, but I don’t understand most of what was written in this thread,
> but I do have a simple question:
>
> If I upgrade to Catalina (I already have Xcode 11.1) and install MacPorts for
> Catalina will ffmp
Hi,
Your ld command is incomplete. You aren't passing any of the runtime
libraries needed to link the .o file into an executable.
The simplest approach is to let gcc do the full job.
Titan ~/Documents/Code > cat test.f
program hello
print *, "Hello World!"
end program he
there, except
/usr/lib/libSystem.B.dylib.
Could that be the problem?
Hans
From: macports-users on behalf of Chris
Jones
Sent: Tuesday, October 22, 2019 7:09 PM
To: macports-users@lists.macports.org
Subject: Re: executing gcc9 on macOS 10.14
Hi,
Y
; sudo port -f uninstall ld64
> sudo port install ld64
Chris
On 23/10/2019 9:21 am, Chris Jones wrote:
Hi,
( Please always reply to the list )
The error below looks like one we addressed recently. Have you updated
your ports ? Please run
> sudo port sync
> sudo port upgrade out
use) set
export SDKROOT=`xcrun --show-sdk-path`
I actually had set the above in my shell profile, so I always have it,
which is why gfortran worked for me 'out the box' (and thus I forgot it
was there, which was my original intention)
Chris
On 22/10/2019 6:09 pm, Chris Jones w
4 @3_1+ld64_xcode (active)"
Any other suggestions?
Hans
From: macports-users on behalf of Chris
Jones
Sent: Wednesday, October 23, 2019 10:27 AM
To: macports-users@lists.macports.org
Subject: Re: executing gcc9 on macOS 10.14
Hi,
One other comment.
No problem, always glad to help someone use MacPorts !
On 23/10/2019 10:38 am, Hans Goedbloed wrote:
Thanks!, I now know what to expect and how to fix it.
Hans
From: macports-users on behalf of Chris
Jones
Sent: Wednesday, October 23, 2019 11:30 AM
Hi,
Please follow the procedure at
https://guide.macports.org/#project.tickets
first see if there is an open bug report, and if there is contribute to
that. Otherwise, open a new one.
cheers Chris
On 28/10/2019 10:51 am, Christoph Kukulies wrote:
I was trying to build FreeCAD under macport
Hi,
On 05/11/2019 12:28 pm, Hans Goedbloed wrote:
Hi Peter, Ryan and Chris
Thanks for your help.
Reply to Chris Jones:
-- I am not sure that I removed all ports, how can I find out?
-- How do I create an empty vanilla MacPorts installation?
By 'port -u uninstall'?
Foll
On 05/11/2019 12:28 pm, Hans Goedbloed wrote:
Hi Peter, Ryan and Chris
Thanks for your help.
Reply to Chris Jones:
-- I am not sure that I removed all ports, how can I find out?
-- How do I create an empty vanilla MacPorts installation?
By 'port -u uninstall'?
To Ryan Schm
Hi,
On 06/11/2019 8:34 am, Michael Newman via macports-users wrote:
I have no idea why I have postgreSQL:
MrMuscle:~ mnewman$ sudo port dependents postgresql84
postgresql84-server depends on postgresql84
MrMuscle:~ mnewman$ sudo port dependents postgresql84-server
postgresql84-server has no dep
> On 9 Nov 2019, at 1:39 am, Ryan Schmidt wrote:
>
>
>
>> On Nov 8, 2019, at 16:06, Michael Newman wrote:
>>
>>> On Nov 7, 2019, at 06:34, Ryan Schmidt wrote:
>>>
>>> If `port installed requested` shows things that you don't actually want,
>>> tell MacPorts by marking them as not request
> On 9 Nov 2019, at 1:50 pm, Henning Hraban Ramm wrote:
>
> Hi,
> I also had problems on Mojave, since at least cctools was expecting a
> MacOSX10.14.sdk in
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs;
> on Mojave there’s only the 10.15 SDK.
> I ha
Hi,
So what exactly have you run ?
Please run
sudo port install xorg-server
in a terminal, and if you still have problems post *exactly* what the
above gives.
Chris
On 27/11/2019 4:09 am, yiming roberts-lo wrote:
Hello,
I'm trying to figure out how to install Inkscape. I tried to follow t
'm assuming I should setup X11 as the default server?
Yes, just do exactly what it says...
>
> Thanks!
>
>> On Wed, Nov 27, 2019 at 4:55 AM Chris Jones wrote:
>> Hi,
>>
>> So what exactly have you run ?
>>
>> Please run
>>
>> sudo po
> On 28 Nov 2019, at 3:39 pm, Comer Duncan wrote:
>
> I've migrated to catalina and am having problem with building pango.
> I've attached an edited version of the main.log, as the whole file was
> deemed too big. Please take a look and let me know what you think.
> Thanks very much!
You c
Hi,
I would say the situation with 10.15 is now similar to other OSes. Some
things work, some things do not. There are also some clear cases of
things not working, and cannot/willnot be fixed, such as 32 bit support.
At the end of the day though only you know which ports you really care
abou
As with any OS upgrade, follow the instructions at
https://trac.macports.org/wiki/Migration
On 21/01/2020 1:28 am, Dave Horsfall wrote:
I don't have web access right now, hence the list...
My ancient Sierra MacBook failed (graphics board which is no longer
available) but I have been offered
OK. Done that. What does the error mean? I am in a local git branch at
the moment (not in master), is that the problem?
Yes. Just do what it says, define the remote branch to use. e.g.
git branch --set-upstream-to=origin/master minio-20200128
bash-3.2# port -v sync
---> Updating the port
Another question is why does clang depend explicitly on python 2.7, can
it not be updated to a newer 3.x version ?
On 05/02/2020 7:34 am, Vincent Habchi wrote:
Hi there,
everything is in the subject. Is there any reason for this dependency? I’m
trying to get rid of python 2.7, and the only
On 05/02/2020 7:34 am, Vincent Habchi wrote:
Hi there,
everything is in the subject. Is there any reason for this dependency? I’m
trying to get rid of python 2.7, and the only dependent port left so far is
clang 9.0, which is needed by qt5-qttools, but I can’t figure out why.
Isn't the an
o I think the python dep. can be removed for the majority of (not
ancient) systems.
cheers Chris
On 05/02/2020 11:07 am, Chris Jones wrote:
Another question is why does clang depend explicitly on python 2.7, can
it not be updated to a newer 3.x version ?
On 05/02/2020 7:34 am, Vincent Habc
Hi,
Indeed thanks, I had found my way to that link already ;)
I think has far as Macports goes, we can fix this by just removing the
python dep. entirely for darwin >= 11. Its only needed on the older OSes
where the system python is not new enough. I have the changes to do this
almost ready,
Hi,
On 05/02/2020 2:18 pm, Ken Cunningham wrote:
doing that doesn't really take us in the right directiion, though chris.
reproducible builds and all that.
we go from a fully spec'd proper python
Actually no. That is not what happens at the moment. Check the clang-9.0
config on darwin 11+
as seems to be the current
intention, or for all OSes, is really a separate question.
Chris
On 05/02/2020 2:33 pm, Chris Jones wrote:
Hi,
On 05/02/2020 2:18 pm, Ken Cunningham wrote:
doing that doesn't really take us in the right directiion, though chris.
reproducible builds and all th
before, with
or without MacPorts python being used. The MR really just removes the
python27 dep. when it is not actually used.
Chris
On 05/02/2020 2:40 pm, Chris Jones wrote:
Hi,
Just to try and be clear. The current inconsistency in the port files is
the fact the clang-X builds are configured
> On 3 Mar 2020, at 6:20 pm, dan d. wrote:
>
>
> Hello,
>
> I may in the near future install a newer os10 which skips some versions.
>
> How short of uninstalling the current macports can this be done?
You cannot. With Any major OS upgrade you must follow the migration
instructions, other
> On 15 Mar 2020, at 11:26 pm, Richard DeLaurell
> wrote:
>
>
> Hello,
>
> I am trying to update from ncurses 6.1 to 6.2, but am getting the warnings
> noted in ticket #60152; however, unlike the ticket report there my
> installation does not complete.
>
> The failure log reports: instal
> On 29 Apr 2020, at 1:45 am, Max Anglad wrote:
>
> I forgot to say that after Macports python38 installation, following the
> notes, I made :
>
>> sudo port select --set python3 python38
> Selecting 'python38' for 'python3' succeeded. 'python38' is now active.
>
> But however I think the P
> On 3 Jun 2020, at 9:10 pm, Ryan Schmidt wrote:
>
>
>
>> On Jun 3, 2020, at 05:38, Carlo Tambuatco wrote:
>>
>> I’m attempting to build emacs-27 from source and I would like to have AppKit
>> support for running natively on macOS and Gtk3 support.
>>
>> These are the gtk3 libraries I’ve
Hi,
Either install the newest available, 11.5, or just remove the CLT (its not
really needed).
https://developer.apple.com/library/archive/technotes/tn2339/_index.html#//apple_ref/doc/uid/DTS40014588-CH1-HOW_CAN_I_UNINSTALL_THE_COMMAND_LINE_TOOLS_
Chris
> On 1 Aug 2020, at 5:59 pm, Murray Eise
Have you tried doing what it asks ?
> On 9 Dec 2020, at 11:32 pm, Tom wrote:
>
>
> Hi,
>
> I get the following Error Message, although Xcode 12 and the CLI Tools are
> installed:
>
>>> Warning: The macOS 11.0 SDK does not appear to be installed. Ports may not
>>> build correctly.
>>> Warn
I tried it myself, and switching to --with-build-sysroot with gcc10 on big sur
does seem to build. I haven't had time to run any tests to see exactly what
this means w.r.t. the default sdk search paths. But in any case I think the
best advice is anyway to explicitly set it yourself, using one o
Have you checked to see if the ports you are trying to restore are available
for arm64 ? Its highly likely that either some are just not available at this
time, or if they are they might require different variants to that you
previously used. I am not surprised just blindly running the restore
It sounds like your builds are not correctly specifying the SDK gcc is to use.
There are a number of ways you can do this, either by pass it via a compiler
flag, by running the complication through xcrun, or by setting the SDKROOT
variables to the required path.
Cheers Chris
> On 7 Feb 2021,
ggc-min-expand=100 --param ggc-min-heapsize=131072
>>> Compiler executable checksum: 45101e0fe9cd9377caa0fee122dd387a
>>> In file included from
>>> /opt/local/include/gcc9/c++/ext/string_conversions.h:41,
>>> from /opt/local/include/gcc9/c+
Hi,
> On 7 Mar 2021, at 6:18 pm, Fielding, Eric J (US 329A) via macports-users
> wrote:
>
>
> I am getting this warning again from running ‘port upgrade outdated’:
>
> Warning: cltversion: The Command Line Tools are installed, but MacPorts
> cannot determine the version.
> Warning: cltvers
Hi,
Looks like at some point you did not follow the migration instructions
correctly. You should do so now.
Chris
> On 11 Mar 2021, at 2:41 pm, Christoph P.U. Kukulies wrote:
>
> Of course the error (OS platform mismatch) occurs on every command I'm
> running on port,
>
> like
>
> port inf
se errors messages.
Chris
>
> Jim
> 3222 NE 89th St
> Seattle, WA 98115
> (206) 430-0109
>
>> On Mar 11, 2021, at 6:44 AM, Chris Jones wrote:
>>
>> Hi,
>>
>> Looks like at some point you did not follow the migration instructions
>> correctly
Hi,
Gcc-devel provides gfortran for M1 machines by default.
Chris
> On 20 Mar 2021, at 1:01 pm, petr.2...@centrum.cz wrote:
>
> Is it already possible to install gfortran on M1?
> It seems that gcc-devel does not have +gfortran variant and and other gcc
> versions are not compatible.
> Thank
Hi,
Llvm/clang 10 does not work reliably on apple silicon. use llvm/clang 11
instead.
Chris
> On 30 Mar 2021, at 7:19 am, Sandeep Thakkar
> wrote:
>
>
> Hi,
>
> I'm installing llvm-10 on Apple M1 (macOS BigSur) with these changes in
> macports.conf:
>
> # custom changes
> buildfromsourc
Hi,
Whilst the statement that the devel version of gcc was correct at the time it
was made, gcc10 now has had support back ported. So I suggest you force
uninstall libgcc-devel and let libgcc10 get installed in its place.
Chris
> On 7 May 2021, at 12:37 pm, Andrew Rohl wrote:
>
> I have ins
Hi,
I would suggest maybe its worth pruning the gcc list a bit as well ? I believe
e.g. gcc7 at least works all the way down to 10.5, perhaps even older ? Do we
still need gcc 5, 6?
Chris
> On 7 May 2021, at 1:35 pm, Christopher Nielsen
> wrote:
>
> Folks,
>
> We’re considering retirement
Hi,
Another clean up suggestion is to remove all clangs apart from 11+ for
macOS11(arm). I just noticed the buildbots building the clang-9.0 version for
arm, but its worth noting that clang 9.0 and 10 are not reliable for arm, I
have seen them generate bad code, fail with ICEs, so really there
lang10 around for arm until we can migrate the
above to clang11.
Cheers Chris
>
> K
>
>
>
>> On May 7, 2021, at 12:22 PM, Chris Jones wrote:
>>
>> Hi,
>>
>> Another clean up suggestion is to remove all clangs apart from 11+ for
>> macOS11
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Please follow the instructions you were given above to either open a ticket or
see if one for this issue already exists.
> On 12 May 2021, at 8:25 pm, tom eee wrote:
>
> Error: Follow https://guide.macports.org/#projec
See `config.log' for more details
We need to see what is in this file… (from the messages you posted below).
Chris
> On 19 May 2021, at 3:06 pm, Bjarne D Mathiesen
> wrote:
>
> OK -
>
> on 10.6.8 I get :
>
> #=> ls -l /usr/bin/cc
> lrwxr-xr-x 1 root wheel 32 4 Jan 14:50 /usr/bin/cc ->
> On 10 Jun 2021, at 9:05 am, Giuseppe Di Matteo
> wrote:
>
> I opened ticket #63062.
> What about streamripper. Configure failed for libmad. (Big Sur arm64)
Same. Check for and if need be open tickets against failing ports.
>
> Pino Di Matteo
> pinodimat...@me.com
>
>
>
>> Le 9 juin 20
sudo port install xorg-server
Logout and back in again
> On 12 Sep 2021, at 11:17 am, Gerben Wierda via macports-users
> wrote:
>
> I’ve been trying out code::blocks and X11 installed via MacPorts and I’m
> under the impression something is missing.
>
> I installed using
>
> sudo port ins
The majority of ports will indeed build fine with just the CLT installed. There
are a number though where the build does indeed require a complete Xcode
installation, which is why the baseline recommendation is to install Xcode.
However if you are ok with perhaps running into the occasional por
> On 27 Sep 2021, at 10:36 pm, Ian Wadham wrote:
>
> Hello Chris,
>
>> On 27 Sep 2021, at 8:42 am, Chris Jones wrote:
>> The majority of ports will indeed build fine with just the CLT installed.
>
> So what is the “recipe” to install just the CLT with no ve
I have always favoured VMWare over parallels myself, and they now offer a free
license for non-commerical usages.
https://customerconnect.vmware.com/web/vmware/evalcenter?p=fusion-player-personal
> On 31 Oct 2021, at 12:07 pm, Richard L. Hamilton wrote:
>
> Years ago, creating a (then OS X,
> On 12 Nov 2021, at 6:59 pm, Tom wrote:
>
>
>>
>>> Hi,
>>>
>>> when trying to run an X11 program, I get the following error message:
>>>
>>> (putty:8198): Gtk-WARNING **: 00:06:49.190: cannot open display: :0
>>>
>>> How can I fix that?
>>
>> Assuming you are running Mac OS X 10.5 or
I am not aware of any use macports itself makes of spotlight, so for sure if
you don’t plan on using it yourself to search the install prefix, you can
disable it.
> On 16 Nov 2021, at 6:26 am, Richard L. Hamilton wrote:
>
> Seems it'd thrash Spotlight a lot less during "port selfupdate" or "
al is only 35GiB - and I
frequently remove most inactive ports and run a port clean installed)
and active in terms of changes.
On Nov 16, 2021, at 16:06, Chris Jones <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
I am not aware of any use macports itself makes of spotlight, so for
sur
Give the developers of rust itself a piece of your mind if you like,
over how slow it is to compile. Good luck with that - I suspect to be
THAT slow (although really? compiling a C compiler suite plus library
isn't exactly fast either) they might be doing some things by brute
force that they
and in the
latter case, those building themselves will also have the problem.
On Nov 29, 2021, at 09:15, Bill Cole
<mailto:macportsusers-20171...@billmail.scconsult.com>> wrote:
On 2021-11-29 at 08:32:46 UTC-0500 (Mon, 29 Nov 2021 13:32:46 +)
Chris Jones mailto:jon...@hep.phy.cam.ac.uk
Did you follow the migration guide when moving to a new major os version ?
https://trac.macports.org/wiki/Migration
If not, follow it now, to wipe out your ports and reinstall them correctly for
the new os.
If you did, your ports tree seems to be very out of date. Then try,
> sudo port selfup
the tip on migration, Chris!
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
>> On Thursday, December 9th, 2021 at 2:47 PM, Chris Jones
>> wrote:
>>
>>
>>
>> Did you follow the migration guide when moving to a new ma
Ports Migration Guide suggested a manual update (i.e. reinstall) which I
>>> believe got me going again. Thanks guys! ~SeaQuench
>>>
>>> ‐‐‐ Original Message ‐‐‐
>>>
>>>> On Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt
>>>&
u did
not pay enough attention to it in the first case ;)
Chris
>
> ‐‐‐ Original Message ‐‐‐
>
>> On Friday, December 10th, 2021 at 2:21 PM, Chris Jones
>> wrote:
>>
>> Hi,
>>
>> Yes, the error is expected. What i am asking is if you get any in
Nothing in macports will be installing to /usr/local. If you have anything in
that area it has been put there by some other means. Maybe homebrew?, but also
a number of third party installers sometimes use this directory as well (which
are the reasons why MacPorts specifically ignores this are
> On 3 Jan 2022, at 5:18 pm, Maxim Abalenkov wrote:
>
> Dear all,
>
> Thank you for all of your replies and suggestions! I have written my own
> matrix multiplication script in order to test NumPy’s performance. Please
> find it attached. I’m using the MKL variant of NumPy. Strangely enough
> On 3 Jan 2022, at 11:54 pm, Michael Newman via macports-users
> wrote:
>
> When I periodically update MacPorts I also run:
>
> sudo port -f uninstall inactive
Why are you using the -f option here. That could force something to happen that
might not be a good idea. Generally speaking you
In my opinion the best way to keep older hardware secure and useful past the
point the max macOS version they can run is long since obsolete, is to stop
using those OSes and install an alternative. There are, e.g. plenty of linux
distros out there and offer a modern, maintained, OS and run jus
> git pull --rebase --autostash origin master
works pretty much just fine 99.9% of the time.
cheers Chris
* Its actually what 'port sync' does under the hood, if you have
configured macports to work directly off a git checkout of the ports
tree, instead of the dfault rsync tarball
** the
On 07/03/2022 3:31 pm, Michele Venturi wrote:
I have the required libraries in /usr/lib/swift too,but MPV is looking
for them in /opt/local/lib,so it doesn't find them:
otool -l $(which mpv)
...
cmd LC_RPATH
cmdsize 32
path /opt/local/lib (offset 12)
Should we change RPATH or add symbolic l
ets from there.
On Mar 7, 2022, at 10:22 AM, Michele Venturi mailto:dard...@gmail.com>> wrote:
Should I submit a bug report before we even know if it's a
MacPorts specific issue? Or how do we find that out?
Il lun 7 mar 2022, 16:47 Chris Jones mailto:jon...@hep.p
On 11/03/2022 8:02 am, Michele Venturi wrote:
What is wrong is that a simple package manager
requires an entire multigigabyte professional IDE;
I have even taken the time to talk to them about it
and file a bug about it,but they clearly don't care...
It's surely not a new issue,it's like that
On 05/04/2022 11:33 am, Christoph Kukulies wrote:
I’m in the need of testing a libusb issue with an intermediate build of
libusb (1.0.26-rc1, that is)
Since I’m always reluctant of mixing brew and macports - is that
actually „dangerous“ or impossible at all, should that be avoided or can
i
On 05/04/2022 11:50 am, Christoph Kukulies wrote:
$ sudo port deactivate libusb @1.0.25_0
Password:
Note: It is not recommended to uninstall/deactivate a port that has
dependents as it breaks the dependents.
The following ports will break:
libusb-compat @0.1.7_0
openocd @0.11.0_0
usbut
without affecting the default X port.
If you want a different version than libusb-devel currently provides,
then you need to update the port to provide this.
Btw, what is the correspondent to
ldd
under macOS?
otool -L
—
Christoph
Am 05.04.2022 um 12:56 schrieb Chris Jones :
On
not new enough ?
Chris
>
> Do the pkgconfig .pc files play a role in the installation mechanism?
>
> —
> Christoph
>
>> Am 05.04.2022 um 15:36 schrieb Chris Jones :
>>
>>
>>> On 05/04/2022 1:54 pm, Christoph Kukulies wrote:
>>> Thanks. None
Hi,
Speaking only for myself, I generally suggest *not* using the
restore_ports.tcl script. When I migrate to a new OS I generate the list
of installed ports *and* requested ones, and follow the instructions as
far as wi[ping out my old ports prior to the update.
However, when restoring the
On 05/05/2022 4:51 pm, chilli.names...@gmail.com wrote:
I can't upgrade because of 404? Is this a problem on my end?
Most probably yes. Update built just fine here.
Check your local network / firewall.
---> Computing dependencies for curl-ca-bundle.
---> Fetching distfiles for curl-ca
The instructions given below are i think quite clear, just follow them…
> sudo port -f deactivate libunwind-headers
Then try again.
> On 7 Jul 2022, at 11:11 pm, Tao Zhang wrote:
>
> Hi,
>
>
> When I install wgrib2 into my Macbook pro (10.14.6), I get the following
> error.
> Does an
These are really questions not for macports, but for the maintainers of the
static libs, which I presume you downloaded in binary form from somewhere? The
first question is what platforms do the libs support ? 64 or 32 bit, etc…
Gfortran from macports works fine. This part is not your problem…
. I download those *.a from other platform, not from Mac.
> Gfortran works fine in my Mac if I do not call those *.a in a code.
>
> https://github.com/NOAA-EMC/NCEPLIBS does not mention which platform the
> libs support.
>
> Thanks
> Tao
>
>
>> On 7/7/22
build it by myself if Macport does not have these package.
> Thanks
> Tao
>
>> On 7/7/22 4:33 PM, Chris Jones wrote:
>>
>> Well, if those static libraries are not even built for macOS….. they are
>> never going to work on a mac.
>>
>> You need to either
Gcc12 brought a number of issues, that took time to be solved and
required a number of updates in other gcc versions as well, and only
became apparent as users submitted tickets etc. for those issues as they
where found. I apologies for the number of updates, but I think now,
touch wood, thi
> On 27 Jul 2022, at 7:29 pm, Hangglider wrote:
>
> Hello,
>
> somewhere in the dependencies for some package I have to compile
> libzzip. That's less easy than it sounds:
>
> The libzzip package seems to enforce gcc-4.2 (there's /usr/bin/gcc-4.0
> and /opt/local/bin/ppc-apple-darwin9-gcc-7
Btw. What the heck is ‘sorbet Leopard’ ??
> On 27 Jul 2022, at 7:29 pm, Hangglider wrote:
>
> Hello,
>
> somewhere in the dependencies for some package I have to compile
> libzzip. That's less easy than it sounds:
>
> The libzzip package seems to enforce gcc-4.2 (there's /usr/bin/gcc-4.0
>
> On 27 Jul 2022, at 7:54 pm, Chris Jones wrote:
>
>
>
>> On 27 Jul 2022, at 7:29 pm, Hangglider wrote:
>>
>> Hello,
>>
>> somewhere in the dependencies for some package I have to compile
>> libzzip. That's less easy than it sounds
On 27/07/2022 8:52 pm, Hangglider wrote:
MacOSX 10.5.9,
http://macintoshgarden.org/forum/introducing-sorbet-leopard-105-reinvigorated
http://macintoshgarden.org/apps/sorbet-leopard
So an unofficial OS. We don't really support those...
On 27.07.22 20:55, Chris Jones wrote:
Btw.
Yes, using it just fine for a short whole now…
> On 31 Jul 2022, at 10:09 am, Gerben Wierda via macports-users
> wrote:
>
> Has anyone been using Monterey 12.5 yet?
>
> Gerben Wierda (LinkedIn)
> R&A IT Strategy (main site)
> Book: Chess and the Art of Enterprise Architecture
> Book: Masterin
> On 31 Jul 2022, at 9:05 am, Gerben Wierda via macports-users
> wrote:
>
>
> gerben@hermione macports-ports % sudo port -v selfupdate
> ---> Updating MacPorts base sources using rsync
>
> Willkommen auf dem RSYNC-server auf ftp.fau.de.
> Nicht all unsere Mirror sind per rsync verfuegbar.
On 14/12/16 15:04, Guillaume Lapierre wrote:
Le 14/12/2016 à 15:40, Russell Jones a écrit :
Did you grab the .rmd160 file to go with the binary archive?
Yes.
The solution was to grab the distfile instead of the pre-built package
and use the -s switch on the command line to force building fr
Hi,
when you say 'breaks your setup' what exactly do you mean ?
Presumably the first machine, that creates the local binaries runs just
fine, but then the second doesn't use these for this one port, and
attempts to build again from source ? If correct, is this really a
problem ? From the disc
On 01/02/17 17:23, Barry Scott wrote:
On 1 Feb 2017, at 14:20, Bachsau mailto:w...@bachsau.name>> wrote:
Am 01.02.2017 um 07:38 schrieb Ryan Schmidt:
Sorry. Repeated modifications of the profile when the modifications
were already there was a bug. It looks like a fix was committed, so
hopef
Hi,
On 02/02/17 16:16, db wrote:
On 2 Feb 2017, at 16:34, Mojca Miklavec wrote:
If you only want to do it once, you can cd to the folder with the port
that you want to use and run "sudo port ..." from there.
Hmm…no, I thought I could mark the ports' default priority/availability,
something
Hi,
I guess the main message is
gdk-pixbuf2 must be installed with +x11.
You must have this port installed already without the x11 variant. Try
reinstalling with this option.
Chris
On 08/02/17 04:38, Dorien Herremans wrote:
Hello,
Thanks for all the replies.
I'm trying to install kde4-ba
Run
sudo port clean kde4-baseapps
And then try again.
> On 11 Feb 2017, at 8:34 am, Dorien Herremans
> wrote:
>
> Hi Ryan,
>
> Thanks.
>
> I've run:
> sudo port uninstall installed
>
> sudo port install kde4-baseapps
>
> and it end with the following error:
> Error: Requested variants
> On 11 Feb 2017, at 8:34 am, Dorien Herremans
> wrote:
>
> Hi Ryan,
>
> Thanks.
>
> I've run:
> sudo port uninstall installed
>
> sudo port install kde4-baseapps
>
> and it end with the following error:
> Error: Requested variants "+gtk+gtk3+x11" do not match those the build was
> st
On 23/02/17 14:38, Dave Horsfall wrote:
Let's say that I accidentally lost a critical Macports file (don't ask).
How would I recover it with Time Machine? It seems that my only options
are to recover an arbitrary file within my home directory, or to restore
the entire Mac, thereby making the w
On 23/02/17 17:51, Michael Parson wrote:
On Fri, 24 Feb 2017, Dave Horsfall wrote:
On Thu, 23 Feb 2017, Chris Jones wrote:
[...]
If not, then go to in terminal
/opt
assuming that is your macports prefix.
Run 'open .' which will start finder in that area, and then activate TM.
Hi,
You haven't really provided any useful information that anyone can use
to help. For instance the last line of the log you posted says
:debug:build "$procedure $targetname"
:error:build See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_por
Building statically is also a security nightmare.
If I have a dynamic libFoo.so, that a lot of other libraries and
applications dynamically link against, that is suddenly found to have a
major security bug, then once libFoo.so is updated I know everything
else using it is also fixed. If inste
201 - 300 of 390 matches
Mail list logo
