[Help] Linux low level data structures < - > FreeBSD low level data structures
Hello Is there anyone on either of these lists that have experience with both linux low level data structures and their equivalents on FreeBSD? For instance the linux header file: which includes the header file: Then looking at that file: I'll be doing a lot of work trying to find these FreeBSD equivalent of these types of files to port some code. Does anyone here have experience with something like this? Is there any other projects that maps these low level data structures from Linux <-> FreeBSD, etc? Best, Owen ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [Help] Linux low level data structures < - > FreeBSD low level data structures
On 4/6/17 7:07 pm, blubee blubeeme wrote: Hello Is there anyone on either of these lists that have experience with both linux low level data structures and their equivalents on FreeBSD? For instance the linux header file: which includes the header file: Then looking at that file: You are going to have to be a lot more specific about this. I have worked in several places where they use s shim layer to make Linux basic services work on freeBSD. usually a mix of functions, macros and inlines. However you need to narrow down your questions a bit as the POSSIBLE scope of your question is too large for anyone to attempt an answer. Remember that both systems are POSIX inspired so outside the kernel there are many more simlarities than one might be led to expect, but you need to be way more specific. It's even possible to write kernel code to run on both, but it is usually domain specific. I'll be doing a lot of work trying to find these FreeBSD equivalent of these types of files to port some code. Does anyone here have experience with something like this? Is there any other projects that maps these low level data structures from Linux <-> FreeBSD, etc? Best, Owen ___ freebsd-curr...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox and OSS
On Sun, 4 Jun 2017 09:33:03 +0300 abi wrote: > AFAIK OSS support is not complete (WebRTS doesn't use it) If WebRTS is not spoorted - ok, let user decide. I prefer to have option for OSS, and able to build firefox without sound support at all. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Which wine do I need?
On Sun, 28 May 2017, Gerald Pfeifer wrote: > What do you guys think about the following patch for emulators/wine > to help clarify this? I now applied this to help clarify for others (just changing lang/i386-wine to emulators/i386-wine - too much lang/gcc* work recently ;-). Gerald ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [Help] Linux low level data structures < - > FreeBSD low level data structures
Hi Julian My goals are to port the Linux graphics stack over to FreeBSD w/o relying too heavily on the linuxkpi stuff. That's cool for a lot of use cases but it just seems a bit too brittle. It is a very large I understand the task will not be easy but I am willing to do the work, even from scratch if necessary although some help would be appreciated. I've been watching the Linux DRM project grow and while the top levels has changed, it's been a very long time since the actual low level stuff has been changed. Most of the diffs have shown changes in the [linux/driver/gpu/drm] layer which relies heavily on the [linux/include/drm] that does a lot of the heavy lifting here's a link to the latest version files: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/drm?h=v4.12-rc3 here's a diff of the latest version of the [linux/driver/gpu/drm] : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/?id=v4.12-rc3&id2=v4.12-rc2&dt=2 The diffs in the drivers change constantly but the lower level stuff hasn't changed as much. Doing some of the lower level translation to native FreeBSD style data structures then the upper part could be easily migrated, even with something as using AST to translate the headers to their FreeBSD equivalent without worrying about inadvertently breaking something or having major diffs that needs people to actively look at maintaining. That's a high level overview of my plan and what I'd like to achieve. Will it be easy, most likely not but once it's done FreeBSD will be just fine. Hope that helps clarify things for anyone who is interested. Any assistance would be greatly appreciated. Best, Owen On Sun, Jun 4, 2017 at 9:26 PM, Julian Elischer wrote: > On 4/6/17 7:07 pm, blubee blubeeme wrote: > >> Hello >> >> Is there anyone on either of these lists that have experience with both >> linux low level data structures and their equivalents on FreeBSD? >> >> For instance the linux header file: >> >> >> which includes the header file: >> >> >> Then looking at that file: >> >> >> >> >> >> > > You are going to have to be a lot more specific about this. > I have worked in several places where they use s shim layer to make Linux > basic services work on freeBSD. > usually a mix of functions, macros and inlines. > However you need to narrow down your questions a bit as the POSSIBLE scope > of your question is too large for anyone to attempt an answer. > > Remember that both systems are POSIX inspired so outside the kernel there > are many more simlarities than one might be led to expect, > but you need to be way more specific. > It's even possible to write kernel code to run on both, but it is usually > domain specific. > > > >> I'll be doing a lot of work trying to find these FreeBSD equivalent of >> these types of files to port some code. >> >> Does anyone here have experience with something like this? Is there any >> other projects that maps these low level data structures from >> Linux <-> FreeBSD, etc? >> >> Best, >> Owen >> ___ >> freebsd-curr...@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org >> " >> > > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: nvidia-driver-375.39
On Fri, 19 May 2017 22:50:38 -0700 "The Saccullo's" wrote: > I'm having a problem loading the nvidia-driver 375.39. > > > > I get the following error: > > link_elf_obj: symbol sc_get_softc undefined > > linker_load_file: Unsupported file type > > > > Any suggestions? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216050 Dont know why it does not commited. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [Help] Linux low level data structures < - > FreeBSD low level data structures
Hi Owen, The most comprehensive open-source wrappers for Linux kernel APIs in the FreeBSD kernel is found at: https://github.com/FreeBSDDesktop/freebsd-base-graphics/tree/drm-next/sys/compat/linuxkpi The most comprehensive open-source wrappers for Linux kernel APIs in FreeBSD user-space is found at: http://www.freshports.org/multimedia/webcamd I recommend you start with webcamd. Download the source code and look at the sources. See if there is something you think you can improve. It is much easier to debug using GDB and if something goes wrong it can easily be restarted. When you have a working solution for webcamd, try to use the same solution with the kernel. There is no simple 1:1 mapping for Linux APIs to FreeBSD APIs. Take for example linux/list.h . You might think that a list can be re-implemented and mapped to our sys/queue.h. But oh-no. Linux kernel code depends on all the characteristics of list.h, how the structure members are stored and named, and how foreach() macros complete with NULL or non-NULL in the iterator. Further you'll find resistance among the Linux kernel developers to support compilers different from GCC. I recently found a piece of code in a header file, which works with GCC and causes a panic() when compiled with clang. I reported it to one of the Linux kernel team members and they didn't care about it. Even if you get everything compiling it doesn't it will work :-( --HPS On 06/04/17 16:35, blubee blubeeme wrote: Hi Julian My goals are to port the Linux graphics stack over to FreeBSD w/o relying too heavily on the linuxkpi stuff. That's cool for a lot of use cases but it just seems a bit too brittle. It is a very large I understand the task will not be easy but I am willing to do the work, even from scratch if necessary although some help would be appreciated. I've been watching the Linux DRM project grow and while the top levels has changed, it's been a very long time since the actual low level stuff has been changed. Most of the diffs have shown changes in the [linux/driver/gpu/drm] layer which relies heavily on the [linux/include/drm] that does a lot of the heavy lifting here's a link to the latest version files: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/drm?h=v4.12-rc3 here's a diff of the latest version of the [linux/driver/gpu/drm] : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/?id=v4.12-rc3&id2=v4.12-rc2&dt=2 The diffs in the drivers change constantly but the lower level stuff hasn't changed as much. Doing some of the lower level translation to native FreeBSD style data structures then the upper part could be easily migrated, even with something as using AST to translate the headers to their FreeBSD equivalent without worrying about inadvertently breaking something or having major diffs that needs people to actively look at maintaining. That's a high level overview of my plan and what I'd like to achieve. Will it be easy, most likely not but once it's done FreeBSD will be just fine. Hope that helps clarify things for anyone who is interested. Any assistance would be greatly appreciated. Best, Owen On Sun, Jun 4, 2017 at 9:26 PM, Julian Elischer wrote: On 4/6/17 7:07 pm, blubee blubeeme wrote: Hello Is there anyone on either of these lists that have experience with both linux low level data structures and their equivalents on FreeBSD? For instance the linux header file: which includes the header file: Then looking at that file: You are going to have to be a lot more specific about this. I have worked in several places where they use s shim layer to make Linux basic services work on freeBSD. usually a mix of functions, macros and inlines. However you need to narrow down your questions a bit as the POSSIBLE scope of your question is too large for anyone to attempt an answer. Remember that both systems are POSIX inspired so outside the kernel there are many more simlarities than one might be led to expect, but you need to be way more specific. It's even possible to write kernel code to run on both, but it is usually domain specific. I'll be doing a lot of work trying to find these FreeBSD equivalent of these types of files to port some code. Does anyone here have experience with something like this? Is there any other projects that maps these low level data structures from Linux <-> FreeBSD, etc? Best, Owen ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [Help] Linux low level data structures < - > FreeBSD low level data structures
＠Hans I've noticed these things about Linux. A lot of stuff relies on knowing the internals of the data structures instead of working with the API but I don't want to start all that stuff up. The goal is to lift up FreeBSD w/o tearing down Linux and as u know needing to be glued to the Linux data structures, while they always seem to be in flux is one reason why I want to steer clear from the linuxkpi stuff. I cam across the webcamd thing a while ago, it was written when Linux was not moving so fast if I remember correctly. This is a big challenge but I think once it's up and running it will bring some additional resources to FreeBSD that can bring the desktop world up to snuff with it's server acumen. Thanks for the tips though! Best, Owen On Mon, Jun 5, 2017 at 12:07 AM, Hans Petter Selasky wrote: > Hi Owen, > > The most comprehensive open-source wrappers for Linux kernel APIs in the > FreeBSD kernel is found at: > > https://github.com/FreeBSDDesktop/freebsd-base-graphics/ > tree/drm-next/sys/compat/linuxkpi > > The most comprehensive open-source wrappers for Linux kernel APIs in > FreeBSD user-space is found at: > > http://www.freshports.org/multimedia/webcamd > > I recommend you start with webcamd. Download the source code and look at > the sources. See if there is something you think you can improve. It is > much easier to debug using GDB and if something goes wrong it can easily be > restarted. > > When you have a working solution for webcamd, try to use the same solution > with the kernel. > > There is no simple 1:1 mapping for Linux APIs to FreeBSD APIs. Take for > example linux/list.h . You might think that a list can be re-implemented > and mapped to our sys/queue.h. But oh-no. Linux kernel code depends on all > the characteristics of list.h, how the structure members are stored and > named, and how foreach() macros complete with NULL or non-NULL in the > iterator. Further you'll find resistance among the Linux kernel developers > to support compilers different from GCC. I recently found a piece of code > in a header file, which works with GCC and causes a panic() when compiled > with clang. I reported it to one of the Linux kernel team members and they > didn't care about it. Even if you get everything compiling it doesn't it > will work :-( > > --HPS > > > On 06/04/17 16:35, blubee blubeeme wrote: > >> Hi Julian >> >> My goals are to port the Linux graphics stack over to FreeBSD w/o relying >> too heavily on the linuxkpi stuff. That's cool for a lot of use cases but >> it just seems a bit too brittle. >> >> It is a very large I understand the task will not be easy but I am willing >> to do the work, even from scratch if necessary although some help would be >> appreciated. >> >> I've been watching the Linux DRM project grow and while the top levels has >> changed, it's been a very long time since the actual low level stuff has >> been changed. Most of the diffs have shown changes in the >> [linux/driver/gpu/drm] layer which relies heavily on the >> [linux/include/drm] that does a lot of the heavy lifting here's a link to >> the latest version files: >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin >> ux.git/tree/include/drm?h=v4.12-rc3 >> >> here's a diff of the latest version of the [linux/driver/gpu/drm] : >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin >> ux.git/diff/?id=v4.12-rc3&id2=v4.12-rc2&dt=2 >> >> The diffs in the drivers change constantly but the lower level stuff >> hasn't >> changed as much. >> >> Doing some of the lower level translation to native FreeBSD style data >> structures then the upper part could be easily migrated, even with >> something as using AST to translate the headers to their FreeBSD >> equivalent >> without worrying about inadvertently breaking something or having major >> diffs that needs people to actively look at maintaining. >> >> That's a high level overview of my plan and what I'd like to achieve. Will >> it be easy, most likely not but once it's done FreeBSD will be just fine. >> >> Hope that helps clarify things for anyone who is interested. Any >> assistance >> would be greatly appreciated. >> >> Best, >> Owen >> >> On Sun, Jun 4, 2017 at 9:26 PM, Julian Elischer >> wrote: >> >> On 4/6/17 7:07 pm, blubee blubeeme wrote: >>> >>> Hello Is there anyone on either of these lists that have experience with both linux low level data structures and their equivalents on FreeBSD? For instance the linux header file: which includes the header file: Then looking at that file: >>> You are going to have to be a lot more specific about this. >>> I have worked in several places where they use s shim layer to make Linux >>> basic services work on freeBSD. >>> usually a mix of functions, macros and inlines. >>> However you need to narrow down your questions a bit as the POSSIBLE >>> scope >>> of your question is too large for anyone to
svnlite barfing when updating from repo
when I am update my ports repo like this svnlite co "https://svn.freebsd.org/ports/head"; "/usr/src/ports" svn: E155009: Failed to run the WC DB work queue associated with '/usr/home/FreeBSD/source/ports/head/net-im/mastodon/files', work item 132774 (file-remove net-im/mastodon/files/patch-bin_yarn) svn: E13: Can't remove file '/usr/home/FreeBSD/source/ports/head/net-im/mastodon/files/patch-bin_yarn': Permission denied What causes this? I am updating the repo as a regular user and not root and the directory has the proper perms. I am getting this after I update a repo ( i do this once a month ) and it was fine last moth and now I get multiple failures. After: rm -rf /usr/home/FreeBSD/source/ports/head/net-im/mastodon/files/; svnlite cleanup; svnlite co "https://svn.freebsd.org/ports/head"; "/usr/src/ports" It will run until it finds another perm problem so I have to shampoo,rinse,repeat until the local repo is finally updated ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
py-enchant and wxPython Dependency
Hi there, I have a webapp that is making use of textproc/py-enchant for spellchecking in some input forms we use. when i install py-enchant via pip it only requires some libraries that ship with textproc/enchant. yet when i install the py27-enchant pkg it looks like i have to slup in about 1GB of deps - including lots of X libraries (libGL for example). This seems to be related to having "USE_WX" flag set in the textproc/py-enchant Makefile. Since my use-case is for a python webapp I have no need for wxPython and it's dependency tree. Is there an easy way to re-build this port w/o the wxPython dependency? I can confirm the py-enchant works fine without wxPython when it is installed via pip inside a python venv. My understanding is that the USE_* flags are not really meant to be user-settable. Cheers, -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: py-enchant and wxPython Dependency
On 6/5/17 2:50 AM, Pete Wright wrote: > Hi there, > > I have a webapp that is making use of textproc/py-enchant for > spellchecking in some input forms we use. when i install py-enchant via > pip it only requires some libraries that ship with textproc/enchant. > yet when i install the py27-enchant pkg it looks like i have to slup in > about 1GB of deps - including lots of X libraries (libGL for example). > This seems to be related to having "USE_WX" flag set in the > textproc/py-enchant Makefile. > > Since my use-case is for a python webapp I have no need for wxPython and > it's dependency tree. Is there an easy way to re-build this port w/o > the wxPython dependency? I can confirm the py-enchant works fine > without wxPython when it is installed via pip inside a python venv. My > understanding is that the USE_* flags are not really meant to be > user-settable. > > Cheers, > > -pete > Hi Pete, If WX is optional (for enchant) then it should be made an OPTION to at least allow ports users to disable the dependency and its consequent features, and if you're a package user, the ability to create a custom package. This should take place as a request in Bugzilla (with rationale, etc) with a summary like: textproc/py-enchant: Make WX OPTION'al CC'ing port maintainer ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: py-enchant and wxPython Dependency
On 06/04/2017 09:54, Kubilay Kocak wrote: On 6/5/17 2:50 AM, Pete Wright wrote: Hi there, I have a webapp that is making use of textproc/py-enchant for spellchecking in some input forms we use. when i install py-enchant via pip it only requires some libraries that ship with textproc/enchant. yet when i install the py27-enchant pkg it looks like i have to slup in about 1GB of deps - including lots of X libraries (libGL for example). This seems to be related to having "USE_WX" flag set in the textproc/py-enchant Makefile. Since my use-case is for a python webapp I have no need for wxPython and it's dependency tree. Is there an easy way to re-build this port w/o the wxPython dependency? I can confirm the py-enchant works fine without wxPython when it is installed via pip inside a python venv. My understanding is that the USE_* flags are not really meant to be user-settable. Cheers, -pete Hi Pete, If WX is optional (for enchant) then it should be made an OPTION to at least allow ports users to disable the dependency and its consequent features, and if you're a package user, the ability to create a custom package. This should take place as a request in Bugzilla (with rationale, etc) with a summary like: textproc/py-enchant: Make WX OPTION'al CC'ing port maintainer Sounds great, I'm doing a build and test on our end now. Once I verify things work when the package is build w/o the wxPython dependency I'll file a PR as you suggest. Thanks! -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: svnlite barfing when updating from repo
--> svn: E13: Can't remove file '/usr/home/FreeBSD/source/ports/head/net-im/mastodon/files/patch-bin_yarn': Permission denied If you cannot remove the file, then you do not have the "proper" permissions in that directory -- not the top level, but at the leaf node (.../net-im/mastodon/files/). You need write permission on the immediate parent directory to remove a file. One other possibility -- if the sticky bit is set on the parent directory, ONLY the user that owns the file will be able to delete it. Beckman On Sun, 4 Jun 2017, Baho Utot wrote: when I am update my ports repo like this svnlite co "https://svn.freebsd.org/ports/head"; "/usr/src/ports" svn: E155009: Failed to run the WC DB work queue associated with '/usr/home/FreeBSD/source/ports/head/net-im/mastodon/files', work item 132774 (file-remove net-im/mastodon/files/patch-bin_yarn) svn: E13: Can't remove file '/usr/home/FreeBSD/source/ports/head/net-im/mastodon/files/patch-bin_yarn': Permission denied What causes this? I am updating the repo as a regular user and not root and the directory has the proper perms. I am getting this after I update a repo ( i do this once a month ) and it was fine last moth and now I get multiple failures. After: rm -rf /usr/home/FreeBSD/source/ports/head/net-im/mastodon/files/; svnlite cleanup; svnlite co "https://svn.freebsd.org/ports/head"; "/usr/src/ports" It will run until it finds another perm problem so I have to shampoo,rinse,repeat until the local repo is finally updated ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" --- Peter Beckman Internet Guy beck...@angryox.com http://www.angryox.com/ --- ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Upgrade PHP to 7.0
Are there any instructions explaining how to upgrade php from 5.6.30 to 7.0? Is it fairly straightforward? Or are there some gotchas one needs to know about? Paul Schmehl, Retired As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: svnlite barfing when updating from repo
On 06/04/17 13:11, Peter Beckman wrote: --> svn: E13: Can't remove file '/usr/home/FreeBSD/source/ports/head/net-im/mastodon/files/patch-bin_yarn': Permission denied If you cannot remove the file, then you do not have the "proper" permissions in that directory -- not the top level, but at the leaf node (.../net-im/mastodon/files/). You need write permission on the immediate parent directory to remove a file. One other possibility -- if the sticky bit is set on the parent directory, ONLY the user that owns the file will be able to delete it. This repository was created with svnlite co (etc) so how would all of a sudden it would incure these problems? I just got done fixing this repo again for this month and next month when I do a svnlite up I will see this again as it has happened every month from January to now. I do not change anything between update as I use rsync to copy it to a directory just for synth use. This repo only gets changed bu svnlite. This is quite aggravating as it it always multiple directories that have this issue. On Sun, 4 Jun 2017, Baho Utot wrote: when I am update my ports repo like this svnlite co "https://svn.freebsd.org/ports/head"; "/usr/src/ports" svn: E155009: Failed to run the WC DB work queue associated with '/usr/home/FreeBSD/source/ports/head/net-im/mastodon/files', work item 132774 (file-remove net-im/mastodon/files/patch-bin_yarn) svn: E13: Can't remove file '/usr/home/FreeBSD/source/ports/head/net-im/mastodon/files/patch-bin_yarn': Permission denied What causes this? I am updating the repo as a regular user and not root and the directory has the proper perms. I am getting this after I update a repo ( i do this once a month ) and it was fine last moth and now I get multiple failures. After: rm -rf /usr/home/FreeBSD/source/ports/head/net-im/mastodon/files/; svnlite cleanup; svnlite co "https://svn.freebsd.org/ports/head"; "/usr/src/ports" It will run until it finds another perm problem so I have to shampoo,rinse,repeat until the local repo is finally updated ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
[Default] On Sun, 04 Jun 2017 12:10:46 -0500, Paul Schmehl wrote: >Are there any instructions explaining how to upgrade php from 5.6.30 to >7.0? Is it fairly straightforward? Or are there some gotchas one needs to >know about? php.net has some info, but if you're not doing anything fancy you shouldn't have any trouble. I always mind Tony Hoare's advice and avoid the fancy stuff, so when I installed 7.0 instead of 5.6 everything ran fine. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
--On June 4, 2017 at 2:42:51 PM -0400 scratch65...@att.net wrote: [Default] On Sun, 04 Jun 2017 12:10:46 -0500, Paul Schmehl wrote: Are there any instructions explaining how to upgrade php from 5.6.30 to 7.0? Is it fairly straightforward? Or are there some gotchas one needs to know about? php.net has some info, but if you're not doing anything fancy you shouldn't have any trouble. I always mind Tony Hoare's advice and avoid the fancy stuff, so when I installed 7.0 instead of 5.6 everything ran fine. Unfortunately, I had a problem. PHP Fatal error: Uncaught Error: Call to undefined function mysql_connect() I noticed that there was no php70-mysql extension any more. Is there something that replaces that? Paul Schmehl, Retired As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
Hi! > PHP Fatal error: Uncaught Error: Call to undefined function > mysql_connect() > > I noticed that there was no php70-mysql extension any more. Is there > something that replaces that? databases/php70-mysqli Btw, you can migrate to php71, as well. Not much difference. -- p...@opsec.eu+49 171 3101372 3 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
--On June 4, 2017 at 9:28:29 PM +0200 Kurt Jaeger wrote: Hi! PHP Fatal error: Uncaught Error: Call to undefined function mysql_connect() I noticed that there was no php70-mysql extension any more. Is there something that replaces that? databases/php70-mysqli Btw, you can migrate to php71, as well. Not much difference. That was installed. Is there a configuration option that needs to be set or changed? Paul Schmehl, Retired As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
mysql_connect is obsolete in php 7+, you need to change your code to use mysqli_connect. On Sun, Jun 4, 2017 at 12:39 PM, Paul Schmehl wrote: > --On June 4, 2017 at 9:28:29 PM +0200 Kurt Jaeger wrote: > >> Hi! >> >>> PHP Fatal error: Uncaught Error: Call to undefined function >>> mysql_connect() >>> >>> I noticed that there was no php70-mysql extension any more. Is there >>> something that replaces that? >> >> >> databases/php70-mysqli >> >> Btw, you can migrate to php71, as well. Not much difference. > > > That was installed. Is there a configuration option that needs to be set or > changed? > > Paul Schmehl, Retired > As if it wasn't already obvious, my opinions > are my own and not those of my employer. > *** > "It is as useless to argue with those who have > renounced the use of reason as to administer > medication to the dead." Thomas Jefferson > "There are some ideas so wrong that only a very > intelligent person could believe in them." George Orwell > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
--On June 4, 2017 at 12:40:43 PM -0700 "Jack L." wrote: mysql_connect is obsolete in php 7+, you need to change your code to use mysqli_connect. Oh, that sucks. This server is running both Joomla and Wordpress. Joomla has been complaining about updating php to 70, so I thought I'd give it a shot. Don't know if Wordpress is compatible or not. I just installed php71 after reverting back to php56. We'll see if everything works or not. Paul Schmehl, Retired As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
--On June 4, 2017 at 12:40:43 PM -0700 "Jack L." wrote: mysql_connect is obsolete in php 7+, you need to change your code to use mysqli_connect. The site is up and running on php71 and both Joomla and Wordpress are working fine. I don't know if I did something wrong in php70 or not. I know I had mysqli configured in php70-extensions. Oh well, it's working fine now. Thanks for all the responses. Paul Schmehl, Retired As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
On 04.06.2017 22:39, Paul Schmehl wrote: --On June 4, 2017 at 9:28:29 PM +0200 Kurt Jaeger wrote: Hi! PHP Fatal error: Uncaught Error: Call to undefined function mysql_connect() I noticed that there was no php70-mysql extension any more. Is there something that replaces that? databases/php70-mysqli Btw, you can migrate to php71, as well. Not much difference. That was installed. Is there a configuration option that needs to be set or changed? You must fix the code and migrate to mysqli or pdo, mysql was deprecated for more than 5 years. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
On 04.06.2017 21:42, scratch65...@att.net wrote: [Default] On Sun, 04 Jun 2017 12:10:46 -0500, Paul Schmehl wrote: Are there any instructions explaining how to upgrade php from 5.6.30 to 7.0? Is it fairly straightforward? Or are there some gotchas one needs to know about? php.net has some info, but if you're not doing anything fancy you shouldn't have any trouble. I always mind Tony Hoare's advice and avoid the fancy stuff, so when I installed 7.0 instead of 5.6 everything ran fine. As OP problem was solved, it's time to hijack the thread a little :) I'm considering to migrate as well, what is recommended path for upgrade ? Uninstall all php56 ports or replace them (I believe, -o key in portmaster). ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
--On June 4, 2017 at 11:20:20 PM +0300 abi wrote: On 04.06.2017 21:42, scratch65...@att.net wrote: As OP problem was solved, it's time to hijack the thread a little :) I'm considering to migrate as well, what is recommended path for upgrade ? Uninstall all php56 ports or replace them (I believe, -o key in portmaster). Here's what I did. portmaster -o lang/php71 lang/php56 That upgrades php. Then I removed all the php56-extensions: pkg-delete php56-\* mod_php56 php56-extensions And then installed the php71-extensions. cd /usr/ports/lang/php71-extensions make config make install clean Make sure you make a list of all the installed php56-extensions so you can select the same ones in php71-extensions. Paul Schmehl, Retired As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Hosting distfiles on HTTPS w/Let's Encrypt - how? [somehow solved]
On Thu, 1 Jun 2017, Marcin Cieslak wrote:
> => Attempting to fetch
> https://distfile.net/local-ports-distfiles/INIT.2014-12-24.tgz
> Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt
> Authority X3
> 34374329736:error:14090086:SSL
> routines:ssl3_get_server_certificate:certificate verify
> failed:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1264:
> fetch: https://distfile.net/local-ports-distfiles/INIT.2014-12-24.tgz:
> Authentication error
My temporary solution to this problem is to pin the CA certificate in the port
itself:
commit 7eec5787c09565b0b2dfc4b2cee176c8509474b2
Author: Marcin Cieślak
Date: Sun Jun 4 21:31:22 2017 +
Hardwire CA certificate to facilitate HTTPS downloads
Ports do not have a public key infrastructure to facilitate
ports that need to be fetched using https only.
So we hardcode a root certificate used by Let's Encrypt
for now.
diff --git a/shells/ksh93/Makefile b/shells/ksh93/Makefile
index 10f826c..c1ddef2 100644
--- a/shells/ksh93/Makefile
+++ b/shells/ksh93/Makefile
@@ -24,7 +24,7 @@ LICENSE= EPL
OPTIONS_DEFINE=EXAMPLES STATIC
-FETCH_ENV= HTTP_AUTH=basic:*:I\ accept\ www.opensource.org/licenses/cpl:.
+FETCH_ARGS+= --ca-cert="${FILESDIR}/dst_root_ca_x3.crt"
LDFLAGS+= -lm
MAKE_ENV= CCFLAGS="${CFLAGS}"
NO_WRKSUBDIR= yes
diff --git a/shells/ksh93/files/dst_root_ca_x3.crt
b/shells/ksh93/files/dst_root_ca_x3.crt
new file mode 100644
index 000..e2bd36f
--- /dev/null
+++ b/shells/ksh93/files/dst_root_ca_x3.crt
@@ -0,0 +1,22 @@
+subject=/O=Digital Signature Trust Co./CN=DST Root CA X3
+issuer=/O=Digital Signature Trust Co./CN=DST Root CA X3
+-BEGIN CERTIFICATE-
+MIIDSjCCAjKgAwIBAgIQRK+wgNajJ7qJMDmGLvhAazANBgkqhkiG9w0BAQUFADA/
+MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT
+DkRTVCBSb290IENBIFgzMB4XDTAwMDkzMDIxMTIxOVoXDTIxMDkzMDE0MDExNVow
+PzEkMCIGA1UEChMbRGlnaXRhbCBTaWduYXR1cmUgVHJ1c3QgQ28uMRcwFQYDVQQD
+Ew5EU1QgUm9vdCBDQSBYMzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
+AN+v6ZdQCINXtMxiZfaQguzH0yxrMMpb7NnDfcdAwRgUi+DoM3ZJKuM/IUmTrE4O
+rz5Iy2Xu/NMhD2XSKtkyj4zl93ewEnu1lcCJo6m67XMuegwGMoOifooUMM0RoOEq
+OLl5CjH9UL2AZd+3UWODyOKIYepLYYHsUmu5ouJLGiifSKOeDNoJjj4XLh7dIN9b
+xiqKqy69cK3FCxolkHRyxXtqqzTWMIn/5WgTe1QLyNau7Fqckh49ZLOMxt+/yUFw
+7BZy1SbsOFU5Q9D8/RhcQPGX69Wam40dutolucbY38EVAjqr2m7xPi71XAicPNaD
+aeQQmxkqtilX4+U9m5/wAl0CAwEAAaNCMEAwDwYDVR0TAQH/BAUwAwEB/zAOBgNV
+HQ8BAf8EBAMCAQYwHQYDVR0OBBYEFMSnsaR7LHH62+FLkHX/xBVghYkQMA0GCSqG
+SIb3DQEBBQUAA4IBAQCjGiybFwBcqR7uKGY3Or+Dxz9LwwmglSBd49lZRNI+DT69
+ikugdB/OEIKcdBodfpga3csTS7MgROSR6cz8faXbauX+5v3gTt23ADq1cEmv8uXr
+AvHRAosZy5Q6XkjEGB5YGV8eAlrwDPGxrancWYaLbumR9YbK+rlmM6pZW87ipxZz
+R8srzJmwN0jP41ZL9c8PDHIyh8bwRLtTcm1D9SZImlJnt1ir/md2cXjbDaJWFBM5
+JDGFoqgCWjBH4d1QB7wCCZAA62RjYJsWvIjJEubSfZGL+T0yjWW06XyxV3bqxbYo
+Ob8VZRzI9neWagqNdwvYkQsEjgfbKbYK7p2CNTUQ
+-END CERTIFICATE-
https://github.com/saper/ports-exp/commit/7eec5787c09565b0b2dfc4b2cee176c8509474b2
smime.p7s
Description: S/MIME Cryptographic Signature
