Hi
On Wednesday, May 9, 2018, Boris Samorodov wrote:
> Hi All,
>
> I use self-built base packages. How can I test/use drm-next-kmod?
> Packages for kernel and drm-nex-kmod are in conflict:
> -
> ╰→ sudo pkg install drm-next-kmod-4.11.g20180224
>
> Updating FreeBSD-base repository catalogue..
On Wed, May 09, 2018 at 10:06:19AM +0200, Niclas Zeising wrote:
On 05/08/18 22:09, Manuel Stühn wrote:
P.S.
I'm useing drm-stable-kmod, drm-next-kmod did not work for me.
What issues are you seeing with drm-next-kmod?
I mixed my machines up. The one showing problems with drm-next was the
On Thu, May 10, 2018 at 2:45 AM, Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
> In review PR 228007, it came to my attention some individuals are
> mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD
> issue". See
>
> https://lists.freebsd.org/pipermail/freebsd-fortran/201
On Thu, May 10, 2018 at 10:46:31AM +0300, Gleb Popov wrote:
> On Thu, May 10, 2018 at 2:45 AM, Steve Kargl <
> s...@troutmask.apl.washington.edu> wrote:
>
> > In review PR 228007, it came to my attention some individuals are
> > mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD
> >
On Thu, May 10, 2018 at 10:24:52AM -0400, Diane Bruce wrote:
> On Thu, May 10, 2018 at 10:46:31AM +0300, Gleb Popov wrote:
> > On Thu, May 10, 2018 at 2:45 AM, Steve Kargl <
> > s...@troutmask.apl.washington.edu> wrote:
> >
> > > In review PR 228007, it came to my attention some individuals are
>
On 05/10/18 03:45, Johannes Dieterich wrote:
Hi
On Wednesday, May 9, 2018, Boris Samorodov wrote:
Hi All,
I use self-built base packages. How can I test/use drm-next-kmod?
Packages for kernel and drm-nex-kmod are in conflict:
-
Checking integrity... done (1 conflicting)
- drm-next-kmod-
On Thu, May 10, 2018 at 5:30 PM, Theron wrote:
> On 05/10/18 03:45, Johannes Dieterich wrote:
>
>> Hi
>>
>> On Wednesday, May 9, 2018, Boris Samorodov wrote:
>>
>>> Hi All,
>>>
>>> I use self-built base packages. How can I test/use drm-next-kmod?
>>> Packages for kernel and drm-nex-kmod are in co
On Wed, 9 May 2018 16:45:51 -0700 Steve Kargl
wrote:
> In review PR 228007, it came to my attention some individuals are
> mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD
> issue". See
>
> https://lists.freebsd.org/pipermail/freebsd-fortran/2018-May/000124.html
>
> The proble
On Thu, May 10, 2018 at 08:15:22AM -0700, Steve Kargl wrote:
> On Thu, May 10, 2018 at 10:24:52AM -0400, Diane Bruce wrote:
> > On Thu, May 10, 2018 at 10:46:31AM +0300, Gleb Popov wrote:
> > > On Thu, May 10, 2018 at 2:45 AM, Steve Kargl <
> > > s...@troutmask.apl.washington.edu> wrote:
> > >
...
On Thu, May 10, 2018 at 06:21:51PM +0200, Tijl Coosemans wrote:
> On Wed, 9 May 2018 16:45:51 -0700 Steve Kargl
> wrote:
> >
> > So, the runtime loader finds 6 instead of 716, tries to link,
> > fails, and issues an error message. There are a number ways to
> > fix this issue.
> >
> > 1) By f
just another - out of thousands - example that shared libraries are one
of the worst thing invented in computing.
Maybe except of single system wide shared library with constant interface.
On Thu, 10 May 2018, Gleb Popov wrote:
On Thu, May 10, 2018 at 2:45 AM, Steve Kargl <
s...@troutmask.apl.
On Wed, May 09, 2018 at 04:45:51PM -0700, Steve Kargl wrote:
> In review PR 228007, it came to my attention some individuals are
> mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD
> issue". See
It seems we've had the same discussion 2 years ago. My time flies.
ttps://lists.freeb
12 matches
Mail list logo