Re: scons linkage

[rmgls]

Hello Bill,

Thanks for this  helpful info.

Bests

Raoul



> On 22 Feb 2022, at 02:13, Bill Deegan  wrote:
> 
> Raoul,
> 
> If you want to run modern scons with python3 (and you're using macports for 
> newer python installs), probably easiest way to do so is to use a virtualenv.
> 
> https://scons-cookbook.readthedocs.io/en/latest/#setting-up-a-python-virtualenv-for-scons
> 
> -Bill
> SCons Project Co-Manager
> (my main machine is a mac..with macports.. ;)
> 
> On Mon, Feb 21, 2022 at 10:15 AM rmgls  wrote:
> Hi Ryan,
> 
> thanks for clarification
> 
> Bests
> Raoul
> 
> 
> > On 21 Feb 2022, at 17:11, Ryan Schmidt  wrote:
> > 
> > On Feb 19, 2022, at 01:24, rmgls wrote:
> > 
> >> how to bypass the 2.7 python in /system/Library and direct  by default to  
> >> a macport version or even a user path.
> >> details:
> >> port install scons  3.1.X
> >> port select  --set …..
> >> invoking scons  calls the system scons 2.7?
> > 
> > The scons port version 3.1.2 uses MacPorts python 2.7 -- at least that is 
> > the intention. It is not intended to use the system's python.
> > 
> > You may verify which python it will run by using this command:
> > 
> > 
> > head -n1 $(which scons)
> > 
> > 
> > A future version of the scons port will use MacPorts python 3.x. You may Cc 
> > yourself on this ticket if you wish to be notified when that happens:
> > 
> > https://trac.macports.org/ticket/59303
> 

Re: scons linkage

[rmgls]

Hi Ryan,

thanks for clarification

Bests
Raoul


> On 21 Feb 2022, at 17:11, Ryan Schmidt  wrote:
> 
> On Feb 19, 2022, at 01:24, rmgls wrote:
> 
>> how to bypass the 2.7 python in /system/Library and direct  by default to  a 
>> macport version or even a user path.
>> details:
>> port install scons  3.1.X
>> port select  --set …..
>> invoking scons  calls the system scons 2.7?
> 
> The scons port version 3.1.2 uses MacPorts python 2.7 -- at least that is the 
> intention. It is not intended to use the system's python.
> 
> You may verify which python it will run by using this command:
> 
> 
> head -n1 $(which scons)
> 
> 
> A future version of the scons port will use MacPorts python 3.x. You may Cc 
> yourself on this ticket if you wish to be notified when that happens:
> 
> https://trac.macports.org/ticket/59303

scons linkage

[rmgls]

Hello,

sorry for this basic question:
how to bypass the 2.7 python in /system/Library and direct  by default to  a 
macport version or even a user path.
details:
port install scons  3.1.X
port select  --set …..
 invoking scons  calls the system scons 2.7?

Thanks for clarifiction.

Raoul

liboil fail to compile

[rmgls]

hello all,

mplayer install  fails because liboil does not  build correctly.
as i can see it is gtkdocize related.
any hints would be appreciated.

bests.

Raoul
rm...@orange.fr

Re: audacity build problem

[rmgls]

Thanks a lot.




> On 5 Nov 2021, at 17:41, Ryan Schmidt  wrote:
> 
> On Nov 5, 2021, at 11:39, rmgls wrote:
> 
>> On 5 Nov 2021, at 16:54, Ryan Schmidt wrote:
>> 
>>> The crash log would be most helpful. It should be located in /Users/>> username>/Library/Logs/DiagnosticReports/ - find the most recent one with 
>>> "audacity" in the name.
>>> 
>> 
>>> 
>>> 
>>>> apart of this, the  pacports log is completely empty.
>>>> no main.log for anything.
>>> 
>>> MacPorts deletes the main.log file after a successful install unless you 
>>> tell it not to. Since the build was successful, I'm not sure the main.log 
>>> would be helpful anyway.
>>> 
>>> 
>> ha, i understand why.
>> 
>> Please when you find the problem,
>> just two words  to explain .
> 
> I'm afraid I don't have any idea, but the information in the crash log might 
> be useful to the developers of Audacity or the maintainer of the port in 
> diagnosing the problem.
> 
> 

Re: audacity build problem

[rmgls]

> On 5 Nov 2021, at 16:54, Ryan Schmidt  wrote:
> 
> 
> 
>> On Nov 5, 2021, at 10:14, rmgls wrote:
>> 
>> at launching audacity  crashes.
>> if  attached files does not match, please tell me exactly what you expect.
> 
> The crash log would be most helpful. It should be located in /Users/ username>/Library/Logs/DiagnosticReports/ - find the most recent one with 
> "audacity" in the name.
> 


Audacity_2021-11-05-154437_Mmini-A.crash
Description: Binary data
> 
> 
>> apart of this, the  pacports log is completely empty.
>> no main.log for anything.
> 
> MacPorts deletes the main.log file after a successful install unless you tell 
> it not to. Since the build was successful, I'm not sure the main.log would be 
> helpful anyway.
> 
> 
ha, i understand why.

Please when you find the problem,
just two words  to explain .

Thanks.

audacity build problem

[rmgls]

Hello all,

trying to build audacity displays:

7 broken  files  and 1 broken port
continue Y/N?

continuing  build  completely, but launching audacity
fails.

first thing, i suspected a mine fault so:
i decided to delete completely and reinstall macports
(on BigSur).
even this gives the same errors.

any idea would help.

Thanks in advance.

Raoul
rm...@orange.fr

wavpack update needed

[rmgls]

Hello all,

wavpack  installed  in macports need to be updated to the  last
available version.
wavpack emits a warning when used with tag3 for instance.

i downloaded the latest version from the web site
it builds fine, and seems to work fine with sox.
perhaps,   it would be  updated in the port tree?

Bests

Raoul
rm...@orange.fr

Re: configure error on compile ports

[rmgls]

Hello Rayan,

as often you are completely right,
thanks for giving your experience.

all is fine now.

in fact i forgot to delete Applications/macports/*
so, dbus,  and other  osfts  was  orphan, and not registered.

Thanks again.


> On 15 Feb 2021, at 09:44, Ryan Schmidt  wrote:
> 
> 
> 
> On Feb 14, 2021, at 12:22, rmgls wrote:
> 
>> Please can you tell me what to do about this error
>> (elinks but also many other compile)?
>> 
>> 
>> :info:configure checking for gcc... /usr/bin/clang
>> :info:configure checking for C compiler default output file name... 
>> :info:configure configure: error: C compiler cannot create executables
>> 
>> some details:
>> osx11.2. new macports (/opt/local entirely deleted first).
>> gcc and clang correctly seated in /usr/bin and running fine.
>> xcode up-to-date, and commandline tools installed!
> 
> Error messages shown in the config.log file should tell you why the compiler 
> cannot create executables. Often, the cause is that you have not updated the 
> command line tools to a version that is compatible with your OS. When in 
> doubt, download the correct command line tools manually and reinstall them.
> 

Re: configure error on compile ports

[rmgls]

Hello Craig,

Yes xcode run fine here.
Thanks for your reply.

R.M.



> On 14 Feb 2021, at 19:58, Craig Treleaven  wrote:
> 
>> On Feb 14, 2021, at 1:22 PM, rmgls  wrote:
>> ...
>> :info:configure checking for gcc... /usr/bin/clang
>> :info:configure checking for C compiler default output file name... 
>> :info:configure configure: error: C compiler cannot create executables
>> 
>> some details:
>> osx11.2. new macports (/opt/local entirely deleted first).
>> gcc and clang correctly seated in /usr/bin and running fine.
>> xcode up-to-date, and commandline tools installed!
> 
> Have you installed the Xcode command line tools and accepted the license?
> 
> https://www.macports.org/install.php
> 
> Craig
> 

configure error on compile ports

[rmgls]

Hello list,

Please can you tell me what to do about this error
(elinks but also many other compile)?


:info:configure checking for gcc... /usr/bin/clang
:info:configure checking for C compiler default output file name... 
:info:configure configure: error: C compiler cannot create executables

some details:
osx11.2. new macports (/opt/local entirely deleted first).
gcc and clang correctly seated in /usr/bin and running fine.
xcode up-to-date, and commandline tools installed!

Thanks for your answer.

Raoul MEGELAS
rm...@orange.fr

Re: faust-devel

[rmgls]

> On 29 Jun 2020, at 16:06, Ryan Schmidt  wrote:
> 
> 
> 
> On Jun 28, 2020, at 12:24, rmgls wrote:
> 
>> here is what i get:
>> 
>> fetching  distfiles for faust-devel
>> 
>> and nothing else!
> 
> How long did you wait? Unlike most ports, this one fetches from a git 
> repository. There will be no progress bar or any other output while the 
> download happens. In the current version, it fetches 625MB of data. That may 
> take some time if your network is slow. My network is fairly fast so it only 
> took a minute.
> a long time!
the download did not  start at all.

> the version is apparently  really old.
>> 
>> faust  version is 2.14.4  on their site
>> (there is a binary package too).
>> can we upgrade?
> 
> Probably. I haven't touched these ports in awhile. There is another 
> maintainer but he hasn't been active lately either. Would you file a ticket 
> in our issue tracker requesting this update? Or if you're feeling adventurous 
> you can try to do the update yourself and submit a pull request to us.
> 
i will try to see,  if i am too  stuck, i will  put a ticket.
Thanks Rayan.

Raoul
rm...@orange.fr

faust-devel

[rmgls]

Hello list,

here is what i get:

fetching  distfiles for faust-devel

and nothing else!

the version is apparently  really old.

faust  version is 2.14.4  on their site
(there is a binary package too).
can we upgrade?

Bests

Raoul
rm...@orange.fr

Re: macports-users Digest, Vol 165, Issue 19

[rmgls]

HEllo Rayan


THanks i do it
if i can open the app build by notahat.

Thanks

Raoul

> On 22 May 2020, at 23:53, Ryan Schmidt  wrote:
> 
> 
> 
> On May 22, 2020, at 08:02, rmgls wrote:
>> On May 22, 2020, Rayan Schmidt wrote:
>>> On May 21, 2020, at 01:41, rmgls wrote:
>> 
>>>> midi_patchbay  builds  fine.
>>>> But Please try to open it :
>>>> you will see than nothing is displayed!
>> 
>>> It opens fine for me on High Sierra and displays its Untitled window.
>> 
>> Hello Rayan,
>> 
>> yes you are right except than normally it display a full content in this 
>> window 
>> i.e. add path, input, output, and plenty other things.
>> it is impossible to create a new mpb, nor load an ancient.
>> don't know why.
>> have had this since 10.13 i think.
>> for 10.14 the app downloaded from notahat.com worked fine.
> 
> Maybe you should file a bug report in our issue tracker and attach a 
> screenshot there of what you are seeing. I do not see much difference between 
> the version of the app built by MacPorts and the one downloadable from the 
> developer's web site.
> 

Re: macports-users Digest, Vol 165, Issue 19

[rmgls]

On May 22, 2020, Rayan Schmidt wrote:
On May 21, 2020, at 01:41, rmgls wrote:
i 
>> midi_patchbay  builds  fine.
>> But Please try to open it :
> >you will see than nothing is displayed!

> It opens fine for me on High Sierra and displays its Untitled window.

Hello Rayan,

yes you are right except than normally it display a full content in this window 
i.e. add path, input, output, and plenty other things.
it is impossible to create a new mpb, nor load an ancient.
don't know why.
 have had this since 10.13 i think.
 for 10.14 the app downloaded from notahat.com worked fine.

Thanks  for your interest and help.

Raoul MEGELAS
rm...@orange.fr

midi_patchbay

[rmgls]

Hello all,

midi_patchbay  builds  fine.
But Please try to open it :
you will see than nothing is displayed!
$interesting thing,  it does not have any dependance.
the build app on notahat.com does not launch on 10.15.X.
if you have any clue,  it would be  really useful.

thanks in advance

Raoul MEGELAS
rm...@orange.fr

Re: samba4 error

[rmgls]

hello Ryan and Bill,

thanks for your reply.

reading Bill,  i think i will  only use smbd included on mac.

thanks.

Raoul MEGELAS
rm...@orange.fr


On Apr 9, 2020, at 11:20, rmgls wrote:

> samba4 does not build.

True. 7 years ago somebody already filed a bug report about a different problem 
building samba4:

https://trac.macports.org/ticket/38639

If anybody would like to work on fixing it, please do. Thus far, nobody has 
done so.

samba4 error

[rmgls]

Hello All,

samba4 does not build.
i join samba4error.tgz  to help debugging.

Please can you tell me what to do?

Thanks in advance.



samba4error.tgz
Description: Binary data

Re: samba4

[rmgls]

HEllo Rayan, 

thanks for the link. 

i will correct the address book then.

Raoul



> On 8 Jul 2019, at 12:42, Ryan Schmidt  wrote:
> 
> 
> 
> On Jul 6, 2019, at 11:27, rmgls wrote:
> 
>> trying to build samba4 i get these errors, 
> 
> There are a few 6-year-old tickets open about the samba4 port, including a 
> build failure (for a different reason than the one you encountered) and a 
> need to update the port:
> 
> https://trac.macports.org/query?status=!closed=~samba4
> 
> So I would suspect that nobody will be able to build the port until someone 
> volunteers to fix it.
> 
> 
> P.S: Please use our new list addresses at lists.macports.org, not the older 
> hostname you used which we deprecated in 2016.
> 

Vlc build fail

[rmgls]

hello all,

Attempting to build VLC I get the following:

:info:build  /usr/bin/install -c -m 644 icons/128x128/vlc.png 
icons/128x128/vlc-xmas.png 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/icons/hicolor/128x128/apps'
:info:build  /usr/bin/install -c -m 644 icons/256x256/vlc.png 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/icons/hicolor/256x256/apps'
:info:build  /usr/bin/install -c -m 644 vlc.desktop 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/applications'
:info:build  /usr/bin/install -c -m 644 icons/vlc.ico 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/vlc'
:info:build  /usr/bin/install -c -m 644 icons/48x48/vlc.png 
icons/48x48/vlc-xmas.png 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/icons/hicolor/48x48/apps'
:info:build  /usr/bin/install -c -m 644 icons/16x16/vlc.png icons/16x16/vlc.xpm 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/icons/hicolor/16x16/apps'
:info:build  /usr/bin/install -c -m 644 icons/32x32/vlc.png icons/32x32/vlc.xpm 
icons/32x32/vlc-xmas.xpm 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/icons/hicolor/32x32/apps'
:info:build  ../autotools/install-sh -c -d 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/vlc/utils/'
:info:build  ../autotools/install-sh -c -d 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/vlc/lua/http/css/ui-lightness/images'
:info:build  ../autotools/install-sh -c -d 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/doc/vlc/lua/meta/reader'
:info:build  ../autotools/install-sh -c -d 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/lib/vlc/lua/meta/reader'
:info:build  /usr/bin/install -c utils/gnome-vlc-default.sh 
utils/audio-vlc-default.sh utils/video-vlc-default.sh 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/vlc/utils/'
:info:build  /usr/bin/install -c -m 644  lua/meta/reader/README.txt 
lua/meta/reader/filename.lua 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/doc/vlc/lua/meta/reader'
:info:build  /usr/bin/install -c -m 644  
lua/http/css/ui-lightness/images/ui-bg_diagonals-thick_20_66_40x40.png 
lua/http/css/ui-lightness/images/ui-bg_flat_10_00_40x100.png 
lua/http/css/ui-lightness/images/ui-icons_ff_256x240.png 
lua/http/css/ui-lightness/images/ui-bg_gloss-wave_35_f6a828_500x100.png 
lua/http/css/ui-lightness/images/ui-bg_glass_65_ff_1x400.png 
lua/http/css/ui-lightness/images/ui-icons_22_256x240.png 
lua/http/css/ui-lightness/images/ui-bg_glass_100_f6f6f6_1x400.png 
lua/http/css/ui-lightness/images/ui-bg_highlight-soft_100_ee_1x100.png 
lua/http/css/ui-lightness/images/ui-bg_highlight-soft_75_ffe45c_1x100.png 
lua/http/css/ui-lightness/images/ui-bg_diagonals-thick_18_b81900_40x40.png 
lua/http/css/ui-lightness/images/ui-icons_ffd27a_256x240.png 
lua/http/css/ui-lightness/images/ui-icons_228ef1_256x240.png 
lua/http/css/ui-lightness/images/ui-icons_ef8c08_256x240.png 
lua/http/css/ui-lightness/images/ui-bg_glass_100_fdf5ce_1x400.png 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/vlc/lua/http/css/ui-lightness/images'
:info:build  ../autotools/install-sh -c -d 

Re: source-highLight failed to compile

[rmgls]

Helo Rayan,



Thanks for yout time,  and your explanation.

my laziness   have been punished!

i did not follow the  procedure:
Deinstall ports, and so on!!!


Many thanks.

Raoul


> On 23 Oct 2018, at 10:20, Ryan Schmidt  wrote:
> 
> On Oct 23, 2018, at 01:26, rmgls wrote:
> 
>> Source-hiLight failed to compile!
>> Main.log attached.
>> 
>> any idea?
> 
> The log shows you're using Xcode 10 with clang 1000.11.45.2 on macOS 10.14.
> 
> The error in the log is:
> 
> :info:build /opt/local/bin/ranlib: object: .libs/libgnu.a(dirname-lgpl.o) 
> malformed object (unknown load command 1)
> :info:build ar: internal ranlib command failed
> 
> So you're compiling using the latest clang, but you have the cctools port 
> installed, which provides ranlib and other related programs, and it's not 
> able to understand the object files that clang produced.
> 
> Unfortunately MacPorts cctools is old (it's equivalent to Xcode 8.1) and is 
> not compatible with the clang in Xcode 9 or later. This is because 
> unfortunately Apple has not released the source code of newer versions of 
> cctools, so we cannot update the copy in MacPorts to anything newer.
> 
> The cctools port should have detected that you were using Xcode 9 or later 
> and should have installed itself with the +xcode variant, which makes it 
> install only symlinks to Xcode's copies of the programs, instead of building 
> its own older copies, and that should have worked.
> 
> Since it didn't work, can you verify which variant of cctools is installed? 
> Run `port -v installed cctools` to find out. If it does not show the +xcode 
> variant selected, reinstall cctools with the +xcode variant by running `sudo 
> port install cctools +xcode`, then `sudo port clean source-highlight` and try 
> again.
> 

source-highLight failed to compile

[rmgls]

Hi all,

Source-hiLight failed to compile!
Main.log attached.

any idea?

thanks in advance.

Raoul  Megelas


main.log.gz
Description: GNU Zip compressed data

where is the needed sdk?

[rmgls]

   Hello all,


Please how can i solve this problem:
   macports 2.5.4
   sudo port selfupdate
   sudo port upgrade outdated
Error: Unable to determine location of a macOS SDK.
Error: Unable to open port: can't read "configure.sdkroot": Unable to determine 
location of a macOS SDK.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
   xcodebuild: 
Xcode 10.0
Build version 10A255
   uname -a
Darwin ... 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; 
root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64

Thanks

   Best
   Raoul

Re: mplayer start problem

[rmgls]

hi,

Thanks, i’ll get a try.

rmgls


> On 8 Apr 2018, at 20:53, Ken Cunningham <ken.cunningham.web...@gmail.com> 
> wrote:
> 
> 
> 
>> On Apr 8, 2018, at 11:35 AM, rmgls <rm...@orange.fr 
>> <mailto:rm...@orange.fr>> wrote:
>> 
>> hi all,
>>   in terminal mode:
>>   mplayer somefile.mp3
>> illegal instruction 4
>>   my ports are up-to-date, and mplayer reinsta   lled.
>> Darwin myhost.home 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 
>> PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64 x86_64
>> 
>> any idea?
>> 
>> thanks.
>> 
>> rm...@orange.fr <mailto:rm...@orange.fr>
>> 
> 
> Works for me. Try another mp3? — K
> 
> mplayer 
> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/HomeUI.framework/alarm1-b238.mp3
> MPlayer 1.3.0-4.2.1 (C) 2000-2016 MPlayer Team
> 224 audio & 451 video codecs
> 
> Playing 
> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/HomeUI.framework/alarm1-b238.mp3.
> libavformat version 57.25.100 (internal)
> Audio only file format detected.
> Load subtitles in 
> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/HomeUI.framework/
> ==
> Requested audio codec family [mpg123] (afm=mpg123) not available.
> Enable it at compilation.
> Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
> libavcodec version 57.24.102 (internal)
> AUDIO: 48000 Hz, 2 ch, floatle, 192.0 kbit/6.25% (ratio: 24000->384000)
> Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3 audio)
> ==
> AO: [coreaudio] 48000Hz 2ch floatle (4 bytes per sample)
> Video: no video
> Starting playback...
> 
> 

Re: Lynx port crash

[rmgls]

Thank you very match.

Raoul  MEGELAS
rm...@orange.fr <mailto:rm...@orange.fr>



> On 26 Dec 2017, at 18:16, Ryan Schmidt <ryandes...@macports.org> wrote:
> 
> 
> On Dec 26, 2017, at 04:12, rmgls wrote:
> 
>> sorry, my english is not very concease, but here is how to reproduce:
>> here is the complete procedure to repeat.
>> sudo port install lynx.
>>  ...
>> lynx ./
>>  m n
>> NEWNAME return:
>>  abort: trap 6!!!
>> 
>> this was fixed in lynx-cur when i contacted Thomas Dickey.
> 
> Your English is fine! Thanks for the reproduction recipe. I didn't know lynx 
> had file management capabilities built in.
> 
> I can reproduce this problem. I have determined that it was fixed between 
> 2.8.9dev.2 and 2.8.9dev.3. I can't find a public repository of lynx source 
> code so I will try to create a patch that we can use in MacPorts.
> 
> 

Re: Lynx port crash

[rmgls]

>  On Dec 25, 2017, at 13:47, Raoul wrote:
>  
>  On 24 Dec 2017, at 14:59, Jan Stary wrote:
>  
>  On Nov 10 07:37:31, Raoul wrote:
>  It was fixed on my demand two years ago by  the developer
>  Thomas Dickey  (a FreeBSD developer!)
>  I will revert to 2.8.8 to see if it is the culprit.
>  
>  Hello The lynx macport still crashes
>  when renaming a file or folder.
>  
>  I don't get it: when does lynx rename a file or directory,
>  and how exactly does it crash?
  

Lynx Version 2.8.8rel.2 (09 Mar 2014)
libwww-FM 2.14, SSL-MM 1.4.1, OpenSSL 1.0.2n, ncurses 6.0.20171125
Built on darwin17.2.0 Nov  7 2017 15:30:28

Copyrights held by the Lynx Developers Group,
the University of Kansas, CERN, and other contributors.
Distributed under the GNU General Public License (Version 2).
See http://lynx.isc.org/ and the online help for more information.

See http://www.openssl.org/ for information about OpenSSL.
   otool -L lynx

/opt/local/lib/libidn.11.dylib (compatibility version 18.0.0, current 
version 18.16.0)
/opt/local/lib/libncurses.6.dylib (compatibility version 6.0.0, current 
version 6.0.0)
/opt/local/lib/libssl.1.0.0.dylib (compatibility version 1.0.0, current 
version 1.0.0)
/opt/local/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, 
current version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 1252.0.0)
/opt/local/lib/libintl.8.dylib (compatibility version 10.0.0, current 
version 10.5.0)
/opt/local/lib/libiconv.2.dylib (compatibility version 9.0.0, current 
version 9.0.0)


The  lynx-cur.tar.gz from invisible-island.net>
does not crash while renaming file or path.
  
>  MP uses lynx2.8.8rel.2.tar.bz2
>  
>  This problem affect only the lynx from macports.
>  
>  What problem? Is there a ticket?
>  https://trac.macports.org/report/16?PORT=lynx
>  Hi,
>  
>  No there is no ticket yet, 
> ...
>  Mac port lynx crashes when renaming a file/folder.
  
lynx-cur.tar.gz 
from http://lynx.invisible-island.net does not crash.
  
  
>  Could you be more specific about what you mean by "add anything" and 
> "renaming a file/folder"? What series of steps would we need to perform on 
> our systems to observe the problem?

sorry, my english is not very concease, but here is how to reproduce:
 here is the complete procedure to repeat.
sudo port install lynx.
   ...
lynx ./
   m n
NEWNAME return:
   abort: trap 6!!!

this was fixed in lynx-cur when i contacted Thomas Dickey.


  
>  Also, I see an incorrect list address was used on this email thread.
>  Remember to write only to macports-users [at] lists.macports.org, not at any 
> other domain name.

sorry, i have benn too confiant to mail:
cmd-sh-r!!!
next time i will verify what it does,.

Regards,

Raoul
rm...@orange.fr

Re: Lynx port crash

[rmgls]

> Raoul

> On 24 Dec 2017, at 14:59, Jan Stary  wrote:
> 
> On Nov 10 07:37:31, rm...@orange.fr wrote:
>> It was fixed on my demand two years ago by  the developer
>> Thomas Dickey  (a FreeBSD developer!)
>> I will revert to 2.8.8 to see if it is the culprit.
> 
 Hello The lynx macport still crashes
 when renaming a file or folder.
> 
> I don't get it: when does lynx rename a file or directory,
> and how exactly does it crash?
> 
 The  lynx-cur.tar.gz from invisible-island.net
 source code compiles fine, 
 And does not crash at all  while renaming.
> 
> MP uses lynx2.8.8rel.2.tar.bz2
> 
 This problem affect only the lynx from macports.
> 
> What problem? Is there a ticket?
> https://trac.macports.org/report/16?PORT=lynx
> Hi,

No there is no ticket yet, 
The problem is explicitly  explained above,  I cannot add  anything.
Mac port lync crashes when renaming a file/folder.
This  only about lynx from mac ports
The lynxcur  from source  without any patch, does not crash,
I use it al days.


>   Jan

Re: Lynx port crash

[rmgls]

Hello  Ryan,

It was fixed on my demand two years ago by  the developer
Thomas Dickey  (a FreeBSD developer!)
I will revert to 2.8.8 to see if it is the culprit.
And  communicate with Thomas Dickey.

Thanks.



> On 10 Nov 2017, at 04:20, Ryan Schmidt <ryandes...@macports.org> wrote:
> 
> 
> On Nov 9, 2017, at 15:11, rmgls wrote:
> 
>> Hello The lynx macport still crashes
>> when renaming a file or folder.
>> This  point has not been corrected, since  perhaps  one year.
>> 
>> The  lynx-cur.tar.gz from invisible-island.net
>> source code compiles fine, 
>> And does not crash at all  while renaming.
>> 
>> This problem affect only the lynx from macports.
>> 
>> Perhaps one of  the patches  introduce s this fault,  but I am not sure, I 
>> have not yet read them.
>> in all case it is still crashing.
>> 
>> Any idea?
> 
> I don't see a bug report in our issue tracker about this, so you could start 
> by filing one. Our port only has minimal patches which I don't suspect would 
> cause a crash. If the current development source available on the lynx web 
> site works, but 2.8.8 does not, you might suggest to the developers that they 
> release a new version 2.8.9; 2.8.8 is over 3.5 years old at this point so I 
> wouldn't be surprised if the developers have fixed a number of things in the 
> mean time.

Lynx port crash

[rmgls]

Hello The lynx macport still crashes
when renaming a file or folder.
This  point has not been corrected, since  perhaps  one year.

The  lynx-cur.tar.gz from invisible-island.net <http://invisible-island.net/>
source code compiles fine, 
And does not crash at all  while renaming.

This problem affect only the lynx from macports.

Perhaps one of  the patches  introduce s this fault,  but  I am not sure, I 
have not yet read them.
in all case it is still crashing.

Any idea?

Bests.

Rmgls
rm...@orange.fr <mailto:rm...@orange.fr>