From: Marcel Lorenz <lorenz.marcel@web.de>
To: development@lists.ipfire.org
Subject: Re: Planning out Core Update 117
Date: Sat, 18 Nov 2017 08:44:54 +0100 [thread overview]
Message-ID: <baf42a869f8043f3c546151561676dc3@web.de> (raw)
In-Reply-To: <8f2eeaf8-8001-2eb1-b15c-2b755b432b15@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3618 bytes --]
Hi Matthias, hi Michael,
my test images work with this configure warnings. I think, we can
certain remove
this old switches. I will send v2 patches for gmp/e2fsprogs and a
cleanup patch for mpfr.
Some other packages brings this warnings: autoconf, automake, gzip,
libtool, m4, patch
Best,
Marcel
Am 2017-11-17 20:37, schrieb Matthias Fischer:
> Hi,
>
> On 17.11.2017 13:59, Matthias Fischer wrote:
>> Hi,
>>
>> On 07.11.2017 11:44, Michael Tremer wrote:
>>> ...
>>> Could you also please review at least some of the patches that Marcel
>>> sent
>>> last week?
>>> ...
>>
>> Done.
>>
>> Applied all patches (19 commits) from '2017-10-31' against the current
>> 'next':
>>
>> ***SNIP***
>> ...
>> On branch next
>> Changes not staged for commit:
>> (use "git add <file>..." to update what will be committed)
>> (use "git checkout -- <file>..." to discard changes in working
>> directory)
>>
>> modified: config/rootfiles/common/boost
>> modified: config/rootfiles/common/cmake
>> modified: config/rootfiles/common/e2fsprogs
>> modified: config/rootfiles/common/expat
>> modified: config/rootfiles/common/gawk
>> modified: config/rootfiles/common/glib
>> modified: config/rootfiles/common/libarchive
>> modified: config/rootfiles/common/libupnp
>> modified: config/rootfiles/common/libxml2
>> modified: config/rootfiles/common/libxslt
>> modified: config/rootfiles/common/mpfr
>> modified: config/rootfiles/common/pciutils
>> modified: config/rootfiles/common/tcl
>> modified: config/rootfiles/common/texinfo
>> modified: config/rootfiles/common/xfsprogs
>> modified: config/rootfiles/packages/minidlna
>> modified: config/rootfiles/packages/nmap
>> modified: config/rootfiles/packages/stunnel
>> modified: lfs/boost
>> modified: lfs/cmake
>> modified: lfs/e2fsprogs
>> modified: lfs/expat
>> modified: lfs/gawk
>> modified: lfs/glib
>> modified: lfs/libarchive
>> modified: lfs/libupnp
>> modified: lfs/libxml2
>> modified: lfs/libxslt
>> modified: lfs/minidlna
>> modified: lfs/mpfr
>> modified: lfs/nmap
>> modified: lfs/pciutils
>> modified: lfs/rpcbind
>> modified: lfs/stunnel
>> modified: lfs/tcl
>> modified: lfs/texinfo
>> modified: lfs/xfsprogs
>>
>> Untracked files:
>> (use "git add <file>..." to include in what will be committed)
>>
>> src/patches/rpcbind-0.2.4-vulnerability_fixes-1.patch
>> ...
>> ***SNAP***
>>
>> Results:
>>
>> Source for 'e2fsprogs 1.43.6' were missing, copied them to
>> git.ipfire.org. No problem.
>> Besides, in the meantime there's an update to '1.43.7', will test that
>> with a clean build, too.
>>
>> 'poppler 0.52.0' is complaining:
>>
>> Changes in poppler-0.52.0 check rootfile! [see attachment]
>>
>> Besides that, building was ok for now.
>
> Final results:
>
> All patches applied - 'poppler 0.52.0' needs rootfile fix.
>
> The 'e2fsprogs'-update to 1.43.7 also applied - no further changes seem
> to be necessary for this update so far.
>
> @Marcel: would you do these changes or shall I?
>
> Found by chance:
>
> I found about 70 'configure: WARNING: unrecognized
> options:'-notifications in '_build.base.log' and 'build.ipfire.log'.
>
> These deal with '--enable-mpbsd', '--disable-nls' (gmp-6.1.2,
> mpfr-3.1.6, e.g.), '--disable-evms', --enable-multibyte'
> '--enable-zlib', '--disable-static' , '--disable-kernel-module' and so
> on.
>
> I don't know why these option switches are still included or why they
> exist, but: shouldn't we take a look at this?
>
> Best,
> Matthias
--
Gesendet mit Roundcube
next prev parent reply other threads:[~2017-11-18 7:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 18:32 Michael Tremer
2017-11-06 21:06 ` Matthias Fischer
2017-11-07 10:44 ` Michael Tremer
2017-11-17 12:59 ` Matthias Fischer
2017-11-17 19:37 ` Matthias Fischer
2017-11-17 21:25 ` Michael Tremer
2017-11-17 23:15 ` Matthias Fischer
2017-11-18 7:44 ` Marcel Lorenz [this message]
2017-11-06 21:09 ` Matthias Fischer
2017-11-07 10:46 ` Michael Tremer
2017-11-07 15:05 ` Michael Tremer
2017-11-07 18:41 ` Matthias Fischer
2017-11-07 22:47 ` Michael Tremer
2017-11-21 14:42 ` Michael Tremer
2017-11-21 17:35 ` Matthias Fischer
2017-11-22 16:37 ` Michael Tremer
2018-01-29 13:23 ` Compress images with XZ (was: Planning out Core Update 117) Michael Tremer
2018-01-30 16:47 ` Compress images with XZ Matthias Fischer
2018-01-30 20:03 ` Michael Tremer
2018-02-03 19:44 ` Matthias Fischer
2018-02-03 21:09 ` Matthias Fischer
2018-02-06 1:05 ` Michael Tremer
2018-02-11 15:35 ` Matthias Fischer
2018-02-11 19:57 ` Michael Tremer
2018-05-11 20:27 ` Michael Tremer
2018-05-12 0:35 ` Tom Rymes
2018-05-12 8:48 ` Michael Tremer
2018-05-12 14:14 ` Matthias Fischer
2018-05-12 19:40 ` Michael Tremer
2017-11-10 11:01 ` Planning out Core Update 117 ummeegge
2017-11-10 12:18 ` Michael Tremer
2017-11-10 13:35 ` ummeegge
[not found] <7EA8C1E7-14CC-4906-9688-504DA016795D@gmx.com>
2017-11-10 15:36 ` ummeegge
2017-11-18 20:53 ` Horace Michael
2017-11-21 10:25 ` ummeegge
2017-11-21 11:49 ` Michael Tremer
2017-11-21 12:30 ` Horace Michael
2017-11-22 10:30 ummeegge
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=baf42a869f8043f3c546151561676dc3@web.de \
--to=lorenz.marcel@web.de \
--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