Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/gnuplot: Add patch to fix 'undefined reference to gp_read_history'
Date: Sat, 5 Sep 2020 09:51:58 +0200	[thread overview]
Message-ID: <20200905075158.GU14354@scaer> (raw)
In-Reply-To: <20200903133014.19824-1-mf@go-sys.de>

Micheal, All,

On 2020-09-03 15:30 +0200, Michael Fischer spake thusly:
> Signed-off-by: Michael Fischer <mf@go-sys.de>

Thanks for this patch.

This is fixing autobuilder failures, so a reference to at least one
would have been good:

    Fixes:
        http://autobuild.buildroot.org/results/095/0956bc50b9823374254a2032d7897d48aff2d1fa/

> ---
>  package/gnuplot/0002-without-history.patch | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
>  create mode 100644 package/gnuplot/0002-without-history.patch
> 
> diff --git a/package/gnuplot/0002-without-history.patch b/package/gnuplot/0002-without-history.patch
> new file mode 100644
> index 0000000000..2ce144eabd
> --- /dev/null
> +++ b/package/gnuplot/0002-without-history.patch
> @@ -0,0 +1,18 @@
> +Patch to solve the 'undefined reference to gp_read_history'
> +
> +Signed-off-by: Michael Fischer <mf@go-sys.de>

Since gnuplot uses git, we need that patch to be git-formatted:

    https://buildroot.org/downloads/manual/manual.html#_format_and_licensing_of_the_package_patches

(Yes I know the existing patch does not conform to that requirement, but
that is a old patch, from before we started enforcing any coding style.)

Also, did you send that patch upstream? If so, it would be super nice
that you include the URL to the bug-report, or mailing post, so that we
eventually bump gnuplot, we can get rid of that patch.

Care to rework and respin, please?

Regards,
Yann E. MORIN.

> +diff -Naur a/src/history.c b/src/history.c
> +--- a/src/history.c	2020-09-03 14:48:47.875493026 +0200
> ++++ b/src/history.c	2020-09-03 14:50:39.493972218 +0200
> +@@ -91,7 +91,9 @@
> + void
> + read_history(char *filename)
> + {
> ++#ifdef GNUPLOT_HISTORY
> +     gp_read_history(filename);
> ++#endif	
> + }
> + 
> + 
> -- 
> 2.28.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2020-09-05  7:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 13:30 [Buildroot] [PATCH 1/1] package/gnuplot: Add patch to fix 'undefined reference to gp_read_history' Michael Fischer
2020-09-05  7:51 ` Yann E. MORIN [this message]
2020-09-08  7:39   ` Michael Fischer
  -- strict thread matches above, loose matches on Subject: below --
2020-09-14  9:07 Michael Fischer
2020-09-19 19:42 ` Thomas Petazzoni

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=20200905075158.GU14354@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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