public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] apache: Update to 2.4.38
Date: Sat, 09 Feb 2019 21:04:01 +0100	[thread overview]
Message-ID: <c7fa971a-29d8-554e-e234-74df7651ca9c@ipfire.org> (raw)
In-Reply-To: <3F4CDFFE-F1D3-48B3-9D72-AE49E81C4C6B@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 461 bytes --]

Hi,

Just FYI:
Problems are gone after upgrading to Core 127. Worked without problems.

On 05.02.2019 21:57, Michael Tremer wrote:
> Well in that case, are you sure that your hardware supports SSE2?

Yes, it does:
http://www.cpu-world.com/CPUs/Celeron_Dual-Core/Intel-Mobile%20Celeron%202957U.html

I didn't touch the 'apache 2.4.38'-installation - now its running
without problems with 'openssl 1.1.0j'. '1.1.0i' is gone...

Best,
Matthias



      parent reply	other threads:[~2019-02-09 20:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01 17:06 Matthias Fischer
2019-02-01 17:13 ` Michael Tremer
2019-02-01 17:44   ` Matthias Fischer
2019-02-01 17:47     ` Michael Tremer
2019-02-01 18:07       ` Matthias Fischer
2019-02-04 22:20         ` Michael Tremer
2019-02-05 17:24           ` Matthias Fischer
2019-02-05 17:30             ` Michael Tremer
2019-02-05 17:45               ` Matthias Fischer
2019-02-05 20:57                 ` Michael Tremer
2019-02-06 17:32                   ` Matthias Fischer
2019-02-06 17:45                     ` Michael Tremer
2019-02-06 17:53                       ` Matthias Fischer
2019-02-09 20:04                   ` Matthias Fischer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c7fa971a-29d8-554e-e234-74df7651ca9c@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox