Alright I will try to figure this out over the weekend
> On Oct 11, 2019, at 22:42, Ryan Schmidt wrote:
>
>
>
>> On Oct 11, 2019, at 21:39, Steven Esser wrote:
>>
>> The bsdtar command seems to work fine outside of the scripts. This is a
>> fresh installation of Catalina and MacPorts, so th
On Oct 11, 2019, at 21:39, Steven Esser wrote:
> The bsdtar command seems to work fine outside of the scripts. This is a fresh
> installation of Catalina and MacPorts, so there are extraneous installs of
> bsdtar or libarchive etc
I assume you are the only person experiencing this problem, s
On Oct 10, 2019, at 22:58, Andrew Hartung wrote:
> What does this mean?
>
> Warning: All compilers are either blacklisted or unavailable; defaulting to
> first fallback option
>
> 10.14.6 with xcode 10.
>
> Showed up after the latest port update I ran after here:
>
> Adding subport libomp-
The bsdtar command seems to work fine outside of the scripts. This is a fresh
installation of Catalina and MacPorts, so there are extraneous installs of
bsdtar or libarchive etc
The custom prefix is just personal preference; The Catalina binaries aren’t
being built yet so I am in the same situa
On Oct 11, 2019, at 09:57, Joshua Root wrote:
> Xcode itself only contains a 10.15 SDK, but the Command Line Tools have
> a 10.14 one. You should be mostly fine with them installed, though there
> are some exceptions. Our installation instructions have always said to
> install both Xcode and the C
On Oct 11, 2019, at 10:49, Steven Esser wrote:
> On a fresh Catalina (10.15) install with Xcode 11.1 and the latest CLI tools
> I cannot seem to activate any ports. Most seem to configure and build
> correctly, but fail when they reach the activation step. Attached is the log
> for an attemp
[ Mes questions & réponses sont dans le sens normal de lecture. ]
Le 11/10/2019, Daniel J. Luke a écrit :
| On Oct 11, 2019, at 11:14 AM, daniel Azuelos
wrote:
[...]
| > How may I find which package provoqued this install of "bsdtar"?
|
| % port provides /opt/local/bin/bsdtar
| /opt/local/bi
On Oct 11, 2019, at 11:14 AM, daniel Azuelos
wrote:
> I entered:
> type bsdtar
> to discover it is the one located in:
> /opt/local/bin/bsdtar
> recently installed in my MacPorts tree.
>
> How may I find which package provoqued this install of "bsdtar"?
% port provides /opt/local/bi
On a fresh Catalina (10.15) install with Xcode 11.1 and the latest CLI tools I
cannot seem to activate any ports. Most seem to configure and build correctly,
but fail when they reach the activation step. Attached is the log for an
attempted installation of ncurses that has this activation step f
This might explain what's happening:
sh-3.2$ file /Applications/MacPorts/Octave.app/Contents/MacOS/Octave
/Applications/MacPorts/Octave.app/Contents/MacOS/Octave: POSIX shell script
text executable, ASCII text
What would usually be the application executable is a shell script wrapper;
maybe tha
I asked the question because EtreCheck Pro reports
/Applications/MacPorts/Octave.app to be 32-bit. On the other hand, macOS System
Information > Software does not list octave at all, either as 32-bit or as
64-bit!
Command
port -v installed octave
does show archs='x86_64' but it was unclear to
Hello,
Recently I encountered a problem during:
port upgrade Wireshark3
a popur window appeared:
bsdtar cannot be opened because of a problem.
Nonetheless,
there wasn't any error in the text log,
and the complete build of Wireshark3 succeeded.
I entered:
type bsdtar
to d
Xcode itself only contains a 10.15 SDK, but the Command Line Tools have
a 10.14 one. You should be mostly fine with them installed, though there
are some exceptions. Our installation instructions have always said to
install both Xcode and the CLTs.
- Josh
Chris Jones wrote:
> yes, as it only has
yes, as it only has the 10.15 SDK, different to the 10.14 one Xcode 10
has, which the buildbots use.
On 11/10/2019 2:56 pm, Richard L. Hamilton wrote:
Is Xcode 11.1 still a bad idea on Mojave?
On Oct 11, 2019, at 09:40, Chris Jones wrote:
This is what I did supposingly but with xcode11
Is Xcode 11.1 still a bad idea on Mojave?
> On Oct 11, 2019, at 09:40, Chris Jones wrote:
>
>
>> This is what I did supposingly but with xcode11.0... but anyway, I will try
>> again with the new xcode.
>> I will maintain you informed... it happened to other people in the office so
>> if I sol
This is what I did supposingly but with xcode11.0... but anyway, I will
try again with the new xcode.
I will maintain you informed... it happened to other people in the
office so if I solve this many people will be happy ;o)
Once Xcode is updated to 11.1 please also run
xcode-select --i
On 11/10/2019 15:34 PM, Chris Jones wrote:
Hi,
Are you *really* sure you rebuilt *all* your ports natively for
Darwin19 (macOS10.15) ? Your output suggests not, i.e. from the first
part
> Driving: gfortran test.f90 -v -mmacosx-version-min=10.15.0
> -asm_macosx_version_min=10.15 -l gfortran -
On 11/10/2019 2:30 pm, Guillaume Houzeaux @ BSC wrote:
Ok Chris,
I'm installing xcode 11.1 from the app store. Should I go through the
migration steps again afterwards?
yes. See my previous mail I just sent. All your ports need to be
uninstalled, then rebuilt from source natively for Darw
Hi,
Are you *really* sure you rebuilt *all* your ports natively for Darwin19
(macOS10.15) ? Your output suggests not, i.e. from the first part
> Driving: gfortran test.f90 -v -mmacosx-version-min=10.15.0
> -asm_macosx_version_min=10.15 -l gfortran -shared-libgcc
> Using built-in specs.
> COLLE
Ok Chris,
I'm installing xcode 11.1 from the app store. Should I go through the
migration steps again afterwards?
Guillaume
On 11/10/2019 2:22 pm, Guillaume Houzeaux @ BSC wrote:
Chris,
On 11/10/2019 1:41 pm, Guillaume Houzeaux @ BSC wrote:
Chris, thanks a lot for your very quick answe
On 11/10/2019 2:22 pm, Guillaume Houzeaux @ BSC wrote:
Chris,
On 11/10/2019 1:41 pm, Guillaume Houzeaux @ BSC wrote:
Chris, thanks a lot for your very quick answer!
1. I followed the path for migration and reinstalled all packages. I
will try to do it once more to be sure.
2. Xcode vers
Chris,
On 11/10/2019 1:41 pm, Guillaume Houzeaux @ BSC wrote:
Chris, thanks a lot for your very quick answer!
1. I followed the path for migration and reinstalled all packages. I
will try to do it once more to be sure.
2. Xcode version: 11.0
Please update to 11.1. 11.0 indeed has a number
On 11/10/2019 1:41 pm, Guillaume Houzeaux @ BSC wrote:
Chris, thanks a lot for your very quick answer!
1. I followed the path for migration and reinstalled all packages. I
will try to do it once more to be sure.
2. Xcode version: 11.0
Please update to 11.1. 11.0 indeed has a number of iss
Chris, thanks a lot for your very quick answer!
1. I followed the path for migration and reinstalled all packages. I
will try to do it once more to be sure.
2. Xcode version: 11.0
3. My test program is minimum:
program test
print*,'a'
end program test
4. The output with -v option is:
Drivi
Hi,
Note, using the test application at
https://gist.github.com/certik/9755084
On my macOS 10.15 Xcode 11.1 machine here works just fine. See below.
I suspect your issue is the SDK path baked into the compiler you are
using does not match what is now available on your system. You should
chec
one more request.
please post the full output from compiling your test code with the -v
option.
cheers Chris
On 11/10/2019 12:59 pm, Chris Jones wrote:
can you please direct us to the exact test application code you are using ?
Also, can you confirm the exact Xcode version you are using
can you please direct us to the exact test application code you are using ?
Also, can you confirm the exact Xcode version you are using ?
Have you correctly followed the macports migration guide after updating
your OS ?
https://trac.macports.org/wiki/Migration
cheers Chris
On 11/10/2019 1
Hello,
I'm compiling with gfortran9 on catalina and get this error:
gfortran test.f90
ld: library not found for -lSystem
collect2: error: ld returned 1 exit status
Seems that it does not find the library libSystem. I changed all the
library paths in my bash_profile
to include /usr/lib but do
28 matches
Mail list logo
