All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2, 1/1] package/monit: fix openssl static build
Date: Sun, 03 Dec 2023 17:44:02 +0100	[thread overview]
Message-ID: <875y1f1bjh.fsf@48ers.dk> (raw)
In-Reply-To: <20231201210645.781257-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Fri, 1 Dec 2023 22:06:45 +0100")

>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:

 > --with-ssl-dir will exclusively search for dynamic library so use
 > --with-ssl-static to fix the following openssl static build failure
 > raised since bump to version 5.33.0 in commit
 > 8cedb39764f70f9d467bf0cc1acc99a8bbb963d6:

 > checking for static SSL support... disabled
 > checking for SSL support... enabled
 > checking for SSL include directory... /home/buildroot/autobuild/instance-2/output-1/host/mipsel-buildroot-linux-uclibc/sysroot/usr/include
 > checking for SSL library directory... /lib64

 > [...]

 > mipsel-buildroot-linux-uclibc-gcc: ERROR: unsafe header/library path used in cross-compilation: '-L/lib64'

 > Fixes:
 >  - http://autobuild.buildroot.org/results/4189decbafb5d28c11d89ddac792b4610abeaff1

 > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
 > ---
 > Changes v1 -> v2 (after review of Yann E. Morin):
 >  - Only pass --with-ssl when building dynamically as this flag is
 >    ignored when building --with-ssl-static

Committed, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-12-03 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 21:06 [Buildroot] [PATCH v2, 1/1] package/monit: fix openssl static build Fabrice Fontaine
2023-12-03 16:44 ` Peter Korsgaard [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=875y1f1bjh.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.