subject:"\[S\-mailx\] why s\-nail contains the build info"

Re: [S-mailx] why s-nail contains the build info

2022-07-27 Thread Steffen Nurpmeso

Hey,

Steffen Nurpmeso wrote in
 <20220727153802._gh84%stef...@sdaoden.eu>:
 |Yu, Mingli wrote in
 | <53fa174d-64f0-183e-5ea9-d027a3faa...@windriver.com>:
 ||Actually I'm just wondering how to make the binary /usr/bin/s-nail not 
 ||include the below info.
 ...
 |I will add configuration for that today, something like
 ...

With credits to you

  # Optional, for packagers who do not want to include build information
  # in the binary: if set non-empty this ends up in the INTERNAL VARIABLES
  # *build-rest*, and *build-cc* as well as *build-ld* will be empty.
  # Please set your own VAL_CONTACT_{MAIL,WEB} if you set this, and/or
  # include enough information to make bug reports linkable to package
  # recipes and the used build environment.
  VAL_BUILD_INFO=

I hope this helps,
Ciao from Germany,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [S-mailx] why s-nail contains the build info

2022-07-27 Thread Steffen Nurpmeso

Hello Mingli.

Yu, Mingli wrote in
 <53fa174d-64f0-183e-5ea9-d027a3faa...@windriver.com>:
 |Thanks very much for your respond!
 |
 |Actually I'm just wondering how to make the binary /usr/bin/s-nail not 
 |include the below info.

I will add configuration for that today, something like
VAL_BUILD_INFO=VALUE: if set it is used for the $build-cc and
$build-ld variables (and hoping the compiler/linker merges the
strings), and $build-rest will be empty.
It would be nice if the OpenEmbedded package recipe would set
their own VAL_CONTACT_MAIL and VAL_CONTACT_WEB in return, like

  EXTRA_OEMAKE += "VAL_BUILD_INFO=OE-SPECIFIC-ID ie 14.9.24-r0
   VAL_CONTACT_MAIL=??
   VAL_CONTACT_WEB=https://bugzilla.yoctoproject.org/;

But anyway include the real recipe version in VAL_BUILD_INFO.
(I do not see where the -r0 in "14.9.24-r0" comes from.)
(And while there, you could simply drop
0001-make.rc-set-VAL_MTA.patch if you want to, it can simply be
added as VAL_MTA=/usr/sbin/sendmail like the above.)

Does this sound ok for you?

Ciao from Germany,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [S-mailx] why s-nail contains the build info

2022-07-26 Thread Yu, Mingli


Hi Steffen,

Thanks very much for your respond!

Actually I'm just wondering how to make the binary /usr/bin/s-nail not 
include the below info.


https://www.sdaoden.eu/code.html^@^@^@^@s-mailx@lists.sdaoden.eu^@^@^@^@VAL_SYSCONFDIR=/etc 
VAL_MANDIR=/usr/share/man VAL_LIBEXECDIR=/usr/libexec 
VAL_BINDIR=/usr/bin VAL_PREFIX=/usr strip=true 
OBJDIR=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/build 
OPT_CROSS_BUILD=yes OPT_AUTOCC=no CONFIG=minimal 
VERBOSE=yes^@^@^@^@Linux^@^@^@i686-wrs-linux-gcc -m32 -march=core2 
-mtune=core2 -msse3 -mfpmath=sse -fstack-protector-strong -O2 
-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security 
--sysroot=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot 
-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed 
-fmacro-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0=/usr/src/debug/s-nail/14.9.24-r0

-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0=/usr/src/debug/s-nail/14.9.24-r0
-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot=
-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot-native= 
 -Wl,-z,relro,-z,now ^@^@^@^@^@^@^@^@^@^@^@^@^@i686-wrs-linux-gcc -m32 
-march=core2 -mtune=core2 -msse3 -mfpmath=sse -fstack-protector-strong 
-O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security 
-Werror=format-security 
--sysroot=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot 
-DNDEBUG -O2 -pipe -g -feliminate-unused-debug-types 
-fmacro-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0=/usr/src/debug/s-nail/14.9.24-r0 
-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0=/usr/src/debug/s-nail/14.9.24-r0 
-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot= 
-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot-native=

@i686-wrs-linux-gcc (GCC) 12.1.0
@Copyright (C) 2022 Free Software Foundation, Inc.
@This is free software; see the source for copying conditions.  There is NO
@warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.^@^@^@^@^@^@^@^@^@^@^@^@disc^@^@N^



Thanks,

On 7/27/22 00:43, Steffen Nurpmeso wrote:

[Please note: This e-mail is from an EXTERNAL e-mail address]

Hello Mingli Yu!

Yu, Mingli wrote in
  <636625a5-5473-bf7d-f648-e052c6c47...@windriver.com>:
  |I'm building s-nail form the source and found the s-nail include below
  |info via "vi /usr/bin/s-nail", any hints?

Ah, but this little software is no rocket science :)
I still have not mentioned that Windriver Linux ships this, it is
because i thought it all comes in via OpenEmbedded (and i have
your email in an "alias mailx-openembedded" for an emergency
notification that never will happen).  So Windriver has s-nail you
say?

And i hope your vi(1) can deal with all the control sequences.
I include the info for possibly happening bug reports, for

  s-nail -:/ -X 'set verbose;version;x'

output, or as shown in "BUGS" of the manual.
Actually it is an iteration of what was included earlier, after
a discussion on some Debian list in 2018 ("Rant about Debian
reproducibility environment", [1], my final thoughts then in [2]).

   [1] https://lists.debian.org/debian-devel/2018/03/threads.html#00036
   [2] https://lists.debian.org/debian-devel/2018/03/msg00078.html

   ...
  |VAL_SYSCONFDIR=/etc
  |VAL_MANDIR=/usr/share/man VAL_LIBEXECDIR=/usr/libexec
  |VAL_BINDIR=/usr/bin VAL_PREFIX=/usr strip=true
  |OBJDIR=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/build
  |OPT_CROSS_BUILD=yes OPT_AUTOCC=no CONFIG=minimal

Looking here, "minimal" is so .. minimal.  (VAL_MTA via patch is
really not necessary.)

  |VERBOSE=yes^@^@^@^@Linux^@^@^@i686-wrs-linux-gcc -m32 -march=core2
  |-mtune=core2 -msse3 -mfpmath=sse -fstack-protector-strong -O2
  |-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security
  |--sysroot=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/rec\
  |ipe-sysroot
  |-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed
  |-fmacro-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
  |24-r0=/usr/src/debug/s-nail/14.9.24-r0
  |
  |-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
  |24-r0=/usr/src/debug/s-nail/14.9.24-r0
  |
  |-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
  |24-r0/recipe-sysroot=
  |
  |-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
  |24-r0/recipe-sysroot-native=
  |  -Wl,-z,relro,-z,now ^@^@^@^@^@^@^@^@^@^@^@^@^@i686-wrs-linux-gcc -m32
  |-march=core2 -mtune=core2 -msse3 -mfpmath=sse -fstack-protector-strong
  |-O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security
  |-Werror=format-security
  |--sysroot=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/rec\
  |ipe-sysroot
  |-DNDEBUG -O2 -pipe -g

Re: [S-mailx] why s-nail contains the build info

2022-07-26 Thread Steffen Nurpmeso

Hello Mingli Yu!

Yu, Mingli wrote in
 <636625a5-5473-bf7d-f648-e052c6c47...@windriver.com>:
 |I'm building s-nail form the source and found the s-nail include below 
 |info via "vi /usr/bin/s-nail", any hints?

Ah, but this little software is no rocket science :)
I still have not mentioned that Windriver Linux ships this, it is
because i thought it all comes in via OpenEmbedded (and i have
your email in an "alias mailx-openembedded" for an emergency
notification that never will happen).  So Windriver has s-nail you
say?

And i hope your vi(1) can deal with all the control sequences.
I include the info for possibly happening bug reports, for

 s-nail -:/ -X 'set verbose;version;x'

output, or as shown in "BUGS" of the manual.
Actually it is an iteration of what was included earlier, after
a discussion on some Debian list in 2018 ("Rant about Debian
reproducibility environment", [1], my final thoughts then in [2]).

  [1] https://lists.debian.org/debian-devel/2018/03/threads.html#00036
  [2] https://lists.debian.org/debian-devel/2018/03/msg00078.html

  ...
 |VAL_SYSCONFDIR=/etc 
 |VAL_MANDIR=/usr/share/man VAL_LIBEXECDIR=/usr/libexec 
 |VAL_BINDIR=/usr/bin VAL_PREFIX=/usr strip=true 
 |OBJDIR=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/build 
 |OPT_CROSS_BUILD=yes OPT_AUTOCC=no CONFIG=minimal 

Looking here, "minimal" is so .. minimal.  (VAL_MTA via patch is
really not necessary.)

 |VERBOSE=yes^@^@^@^@Linux^@^@^@i686-wrs-linux-gcc -m32 -march=core2 
 |-mtune=core2 -msse3 -mfpmath=sse -fstack-protector-strong -O2 
 |-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security 
 |--sysroot=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/rec\
 |ipe-sysroot 
 |-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed 
 |-fmacro-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
 |24-r0=/usr/src/debug/s-nail/14.9.24-r0 
 | 
 |-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
 |24-r0=/usr/src/debug/s-nail/14.9.24-r0 
 | 
 |-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
 |24-r0/recipe-sysroot= 
 | 
 |-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
 |24-r0/recipe-sysroot-native= 
 |  -Wl,-z,relro,-z,now ^@^@^@^@^@^@^@^@^@^@^@^@^@i686-wrs-linux-gcc -m32 
 |-march=core2 -mtune=core2 -msse3 -mfpmath=sse -fstack-protector-strong 
 |-O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security 
 |-Werror=format-security 
 |--sysroot=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/rec\
 |ipe-sysroot 
 |-DNDEBUG -O2 -pipe -g -feliminate-unused-debug-types 
 |-fmacro-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
 |24-r0=/usr/src/debug/s-nail/14.9.24-r0 
 |-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
 |24-r0=/usr/src/debug/s-nail/14.9.24-r0 
 |-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
 |24-r0/recipe-sysroot= 
 |-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.\
 |24-r0/recipe-sysroot-native= 

If it works and the tests are ok, i would consider offering
packagers an option to leave these bytes off the binary.  Well
i mean maybe, as in the Debian thread.  As of today you would have
to patch mk/make-config.sh hard (search for "Create the string
that is used by *features* and the version command.").

 |@i686-wrs-linux-gcc (GCC) 12.1.0
 |@Copyright (C) 2022 Free Software Foundation, Inc.
 |@This is free software; see the source for copying conditions.  There is NO
 |@warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
 |PURPOSE.^@^@^@^@^@^@^@^@^@^@^@^@disc^@^@N^
 |
 |Thanks,

Greetings to China.  Since the west does not really have a face to
loose, any communication is appreciated.

 --End of <636625a5-5473-bf7d-f648-e052c6c47...@windriver.com>

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

[S-mailx] why s-nail contains the build info

2022-07-26 Thread Yu, Mingli


Hi,

I'm building s-nail form the source and found the s-nail include below 
info via "vi /usr/bin/s-nail", any hints?


https://www.sdaoden.eu/code.html^@^@^@^@s-mailx@lists.sdaoden.eu^@^@^@^@VAL_SYSCONFDIR=/etc 
VAL_MANDIR=/usr/share/man VAL_LIBEXECDIR=/usr/libexec 
VAL_BINDIR=/usr/bin VAL_PREFIX=/usr strip=true 
OBJDIR=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/build 
OPT_CROSS_BUILD=yes OPT_AUTOCC=no CONFIG=minimal 
VERBOSE=yes^@^@^@^@Linux^@^@^@i686-wrs-linux-gcc -m32 -march=core2 
-mtune=core2 -msse3 -mfpmath=sse -fstack-protector-strong -O2 
-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security 
--sysroot=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot 
-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed 
-fmacro-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0=/usr/src/debug/s-nail/14.9.24-r0 

-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0=/usr/src/debug/s-nail/14.9.24-r0 

-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot= 

-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot-native= 
 -Wl,-z,relro,-z,now ^@^@^@^@^@^@^@^@^@^@^@^@^@i686-wrs-linux-gcc -m32 
-march=core2 -mtune=core2 -msse3 -mfpmath=sse -fstack-protector-strong 
-O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security 
-Werror=format-security 
--sysroot=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot 
-DNDEBUG -O2 -pipe -g -feliminate-unused-debug-types 
-fmacro-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0=/usr/src/debug/s-nail/14.9.24-r0 
-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0=/usr/src/debug/s-nail/14.9.24-r0 
-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot= 
-fdebug-prefix-map=/build/tmp-glibc/work/core2-32-wrs-linux/s-nail/14.9.24-r0/recipe-sysroot-native= 


@i686-wrs-linux-gcc (GCC) 12.1.0
@Copyright (C) 2022 Free Software Foundation, Inc.
@This is free software; see the source for copying conditions.  There is NO
@warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.^@^@^@^@^@^@^@^@^@^@^@^@disc^@^@N^



Thanks,

Re: [S-mailx] why s-nail contains the build info

Re: [S-mailx] why s-nail contains the build info

Re: [S-mailx] why s-nail contains the build info

Re: [S-mailx] why s-nail contains the build info

[S-mailx] why s-nail contains the build info

5 matches

Site Navigation

Mail list logo

Footer information