On Sat, 9 Mar 2024 01:30:26 -0600
"David C. Rankin" wrote:
> New features are generally something that can be enabled if wanted, not
> something that is forced on an existing build system. For those building
> packages, they are quite familiar with how to generate a debug package if
> wanted --
On 3/7/24 06:10, Christian Heusel wrote:
This was introduced with the following change in pacman[0], see the
documentation for the 'debug' option in makepkg.conf(5):
debug
Add the user-specified debug flags as specified in
DEBUG_CFLAGS and DEBUG_CXXFLAGS to their counterpart
bui
; Martin
>
> On Thu, Mar 7, 2024, 14:41 Ryan Petris wrote:
>
>
> On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
>
> On 3/7/24 12:34, lacsaP Patatetom wrote:
> > hi,
> Hi,
> >
> > when I run `makepkg`, it generates a second package with the `-de
>> __
>> On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
>>> On 3/7/24 12:34, lacsaP Patatetom wrote:
>>> > hi,
>>> Hi,
>>> >
>>> > when I run `makepkg`, it generates a second package with the `-debug`
>>> &g
12:34, lacsaP Patatetom wrote:
> > hi,
> Hi,
> >
> > when I run `makepkg`, it generates a second package with the `-debug`
> > "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and
> > `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
> >
> > I
On Thu, 2024-03-07 at 12:34 +0100, lacsaP Patatetom wrote:
> hi,
>
> when I run `makepkg`, it generates a second package with the `-debug`
> ...
Right, while makepkg defaults to '!debug' at some point
/etc/makepkg.conf set the default to 'debug' instead.
Its act
Le jeu. 7 mars 2024 à 13:28, Robin Candau a écrit :
> On 3/7/24 13:21, Ryan Petris wrote:
> > On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
> >> On 3/7/24 12:34, lacsaP Patatetom wrote:
> >> > hi,
> >> Hi,
> >> >
> >> > when
On 3/7/24 13:21, Ryan Petris wrote:
On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
On 3/7/24 12:34, lacsaP Patatetom wrote:
> hi,
Hi,
>
> when I run `makepkg`, it generates a second package with the `-debug`
> "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst`
On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
> On 3/7/24 12:34, lacsaP Patatetom wrote:
> > hi,
> Hi,
> >
> > when I run `makepkg`, it generates a second package with the `-debug`
> > "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst`
On 24/03/07 12:34PM, lacsaP Patatetom wrote:
> hi,
Hey,
> when I run `makepkg`, it generates a second package with the `-debug`
> "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and
> `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
>
> I couldn't find any
That's not a split package, it's a package built with debug symbols for
analyses and debugging purposes.
See https://wiki.archlinux.org/title/Debuginfod for more info.
I see, thanks. Sorry for the confusion.
On 3/7/24 12:41, Robin Candau wrote:
On 3/7/24 12:38, Georg wrote:
hi,
when I run `makepkg`, it generates a second package with the `-debug`
"extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and
`mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything ab
On 3/7/24 12:38, Georg wrote:
hi,
when I run `makepkg`, it generates a second package with the `-debug`
"extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and
`mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new fe
hi,
when I run `makepkg`, it generates a second package with the `-debug`
"extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and
`mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature
and/or is there a param
On 3/7/24 12:34, lacsaP Patatetom wrote:
hi,
Hi,
when I run `makepkg`, it generates a second package with the `-debug`
"extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and
`mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki
hi,
when I run `makepkg`, it generates a second package with the `-debug`
"extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and
`mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature
and/or is there a param
te:
> > Sorry, I forgot to chmod that file to 666 when uploaded. That's done now.
> >
> Dowloaded and understand now why it is just 1.1k size : the build log is
> empty.
>
> This only happens when there's no build() function or --repackage is used in
> the make
On 27-11-2023 13:35, Jude DaShiell wrote:
Sorry, I forgot to chmod that file to 666 when uploaded. That's done now.
Dowloaded and understand now why it is just 1.1k size : the build log is
empty.
This only happens when there's no build() function or --repackage is
used in t
Sorry, I forgot to chmod that file to 666 when uploaded. That's done now.
--
Jude
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo.
Please use in that order."
Ed Howdershelt 1940.
On Mon, 27 Nov 2023, Lone_Wolf wrote:
>
> On 25-11-2023 16:57, Jude DaSh
On 25-11-2023 18:20, Gil Vicente Bernardo wrote:
I'm facing same problem, can't build chromium anymore (stopped recently)
ninja: build stopped: subcommand failed. ==> ERRO: Uma falha ocorreu
em build()
Hi, that's a different package and unlikely to have the same issue.
Also chromium is in
On 25-11-2023 16:57, Jude DaShiell wrote:
https://www.panix.com/~jdashiel/edbrowse-git-log.zip
has the four logs this build fail produced.
Something went wrong with the upload. I get "You don't have permission
to access this resource." and the size of the file is shown as 1.1k .
I can do
> ==> ERROR: A failure occurred in package().
> > > Aborting...
> >
> >
> > I doublechecked by building in a cleanchroot and everything works fine.
> > Something in your build environment seems amiss.
> >
> > If you want to investigate that furt
> > Aborting...
>
>
> I doublechecked by building in a cleanchroot and everything works fine.
> Something in your build environment seems amiss.
>
> If you want to investigate that further, you need to append the --log
> parameter to the makepkg command and uploa
erything works fine.
> Something in your build environment seems amiss.
>
> If you want to investigate that further, you need to append the --log
> parameter to the makepkg command and upload the build logs somewhere.
>
> a command like
>
> curl -F 'f:1=<-' ix.io
&
omething in your build environment seems amiss.
If you want to investigate that further, you need to append the --log
parameter to the makepkg command and upload the build logs somewhere.
a command like
curl -F 'f:1=<-' ix.io works well for that. after it has finished there will be
t; > install: cannot stat 'edbrowse': No such file or directory
> > make: *** [makefile:82: install] Error 1
> > ==> ERROR: A failure occurred in package().
> > Aborting...
>
>
> That file should exist in $srcdir/$pkgname/src when package() is run.
>
> Try adding --cleanbuild to the makepkg command line to ensure the build
> starts fresh.
>
> LW
>
That file should exist in $srcdir/$pkgname/src when package() is run.
Try adding --cleanbuild to the makepkg command line to ensure the build
starts fresh.
LW
ypto -o edbrowse
> > /usr/bin/ld: cannot find ../../quickjs/libquickjs.a: No such file or
> > directory
>
>
> Two more changes are needed:
>
>
> A.
>
> edbrowse relies on *.a files (static librairies) to use quickjs . makepkg by
> default removes them since a few year
-lssl -lcrypto -lpthread -lm
-lssl -lcrypto -o edbrowse
/usr/bin/ld: cannot find ../../quickjs/libquickjs.a: No such file or
directory
Two more changes are needed:
A.
edbrowse relies on *.a files (static librairies) to use quickjs .
makepkg by default removes them since a few years ago
On 23-11-2023 15:34, Jude DaShiell wrote:
That export patch failed and generated more error lines than the original
PKGBUILD had. I put that export line as the first line of the prepare
section in the PKGBUILD as a test.
On Thu, 23 Nov 2023, Jelle van der Waa wrote:
export CFLAGS="${CFLAGS}
That export patch failed and generated more error lines than the original
PKGBUILD had. I put that export line as the first line of the prepare
section in the PKGBUILD as a test.
-- Jude "There are four boxes to be used in
defense of liberty: soap, ballot, jury, and ammo. Please use in that
ord
Hi,
On 23/11/2023 14:39, Jude DaShiell wrote:
cc -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions
-Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security
-fstack-clash-protection -fcf-protection -Wall -Wno-unused
-D_FILE_OFFSET_BITS=64 -DEDBROWSE_ON_LINUX -c -o fetchmail.o
fetch
rowse-git and in doing so one of the failure
> > messages was some warnings being treated as errors.
> > man makepkg didn't show me any switch to prevent warnings being treated as
> > errors unless maybe force does that. Even with force the package didn't
> > install.
On 23/11/2023 11:26, Jude DaShiell wrote:
I failed to install edbrowse-git and in doing so one of the failure
messages was some warnings being treated as errors.
man makepkg didn't show me any switch to prevent warnings being treated as
errors unless maybe force does that. Even with
I failed to install edbrowse-git and in doing so one of the failure
messages was some warnings being treated as errors.
man makepkg didn't show me any switch to prevent warnings being treated as
errors unless maybe force does that. Even with force the package didn't
install.
Did anyone
On 4/23/21 4:07 PM, u34--- via arch-general wrote:
> I was expecting for
>
> makepkg nosuchoption
>
> to fail. And complain. Instead, it succeeds. The package seem to get
> built.
"nosuchoption" is not an --option flag, it is an operand. makepkg
support
I was expecting for
makepkg nosuchoption
to fail. And complain. Instead, it succeeds. The package seem to get
built.
The package involved is brscan4, from the AUR. All required files were
already ownloaded, and in place.
LC_ALL=C makepkg nosuchoption
PKGBUILD looks to me short and
A few months back there was a proposal to edit the default makepkg build flags
for improved security:
https://lists.archlinux.org/pipermail/arch-dev-public/2020-July/030031.html
As far as I can tell, this was never committed. The show-stopper at the time
was Clang 11 not being released yet
38 matches
Mail list logo
