Re: stupid question
On Jun 29, 2018, at 10:21, pagani laurent wrote: > By the way, I tested the 3 other gcc-*-mp-7 (ranlib, ar, and nm) and all > complained : > >> gcc-ranlib-mp-7 > gcc-ranlib-mp-7: Cannot find plugin ‘liblto_plugin.so' > > Does it matter ? Looks like nobody has worked on that problem: https://trac.macports.org/ticket/38551
Re: stupid question
Thanks! I just forgot that sudo port select mp-gcc7 was not going to do what I expected and started to try several commands, getting mad… Laurent > Le 29 juin 2018 à 17:26, Chris Jones a écrit : > > > > On 29/06/18 16:21, pagani laurent via macports-users wrote: >> Hi, >> I have gcc7.0 installed : >>> sudo port installed gcc7 >> The following ports are currently installed: >> gcc7 @7.3.0_0 (active) >> but I can’t use it under that name. There are several gcc-* files in the /bin >> I figured out that gcc-mp-7 was the one I was looking for but how can I get >> it to be the default gcc compiler ? >> I tried various sudo port select gcc… but all failed. > > port select is the way. It works fine. > > Titan ~ > sudo port select gcc > Available versions for gcc: > mp-gcc7 > none (active) > > Titan ~ > which gcc > /usr/bin/gcc > > Titan ~ > sudo port select gcc mp-gcc7 > Selecting 'mp-gcc7' for 'gcc' succeeded. 'mp-gcc7' is now active. > > Titan ~ > which gcc > /opt/local/bin/gcc > > Titan ~ > gcc --version > gcc (MacPorts gcc7 7.3.0_1) 7.3.0 > Copyright (C) 2017 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > > Please provide details on exactly what you did and exactly how it failed. > > Chris > >> By the way, I tested the 3 other gcc-*-mp-7 (ranlib, ar, and nm) and all >> complained : >>> gcc-ranlib-mp-7 >> gcc-ranlib-mp-7: Cannot find plugin ‘liblto_plugin.so' >> Does it matter ? >> L. >> "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise >> Shadok) "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)
Re: stupid question
On 29/06/18 16:21, pagani laurent via macports-users wrote: Hi, I have gcc7.0 installed : sudo port installed gcc7 The following ports are currently installed: gcc7 @7.3.0_0 (active) but I can’t use it under that name. There are several gcc-* files in the /bin I figured out that gcc-mp-7 was the one I was looking for but how can I get it to be the default gcc compiler ? I tried various sudo port select gcc… but all failed. port select is the way. It works fine. Titan ~ > sudo port select gcc Available versions for gcc: mp-gcc7 none (active) Titan ~ > which gcc /usr/bin/gcc Titan ~ > sudo port select gcc mp-gcc7 Selecting 'mp-gcc7' for 'gcc' succeeded. 'mp-gcc7' is now active. Titan ~ > which gcc /opt/local/bin/gcc Titan ~ > gcc --version gcc (MacPorts gcc7 7.3.0_1) 7.3.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Please provide details on exactly what you did and exactly how it failed. Chris By the way, I tested the 3 other gcc-*-mp-7 (ranlib, ar, and nm) and all complained : gcc-ranlib-mp-7 gcc-ranlib-mp-7: Cannot find plugin ‘liblto_plugin.so' Does it matter ? L. "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)
stupid question
Hi, I have gcc7.0 installed : >sudo port installed gcc7 The following ports are currently installed: gcc7 @7.3.0_0 (active) but I can’t use it under that name. There are several gcc-* files in the /bin I figured out that gcc-mp-7 was the one I was looking for but how can I get it to be the default gcc compiler ? I tried various sudo port select gcc… but all failed. By the way, I tested the 3 other gcc-*-mp-7 (ranlib, ar, and nm) and all complained : >gcc-ranlib-mp-7 gcc-ranlib-mp-7: Cannot find plugin ‘liblto_plugin.so' Does it matter ? L. "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)
Re: smartctl - Can't run select span range
Definitely going to give the sleep thing a try.
Since I'm trying to automate this to kick off long smartctl tests at
specific times, opening a separate window just for caffeinate won't be very
efficient. I've got some ideas on how to script this out.
I'd still love it if Apple would just allow selective span test ranges
instead of just short and long tests.
-Ubence
On Fri, Jun 29, 2018 at 5:36 AM Rainer Müller wrote:
> On 2018-06-29 10:03, Ryan Schmidt wrote:
> >
> > On Jun 28, 2018, at 19:43, Ubence Quevedo wrote:
> >
> >> I gave caffeinate a try, and set my system sleep time to a more
> reasonable timeout [30 minutes], but since smartctl isn't an interactive
> process [a tsr?], the system never stays awake long enough to finish a
> whole test. I even added the -m option to prevent the disk from idle
> sleeping but that didn't help.
> >
> > Oh, right. As I recall, smartctl exits immediately, and the test occurs
> on the disk in the background, and you later run smartctl again to get the
> result.
> >
> > In that case, you can run smartctl normally, and then caffeinate a sleep
> command that takes at least as long as the test. For example, if the test
> will take 206 minutes, you could sleep for 207 minutes (12,420 seconds):
> >
> > caffeinate -i sleep 12420
> >
> > ("sleep" in this context means "wait this many seconds").
>
> You can just start caffeinate without any arguments in a separate
> terminal window to prevent the system from sleeping until you kill the
> process (with Ctrl-C).
>
> Rainer
>
Re: smartctl - Can't run select span range
On 2018-06-29 10:03, Ryan Schmidt wrote:
>
> On Jun 28, 2018, at 19:43, Ubence Quevedo wrote:
>
>> I gave caffeinate a try, and set my system sleep time to a more reasonable
>> timeout [30 minutes], but since smartctl isn't an interactive process [a
>> tsr?], the system never stays awake long enough to finish a whole test. I
>> even added the -m option to prevent the disk from idle sleeping but that
>> didn't help.
>
> Oh, right. As I recall, smartctl exits immediately, and the test occurs on
> the disk in the background, and you later run smartctl again to get the
> result.
>
> In that case, you can run smartctl normally, and then caffeinate a sleep
> command that takes at least as long as the test. For example, if the test
> will take 206 minutes, you could sleep for 207 minutes (12,420 seconds):
>
> caffeinate -i sleep 12420
>
> ("sleep" in this context means "wait this many seconds").
You can just start caffeinate without any arguments in a separate
terminal window to prevent the system from sleeping until you kill the
process (with Ctrl-C).
Rainer
Re: smartctl - Can't run select span range
On Jun 28, 2018, at 19:43, Ubence Quevedo wrote:
> On Tue, Jun 26, 2018 at 9:31 PM Ryan Schmidt wrote:
>
>> On Jun 26, 2018, at 07:32, Ubence Quevedo wrote:
>>
>> > Ubences-MacBook-Pro:ata uquevedo$ smartctl -t long /dev/disk2
>> > smartctl 6.6 2017-11-05 r4594 [Darwin 17.6.0 x86_64] (local build)
>> > Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
>> >
>> > === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
>> > Sending command: "Execute SMART Extended self-test routine immediately in
>> > off-line mode".
>> > Drive command "Execute SMART Extended self-test routine immediately in
>> > off-line mode" successful.
>> > Testing has begun.
>> > Please wait 206 minutes for test to complete.
>> > Test will complete after Tue Jun 26 08:52:02 2018
>> >
>> > Use smartctl -X to abort test.
>> >
>> > There’s no way that will complete under my system’s sleep schedule [three
>> > hour timeout for sleep] which isn’t ideal anyways.
>>
>> So tell the system not to sleep while the test is running.
>>
>> caffeinate -i smartctl -t long /dev/disk2
>>
>> For more info:
>>
>> man caffeinate
>
> I gave caffeinate a try, and set my system sleep time to a more reasonable
> timeout [30 minutes], but since smartctl isn't an interactive process [a
> tsr?], the system never stays awake long enough to finish a whole test. I
> even added the -m option to prevent the disk from idle sleeping but that
> didn't help.
Oh, right. As I recall, smartctl exits immediately, and the test occurs on the
disk in the background, and you later run smartctl again to get the result.
In that case, you can run smartctl normally, and then caffeinate a sleep
command that takes at least as long as the test. For example, if the test will
take 206 minutes, you could sleep for 207 minutes (12,420 seconds):
caffeinate -i sleep 12420
("sleep" in this context means "wait this many seconds").
